Heyzine MCP integration for AI agents.
Connect AI agents to Heyzine through 9 structured actions, including get flipbook, add flipbook to bookshelf, and delete flipbook. Review authentication, inp…
- ACTION CONTRACTS
- 9
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Heyzine integration exposes
The Heyzine Agent App exposes 9 provider-backed actions for design & media and productivity work. Its current contract lets an authorized agent get the details and oembed metadata for a specific heyzine flipbook, add a flipbook to a specific heyzine bookshelf, and delete a specific heyzine flipbook. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Heyzine account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Heyzine capabilities.
Showing 9 of 9 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_flipbookREADGet the details and oEmbed metadata for a specific Heyzine flipbook.
INPUTS: id
add_flipbook_to_bookshelfWRITEAdd a flipbook to a specific Heyzine bookshelf.
INPUTS: id / flipbook_id / position
delete_flipbookHIGH IMPACTDelete a specific Heyzine flipbook.
INPUTS: id
list_bookshelf_flipbooksREADList the flipbooks assigned to a specific Heyzine bookshelf.
INPUTS: id
list_bookshelvesREADList the bookshelves accessible with the current Heyzine API key.
list_flipbooksREADList the flipbooks accessible with the current Heyzine API key.
remove_flipbook_from_bookshelfHIGH IMPACTRemove a flipbook from a specific Heyzine bookshelf.
INPUTS: id / flipbook_id
set_bookshelf_social_dataWRITESet the social sharing metadata for a specific Heyzine bookshelf.
INPUTS: id / title / description / thumbnail
set_flipbook_social_dataWRITESet the social sharing metadata for a specific Heyzine flipbook.
INPUTS: id / title / description / thumbnail
INPUT CONTRACTS
Know what the action needs before it runs.
get_flipbook
idREQUIRED- The Heyzine flipbook or bookshelf identifier.
add_flipbook_to_bookshelf
idREQUIRED- The Heyzine flipbook or bookshelf identifier.
flipbook_idREQUIRED- The Heyzine flipbook identifier.
positionOPTIONAL- The optional 0-based position inside the bookshelf.
delete_flipbook
idREQUIRED- The Heyzine flipbook or bookshelf identifier.
list_bookshelf_flipbooks
idREQUIRED- The Heyzine flipbook or bookshelf identifier.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Flipbook
Get the details and oEmbed metadata for a specific Heyzine flipbook. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_flipbookControl Add Flipbook To Bookshelf
Add a flipbook to a specific Heyzine bookshelf. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
add_flipbook_to_bookshelfVerify with List Bookshelf Flipbooks
List the flipbooks assigned to a specific Heyzine bookshelf. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_bookshelf_flipbooksSAFETY BOUNDARY
Operate Heyzine with explicit limits
- Authorize Heyzine with API key and grant only the provider access required by the selected actions.
- 5 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_flipbook` and `remove_flipbook_from_bookshelf` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Heyzine rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Heyzine task completed successfully.
CONNECTION MODEL
API key
Heyzine API key sent with the Authorization: Bearer header. Log in or register on the developers page to view it.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 4
- WRITE SIGNALS
- 3
- HIGH IMPACT
- 2
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Heyzine.