Integration
Connect Mailparser to Planfact
When New Email Parsed (One Request Per Email) fires in Mailparser, your agent runs Add invoice document in Planfact. 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 Planfact 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 Planfact
When New Email Parsed (One Request Per Email) in Mailparser
then Add invoice document in Planfact
When New Email Parsed (One Request Per Email) in Mailparser
then Add project in Planfact
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 Planfact
Triggers and actions 2 triggers · 20 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.
Action
Add accountCreates a new account (cash, card or electronic money account) in Planfact for a company, with its currency and opening balance.
Action
Add contragentCreates a new contragent (counterparty) in Planfact.
Action
Add invoice documentCreates a new invoice (bill for payment) in PlanFact for a bank account and counterparty, optionally with product lines.
Action
Add operation categoryCreates a new income, outcome or balance-sheet category (article) in PlanFact.
Action
Add operation incomeCreates an income (incoming payment) operation on a Planfact account, optionally split across projects, counterparties and categories.
Action
Add operation outcomeCreates an outcome (payment / expense) operation in Planfact on the chosen account.
Action
Add productCreates a new product or service in Planfact with its name, price, currency and VAT.
Action
Add projectCreates a new project in Planfact, optionally in a project group and linked to a budget.
Action
Delete contragentDeletes a contragent (counterparty) from Planfact.
Action
Delete operationDeletes an operation (income, outcome, move or accrual transaction) from PlanFact by its ID.
Action
Get accountReturns a single money account (cash, card or bank account) by its id, including its currency, current balance and bank details.
Action
Get contragentReturns a single contragent (counterparty) by its ID, including its names, tax identifiers, type, group and default income/outcome categories.
Action
Get operationReturns a single Planfact operation (income, outcome, move, accrual, shipment or supply) by its id, including its account, counterparty, category and project parts.
Action
Get projectReturns a Planfact project by its ID, including its group, currency and status.
Action
List contragentsReturns a list of counterparties (contragents), optionally filtered by name, type, status, group or change date.
Action
List operation categoriesReturns the account's income and expense categories (operation categories), optionally filtered by type, name or parent.
Action
List productsReturns the products and services in your Planfact account, optionally filtered by search text, type, external ID or change date.
Action
List projectsReturns the projects in your Planfact account, optionally filtered by name, group, status or dates.
Action
Update contragentUpdates an existing counterparty (contragent) in Planfact, such as its name, tax details, type, default categories or group.
Action
Update projectUpdates an existing Planfact project's name, comment, status, group, budget or closed flag.
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 Planfact
HubSpot to PlanfactHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to PlanfactSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to PlanfactSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to PlanfactGoogle Sheets
Gmail to PlanfactGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to PlanfactGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Mailparser and Planfact, 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 Planfact when something happens in Mailparser?
Any of Planfact's 20 actions, including Update contragent, Update project, Add account and Add contragent. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Planfact to Mailparser?
Planfact has no triggers in the catalog today, so automations start in Mailparser. If you need the other direction, ask: your agent reads Planfact's API documentation and adds it.
Do I have to build a connector for Mailparser or Planfact?
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.