Heyzine
for LuumenAI
Turn PDFs into flipbooks and manage their access from the terminal
Connect Heyzine and Luumen can list your flipbooks, read their social metadata, and check how much API quota is left before starting a batch. Conversions from PDF, DOCX, or PPTX, link creation, password rules, and access lists run as previewed steps you approve first. Authentication is by API key.
The Heyzine toolbox
14 tools: 7 read, 7 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet API LimitsRetrieve API rate limits.
- ReadGet Flipbook ID ToolRetrieve HTML for Flipbook ID tool.
- ReadGet Flipbook ListRetrieve all flipbooks.
- ReadGet Flipbook Social MetadataRetrieve social metadata for a specific flipbook.
- ReadGet jQuery PluginRetrieve the Heyzine jQuery plugin script URL and usage snippet.
- ReadSetup Heyzine WebhooksHelper tool to validate prerequisites for Heyzine webhooks.
- ReadHeyzine Webhooks - LeadsReceive webhook events when new leads are collected on a flipbook form.
- WriteCreate Flipbook LinkCreate a direct flipbook link. Approval by default
- WriteCreate Flipbook AsynchronouslyCreate a flipbook asynchronously. Approval by default
- WriteCreate Flipbook SyncConvert a PDF, DOCX, or PPTX into a flipbook synchronously via REST API. Approval by default
- WriteDelete FlipbookDelete a flipbook. Approval by default
- WriteUpdate Flipbook Access ListUpdate the access list of a flipbook. Approval by default
- WriteUpdate Flipbook Password ProtectionUpdate flipbook password protection settings. Approval by default
- WriteUpdate Flipbook Social MetadataUpdate a flipbook's social metadata. Approval by default
One prompt, start to finish
What a governed Heyzine run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — create flipbook link, create flipbook asynchronously, create flipbook sync, delete flipbook, and more — is shown as a plan and requires approval by default, including the 1 action classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Heyzine — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
ConfluenceSOPs and runbooks that become skills the whole team can run.
NotionRunbooks in Notion, followed and turned into skills.
SharePointRead SharePoint sites for context, then change files and permissions on approval.
Google DriveSearch Drive for the file you need, then write the change back as an approved stepPut Heyzine to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.