Integration
Connect Docparser and Zengine
When Parsed Document Data Available fires in Docparser, your agent runs Add Form Record in Zengine, or New Event in Zengine to Upload Document in Docparser. 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 Docparser and Zengine 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 Docparser and Zengine can do together
From Docparser to Zengine
When Parsed Document Data Available in Docparser
then Add Form Record in Zengine
From Zengine to Docparser
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 Docparser and Zengine
Triggers and actions 5 triggers · 14 actions
- Parsed Document Data Available
Triggers whenever a new Document is processed and parsed data is available.
- Parsed Table Row Available
Triggers whenever a new Document is processed and parsed table rows are available.
- Fetch Document From URL
Fetches a new document from a publicly accessible URL and imports it into Docparser to begin parsing. (To receive the parsing results, you'll need a separate Zap listening for the "New Parsed Data Available" Trigger).
- Upload Document
Uploads a new document to Docparser which will immediately begin parsing after reception. (To receive the parsing results, you'll need a separate Zap listening for the "New Parsed Data Available" Trigger).
- New Event
Triggers when a new event is added.
- New Task
Triggers when a new task is added.
- Updated Record
Triggers when any record is updated in a form of your choice.
- Add Comment
Adds a comment to a record or workspace.
- Add Form Record
Adds a record to a form.
- Add record
Create a record in a form.
- Create Event
Creates a calendar event in a Zengine workspace.
- Create Task
Creates a task in a Zengine workspace.
- Delete Record
Deletes a record.
- Find Record
Returns the records in a form that match the specified name, folder, creator, completion state or dates.
- Get Event
Returns one calendar event by id.
- Get record
Retrieve one record by id.
- Get Task
Returns one task by id.
- Update Record
Updates a record.
- Upload File to Field
Uploads a file, which can then be saved to a file upload field in a New Record or Update Record action.
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 Docparser
Docparser to PrismixReal-time uptime for 77 AI APIs (OpenAI, Anthropic, Cursor, Gemini) — free JSON endpoint, no auth required
Docparser to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Docparser to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Docparser to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Docparser to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Docparser to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
More into Zengine
Google Calendar to ZengineGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Docparser and Zengine, answered
What can start an automation from Docparser?
Any of Docparser's 2 triggers in the catalog, including Parsed Document Data Available and Parsed Table Row Available. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Zengine when something happens in Docparser?
Any of Zengine's 12 actions, including Create Event, Create Task, Update Record and Upload File to Field. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Zengine to Docparser?
Yes. When something happens in Zengine, your agent can act in Docparser too. This page covers both directions: Zengine's triggers and Docparser's actions are listed here as well.
Do I have to build a connector for Docparser or Zengine?
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 Docparser and Zengine 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.