Integration
Connect FlippingBook to Knock
When New Flipbook fires in FlippingBook, your agent runs Add user in Knock. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want FlippingBook and Knock to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What FlippingBook can start in Knock
When New Flipbook in FlippingBook
then Add user in Knock
When New Flipbook in FlippingBook
then Get user in Knock
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with FlippingBook and Knock
Triggers and actions 1 trigger · 18 actions
Trigger
New FlipbookTriggers when a new flipbook is created in the FlippingBook account.
Action
Add Flipbook SourceUploads a new PDF version to an existing flipbook from a public URL; it goes live once conversion finishes.
Action
Create FlipbookCreates a new flipbook, optionally converting a PDF from a public URL as its first version.
Action
Delete FlipbookMarks a flipbook for deletion; it is removed permanently after a period of time.
Action
Find Flipbook by IDReturns one flipbook (publication) by its unique ID, including its name, URL, page count and customization settings.
Action
Find Flipbook by Public URLFinds the flipbook whose public URL exactly matches the given URL.
Action
Find Flipbook by TitleFinds flipbooks whose name contains the given title text and returns the matching flipbooks.
Action
Get Trackable LinkReturns one trackable link with its state and view statistics.
Action
List Custom DomainsReturns the custom domains available in the FlippingBook account.
Action
Update FlipbookUpdates a flipbook's name or description and can replace its content with a new PDF from a public URL.
Action
Update Trackable LinkRenames a trackable link or disables, re-enables or deletes it.
Action
Add objectCreates an object in a Knock collection, or updates it if an object with that ID already exists, setting its name, locale, time zone, custom properties, channel data and preferences.
Action
Add userCreate a user in Knock, or update an existing one with the same user id (only the supplied properties change).
Action
Delete objectPermanently removes an object from the specified collection. This cannot be undone.
Action
Delete userPermanently delete a Knock user and all associated data.
Action
Get objectRetrieves a specific object by its ID from a collection, including all of its custom properties.
Action
Get userRetrieve a single Knock user by id.
Action
List objectsLists the objects in a Knock collection, optionally with their preferences.
Action
List usersList all users in the Knock account, paginated.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from FlippingBook
FlippingBook to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
FlippingBook to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
FlippingBook to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
FlippingBook to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
FlippingBook to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
FlippingBook to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Knock
EquipDash to KnockEquipDash is a AI-powered equipment rental and tour booking software built for outdoor recreation operators.
HubSpot to KnockHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to KnockSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to KnockSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to KnockGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to KnockGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
FlippingBook and Knock, answered
What can start an automation from FlippingBook?
Any of FlippingBook's 1 trigger in the catalog, including New Flipbook. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Knock when something happens in FlippingBook?
Any of Knock's 8 actions, including Add object, Add user, Get object and Get user. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Knock to FlippingBook?
Knock has no triggers in the catalog today, so automations start in FlippingBook. If you need the other direction, ask: your agent reads Knock's API documentation and adds it.
Do I have to build a connector for FlippingBook or Knock?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use FlippingBook and Knock without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.