Integration
Connect Mailparser to systeme.io
When something happens in Mailparser, your agent does the next thing in systeme.io. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Mailparser and systeme.io to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Mailparser and systeme.io
Triggers and actions 3 triggers · 10 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 Tag Added to ContactTriggers when a tag is added to contact.
Action
Add digital productCreate a new payment Digital Product resource. POST /api/payment/digital-products
Action
Add tag to contactAssign an existing Tag to a Contact by id (distinct from create-or-update-with-tags). POST /api/contacts/{id}/tags
Action
Create or Update a Contact, Including Adding TagsCreates a contact in systeme.io, or updates the existing contact with that email address, and applies any tags you list.
Action
Delete contactRemove a Contact resource by id. DELETE /api/contacts/{id}
Action
Find contacts by emailSearch Contact resources filtered by email address. GET /api/contacts?email=
Action
Get contactRetrieve a single Contact resource by id. GET /api/contacts/{id}
Action
List contactsRetrieve the collection of Contact resources, paginated. GET /api/contacts
Action
List digital productsRetrieve the collection of payment Digital Product resources. GET /api/payment/digital-products
Action
List tagsRetrieve the collection of Tag resources. GET /api/tags
Action
Remove TagRemoves tag from a contact
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