Integration
Connect Mailparser to Cursion
When New Email Parsed (One Request Per Email) fires in Mailparser, your agent runs Create Page in Cursion. 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 Mailparser and Cursion 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 Cursion
When New Email Parsed (One Request Per Email) in Mailparser
then Create Page in Cursion
When New Email Parsed (One Request Per Email) in Mailparser
then Add case in Cursion
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 Cursion
Triggers and actions 7 triggers · 17 actions
Trigger
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.
Trigger
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.
Trigger
New FlowTriggers when a new Flow is created in your Cursion account.
Trigger
New PageTriggers when a new page is added to a Cursion site.
Trigger
New ScanTriggers when a new Scan is created for the selected Cursion page.
Trigger
New SiteTriggers when a new site is added to your Cursion account.
Trigger
New TestTriggers when a new Test (a comparison of two scans) is created for a page.
Action
Add caseGenerates a new test case for a site from a plain-language prompt and returns the process tracking its creation.
Action
Add flowCreates a Flow in Cursion — a named sequence of steps (scans, cases, alerts) that FlowRuns execute.
Action
Create CaseRunRuns a saved Case against a Site, creating a CaseRun that executes in the background and returns immediately.
Action
Create FlowRunRuns a Flow against a Site and returns the new FlowRun, which completes asynchronously.
Action
Create PageCreates a Page under a Cursion Site and, unless skipped, starts its initial baseline Scan.
Action
Create ScanStarts a new Scan of a Site's pages in Cursion. The scan runs in the background and may take several minutes to complete.
Action
Create SiteCreates a Site in Cursion for a domain, then crawls it for pages and runs initial baseline scans in the background.
Action
Delete siteDeletes a site and, with it, all of the site's scans, tests, schedules and alerts.
Action
Get FlowRunReturns a single FlowRun — the result of running a Flow against a Site — including its nodes, status and logs.
Action
Get scanReturns a single Cursion scan with its HTML, logs, Lighthouse and security scores, and screenshots.
Action
Get siteReturns a single Cursion site with its URL, tags, crawl times and latest scan and test summary.
Action
Get testReturns a single Test, the comparison of two scans of a page, with its scores, status and deltas.
Action
List flowsReturns the flows in your Cursion account, including each flow's steps (nodes) and connections (edges).
Action
List pagesReturns the pages that belong to a Cursion site, with each page's URL, tags and latest scan and test results.
Action
List scansReturns the scans captured for a Cursion page, ordered by creation time.
Action
List sitesReturns the sites in your Cursion account, newest first, with each site's URL, tags and latest scan and test details.
Action
List testsReturns the Tests run against a Cursion Page, ordered by creation time.
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 Cursion
ActiveCampaign to CursionActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to CursionOrganize anything with Airtable, a modern database created for everyone.
Asana to CursionAsana is a collaborative information manager for workspace.
ClickUp to CursionClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.
Brevo to CursionBrevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...
Calendly to CursionCalendly is a scheduling automation platform for eliminating the back-and-forth emails to find the perfect...
Questions
Mailparser and Cursion, 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 Cursion when something happens in Mailparser?
Any of Cursion's 17 actions, including Create CaseRun, Create FlowRun, Create Page and Create Scan. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Cursion to Mailparser?
Cursion has no triggers in the catalog today, so automations start in Mailparser. If you need the other direction, ask: your agent reads Cursion's API documentation and adds it.
Do I have to build a connector for Mailparser or Cursion?
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.