Integration
Connect Mailparser to Shift4
When something happens in Mailparser, your agent does the next thing in Shift4. 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 Shift4 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 Shift4
When New Email Parsed (One Request Per Email) in Mailparser
then Add card in Shift4
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 Shift4
Triggers and actions 2 triggers · 21 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 card
Saves a credit or debit card to an existing Shift4 customer, either from a card token / successful charge, or from full card details.
- Add charge
Creates a new charge to a customer or card.
- Add customer
Creates a new customer in Shift4, optionally saving a card to them as their default card.
- Add plan
Creates a new subscription plan that customers can be subscribed to.
- Add refund
Refunds an existing charge in full or in part, returning the funds to the card that was charged.
- Add subscription
Creates a subscription that bills a customer automatically according to a plan.
- Delete card
Deletes a saved card from a Shift4 customer. If the deleted card was the customer's default, the most recently added card becomes the new default.
- Delete customer
Deletes an existing Shift4 customer.
- Delete plan
Deletes a plan by ID.
- Delete subscription
Cancels/deletes an existing subscription by ID.
- Get charge
Fetches a charge by ID.
- Get customer
Fetches a customer by ID.
- Get dispute
Fetches a dispute by ID.
- Get plan
Fetches a plan by ID.
- Get refund
Retrieves an existing Shift4 refund by its id.
- Get subscription
Fetches a subscription by ID.
- List cards
Lists the saved cards of a Shift4 customer, most recently created first.
- List refunds
Returns all refunds.
- Update charge
Updates an existing Shift4 charge's customer, description, shipping, billing, fraud status or metadata. Fields left blank are unchanged.
- Update customer
Updates an existing Shift4 customer. Any field left blank is left unchanged.
- Update subscription
Updates an existing subscription. Any field left blank is left unchanged.
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 Shift4
Instagram to Shift4Instagram is a social media platform for sharing photos, videos, and stories.
Questions
Mailparser and Shift4, 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 Shift4 when something happens in Mailparser?
Any of Shift4's 21 actions, including Update charge, Update customer, Update subscription and Add card. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Shift4 to Mailparser?
Shift4 has no triggers in the catalog today, so automations start in Mailparser. If you need the other direction, ask: your agent reads Shift4's API documentation and adds it.
Do I have to build a connector for Mailparser or Shift4?
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.