Integration
Connect FlippingBook to Azure Form Recognizer
When New Flipbook fires in FlippingBook, your agent runs Analyze Invoice in Azure Form Recognizer. 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 Azure Form Recognizer 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 Azure Form Recognizer
When New Flipbook in FlippingBook
then Analyze Invoice in Azure Form Recognizer
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 Azure Form Recognizer
Triggers and actions 1 trigger · 16 actions
- New Flipbook
Triggers when a new flipbook is created in the FlippingBook account.
- Add Flipbook Source
Uploads a new PDF version to an existing flipbook from a public URL; it goes live once conversion finishes.
- Create Flipbook
Creates a new flipbook, optionally converting a PDF from a public URL as its first version.
- Delete Flipbook
Marks a flipbook for deletion; it is removed permanently after a period of time.
- Find Flipbook by ID
Returns one flipbook (publication) by its unique ID, including its name, URL, page count and customization settings.
- Find Flipbook by Public URL
Finds the flipbook whose public URL exactly matches the given URL.
- Find Flipbook by Title
Finds flipbooks whose name contains the given title text and returns the matching flipbooks.
- Get Trackable Link
Returns one trackable link with its state and view statistics.
- List Custom Domains
Returns the custom domains available in the FlippingBook account.
- Update Flipbook
Updates a flipbook's name or description and can replace its content with a new PDF from a public URL.
- Update Trackable Link
Renames a trackable link or disables, re-enables or deletes it.
- Analyze Document
Analyzes a document with a prebuilt or custom model (layout, invoice, receipt, ID, tax form and more) and returns its text, fields, tables and key-value pairs.
- Analyze Invoice
Extracts the key details of an invoice: vendor, customer, invoice number, dates, totals, tax and line items.
- Analyze Receipt
Extracts the key details of a sales receipt: merchant, date and time, subtotal, tax, tip, total and line items.
- Extract Document Layout
Extracts the text, tables, paragraphs and structure of a document, optionally as Markdown.
- Get Document Model
Returns a document model's details, including the document types it recognizes and the fields each one extracts.
- List Document Models
Returns the prebuilt and custom document models available in your resource.
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 Azure Form Recognizer
Questions
FlippingBook and Azure Form Recognizer, 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 Azure Form Recognizer when something happens in FlippingBook?
Any of Azure Form Recognizer's 6 actions, including Analyze Document, Analyze Invoice, Analyze Receipt and Extract Document Layout. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Azure Form Recognizer to FlippingBook?
Azure Form Recognizer has no triggers in the catalog today, so automations start in FlippingBook. If you need the other direction, ask: your agent reads Azure Form Recognizer's API documentation and adds it.
Do I have to build a connector for FlippingBook or Azure Form Recognizer?
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 Azure Form Recognizer 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.