Integration
Connect Mailparser to Ortto
When something happens in Mailparser, your agent does the next thing in Ortto. 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 Ortto 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 Ortto
Triggers and actions 6 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
Fields UpdatedTriggers when the specified field(s) of a record have been updated in your Ortto account.
Trigger
New Activity OccurredTriggers when a new Ortto activity occurs.
Trigger
New Record CreatedTriggers when a new record (contact or organization) has been added to your Ortto account.
Trigger
Tag Added/RemovedTriggers when a tag has beed added to, or removed from, a record.
Action
Add Custom FieldCreate a new custom field on the person or organization schema in Ortto. Endpoint: POST /v1/custom-field/create. Vendor doc: https://help.ortto.com/developer/latest/api-reference/custom-field/
Action
Create RecordCreate a new record (person, organization), or update an existing record in your Ortto account.
Action
Delete RecordArchive, restore, or permanently delete a person or organization record in Ortto. Endpoint: POST /v1/person/delete (and /v1/organization/delete for accounts). Vendor doc: https://help.ortto.com/a-260-archive-restore-and-delete-people-archive-restore-delete
Action
Get RecordFetches one or more people, or one or more accounts, by their Ortto ids, returning whichever fields you ask for.
Action
List ActivitiesRetrieve the activity feed for a given contact in Ortto. Endpoint: POST /v1/person/activities/list (activity log for a contact ID). Vendor doc: https://help.ortto.com/a-773-retrieve-activity-feed-for-a-given-contact
Action
Opt Out From SMSOpt out a person from all SMS communications.
Action
Search or Create RecordsSearch your Ortto data for a record based on the provided field or optionally create one if none is found.
Action
Tag/Untag RecordsAdds or removes tags on a person or an account in Ortto, matching the record by email address or account name.
Action
Unsubscribe a PersonUnsubscribe a person from all emails.
Action
Update Audience SubscriptionSubscribe or unsubscribe a person to/from an Ortto audience. Endpoint: POST /v1/audience/subscribe. Vendor doc: https://help.ortto.com/developer/latest/api-reference/audiences/
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.