Integration
Connect Mailparser to ServiceM8
When New Email Parsed (One Request Per Email) fires in Mailparser, your agent runs Add company contact in ServiceM8. 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 ServiceM8 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 ServiceM8
When New Email Parsed (One Request Per Email) in Mailparser
then Add company contact in ServiceM8
When New Email Parsed (One Request Per Email) in Mailparser
then Add job payment in ServiceM8
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 ServiceM8
Triggers and actions 4 triggers · 23 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
Job QueuedTriggers when a Job is assigned to a Queue.
Trigger
New JobTriggers when a new job is created.
Action
Add attachmentUploads a file and attaches it to a job (or another ServiceM8 record), so it appears in that record's diary.
Action
Add company contactCreates a new contact person on a ServiceM8 client (company), such as a billing or job contact.
Action
Add job allocationAllocates a ServiceM8 job to a staff member, optionally with a scheduled date and allocation window.
Action
Add job materialAdds a material line item to a ServiceM8 job, with quantity, pricing and tax details.
Action
Add job paymentRecords a payment against a ServiceM8 job, with its amount, method, date and optional note.
Action
Add noteAdds a note to a job, client or other ServiceM8 record.
Action
Create ClientCreates a new client (company) record in ServiceM8.
Action
Create JobCreates a new job in ServiceM8, optionally linked to a client, category and queue, and returns the new job's UUID.
Action
Delete clientDeletes (archives) a client in ServiceM8.
Action
Delete jobDeletes (archives) a job in ServiceM8. The job is hidden in the app and can be restored later.
Action
Get attachmentReturns the details of a single file attachment (photo, PDF or other file) by its UUID.
Action
Get clientReturns one ServiceM8 client (company) record by its UUID, including its name, address and billing details.
Action
Get jobReturns a single ServiceM8 job by its UUID, including its status, client, address and totals.
Action
Get Job AllocationReturns a single job allocation — which staff member a job is allocated to, its window, dates and status.
Action
List clientsReturns the clients (companies) in your ServiceM8 account, optionally narrowed by a filter.
Action
List job materialsReturns the materials (line items) recorded on jobs, optionally filtered, for example to a single job.
Action
List job paymentsReturns the payments recorded against jobs, optionally filtered (for example to a single job).
Action
List Job QueuesReturns the job queues set up in the ServiceM8 account.
Action
List jobsReturns the jobs in your ServiceM8 account, optionally narrowed by a filter.
Action
List notesReturns the notes in your ServiceM8 account, optionally filtered and sorted.
Action
List staff membersReturns the staff members in your ServiceM8 account, optionally narrowed by a filter.
Action
Update clientUpdates an existing client (company) in ServiceM8. Only the fields you fill in are changed.
Action
Update jobUpdates an existing job in ServiceM8, changing only the fields you fill in.
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 ServiceM8
HubSpot to ServiceM8HubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to ServiceM8Salesforce is a leading enterprise customer relationship management (CRM) platform.
Google Sheets to ServiceM8Google Sheets
Gmail to ServiceM8Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to ServiceM8Google Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to ServiceM8Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Questions
Mailparser and ServiceM8, 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 ServiceM8 when something happens in Mailparser?
Any of ServiceM8's 23 actions, including Create Client, Create Job, Update client and Update job. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from ServiceM8 to Mailparser?
ServiceM8 has no triggers in the catalog today, so automations start in Mailparser. If you need the other direction, ask: your agent reads ServiceM8's API documentation and adds it.
Do I have to build a connector for Mailparser or ServiceM8?
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.