Integration
Connect Parseur to Ziflow
When New Document Export Failed fires in Parseur, your agent runs Add user in Ziflow. 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 Parseur and Ziflow 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 Parseur can start in Ziflow
When New Document Export Failed in Parseur
then Add user in Ziflow
When New Document Not Processed in Parseur
then Add guest in Ziflow
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 Parseur and Ziflow
Triggers and actions 6 triggers · 24 actions
Trigger
New Document Export FailedTriggered when Parseur fails to export a document to its destination.
Trigger
New Document Not ProcessedTriggered when Parseur receives a document it cannot extract data from, so you can follow it up.
Trigger
New Document ProcessedTriggered when Parseur finishes extracting data from a document, with the extracted fields.
Trigger
New Document Processed (With List Items)Triggered when Parseur finishes extracting data from a document, including any table or list fields it found (line items, rows).
Trigger
New MailboxTriggers when a new mailbox is created in your Parseur account. Returns the mailbox's name, email prefix, AI engine and document counts.
Trigger
New Table Field ProcessedTriggers once for every row of a table or list field when Parseur finishes processing a document. Returns the row's values along with the document and mailbox it came from.
Action
Create DocumentSends text or HTML content to a Parseur mailbox as a new document, so Parseur can extract its data. Returns the new document's ID.
Action
Create Document From FileUploads a file (PDF, DOCX, image and so on) to a Parseur mailbox as a new document, so Parseur can extract its data. Returns the new document's ID.
Action
Delete DocumentDeletes a document from Parseur by its ID.
Action
Delete MailboxDeletes a Parseur mailbox and everything in it. This cannot be undone.
Action
Get DocumentReturns one document from Parseur by its ID, including its processing status and the data Parseur extracted from it.
Action
Get MailboxReturns one Parseur mailbox by its ID, with its email address, document counts and settings.
Action
List DocumentsReturns the documents in Parseur, optionally narrowed to one mailbox or one processing status.
Action
List MailboxesReturns the mailboxes in your Parseur account, with the email address to send documents to and how many documents each holds.
Action
Reprocess DocumentSends an existing document back through parsing, for example after you update its template. Returns the document's ID, name and processing status.
Action
Update MailboxUpdates a Parseur mailbox's settings. Only the values you supply are changed — anything you leave blank keeps its current setting.
Action
Add guestAdds a guest (an external reviewer) to your Ziflow account.
Action
Add reviewerAdds a reviewer, by email, to a stage of a Ziflow proof.
Action
Add userAdds a user to your Ziflow account. Requires an account with Admin rights.
Action
Create FolderCreates a new folder in Ziflow, optionally inside an existing parent folder.
Action
Create ProofCreates a new proof in Ziflow from one or more file or web page URLs, routed through the review stages you specify.
Action
Delete proofDeletes a proof in Ziflow.
Action
Find proofs by criteriaReturns the proofs that match the search criteria you give, such as status or owner.
Action
Get folderReturns a Ziflow folder, optionally together with its sub-folders.
Action
Get proofReturns a proof by its ID, including its name, status, versions, stages and reviewers.
Action
Get userReturns a Ziflow user in the account, looked up by user ID or email address.
Action
List proofsReturns the proofs available to the connected Ziflow user, sorted from newest to oldest.
Action
Make decisionRecords a reviewer's decision on a proof, or marks their review as complete, depending on the reviewer's role.
Action
Update folderUpdates an existing Ziflow folder's name, privacy, or parent folder (moving it). Returns the updated folder.
Action
Update proofUpdates an existing proof's name, folder or review stages. Only the values you provide are changed; returns the updated proof.
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 Parseur
Parseur to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Parseur to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Parseur to StripeStripe is a payment processing platform for online businesses.
Parseur to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Parseur to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Parseur to PipedrivePipedrive is a sales CRM and pipeline management tool.
More into Ziflow
HubSpot to ZiflowHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to ZiflowSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to ZiflowSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to ZiflowGoogle Sheets
Gmail to ZiflowGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to ZiflowGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Parseur and Ziflow, answered
What can start an automation from Parseur?
Any of Parseur's 6 triggers in the catalog, including New Document Export Failed, New Document Not Processed, New Document Processed and New Document Processed (With List Items). Describe the moment in plain language and your agent picks the right one.
What can your agent do in Ziflow when something happens in Parseur?
Any of Ziflow's 14 actions, including Create Folder, Create Proof, Update folder and Update proof. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Ziflow to Parseur?
Ziflow has no triggers in the catalog today, so automations start in Parseur. If you need the other direction, ask: your agent reads Ziflow's API documentation and adds it.
Do I have to build a connector for Parseur or Ziflow?
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 Parseur and Ziflow 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.