Integration
Connect Mailparser to ZapCap
When something happens in Mailparser, your agent does the next thing in ZapCap. Describe it 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 Mailparser and ZapCap to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 Mailparser can start in ZapCap
When New Email Parsed (One Request Per Email) in Mailparser
then Add font in ZapCap
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 Mailparser and ZapCap
Triggers and actions 2 triggers · 14 actions
- New Email Parsed (One Request Per Email)
Triggered instantly when Mailparser finishes parsing an inbound email, with all of that email's parsed data delivered in a single request. In Mailparser, open your inbox and add a Generic Webhook under Integrations/Downstream Webhooks, paste the minted URL, and set Repeating Data Behaviour to "One request per Email". Parsed fields bind as {{ trigger.body.* }}. Use the One Request Per Row trigger instead when you are parsing tabular data and want each row handled as its own run.
- New Email Parsed (One Request Per Row)
Triggered instantly for EACH parsed table row when Mailparser finishes parsing an inbound email — one run per row, for tabular data such as invoice line items or price lists. In Mailparser, open your inbox and add a Generic Webhook under Integrations/Downstream Webhooks, paste the minted URL, and set Repeating Data Behaviour to "One request per row". That row's fields bind as {{ trigger.body.* }}. Use the One Request Per Email trigger instead when you want the whole email's parsed data in a single run.
- Add font
Uploads a custom font file (TTF, OTF, WOFF or WOFF2) to ZapCap so it can be used in caption styling.
- Add video
Uploads a video (or audio file) to ZapCap from a public URL and returns the new video's id, which is used to create captioning tasks.
- Approve transcript
Approves a captioning task's transcript and starts rendering the video with the transcript currently stored on the task.
- Delete font
Deletes a custom font you uploaded to ZapCap.
- Generate video clips
Starts a ZapCap task that cuts short clips out of an uploaded long-form video. The task runs in the background; use Get clip task with the returned task id to check its status and fetch the clips.
- Get account balance
Returns the remaining API credit balance (USD) on the connected ZapCap account.
- Get clip task
Retrieves a ZapCap clip task (viral shorts generation) for a video, including its status and generated clips.
- Get font
Retrieves the details of one uploaded custom font: its file name, font family and style.
- Get transcript
Get the word-by-word transcript of a ZapCap captioning task.
- Get video task
Fetches the status and result of a captioning task by ID. An error occurs if the task is not found.
- List templates
Lists every captioning template available to the account, with its id, categories and preview links. Use a template id when creating a video processing task.
- List videos
Lists the videos uploaded to your ZapCap account, with their metadata and associated task ids.
- Process Video
Starts a captioning (processing) task on an uploaded ZapCap video using a template. The task runs asynchronously; use Get video task to check its status and fetch the rendered video.
- Update transcript
Updates an existing video task's transcript by ID before rendering.
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 Mailparser
Mailparser to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Mailparser to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Mailparser to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Mailparser to Google SheetsGoogle Sheets
Mailparser to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Mailparser to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into ZapCap
Peerdom to ZapCapPeerdom helps teams navigate change with smart org charts that boost collaboration and performance.
Questions
Mailparser and ZapCap, answered
What can start an automation from Mailparser?
Any of Mailparser's 2 triggers in the catalog, including New Email Parsed (One Request Per Email) and New Email Parsed (One Request Per Row). Describe the moment in plain language and your agent picks the right one.
What can your agent do in ZapCap when something happens in Mailparser?
Any of ZapCap's 14 actions, including Update transcript, Add font, Add video and Approve transcript. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from ZapCap to Mailparser?
ZapCap has no triggers in the catalog today, so automations start in Mailparser. If you need the other direction, ask: your agent reads ZapCap's API documentation and adds it.
Do I have to build a connector for Mailparser or ZapCap?
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.
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.