Integration
Connect systeme.io to Emailr
When something happens in systeme.io, your agent does the next thing in Emailr. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want systeme.io and Emailr 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 systeme.io and Emailr
Triggers and actions 1 trigger ยท 22 actions
Trigger
New Tag Added to ContactTriggers when a tag is added to contact.
- Add digital product
Create a new payment Digital Product resource. POST /api/payment/digital-products
- Add tag to contact
Assign an existing Tag to a Contact by id (distinct from create-or-update-with-tags). POST /api/contacts/{id}/tags
- Create or Update a Contact, Including Adding Tags
Creates a contact in systeme.io, or updates the existing contact with that email address, and applies any tags you list.
- Delete contact
Remove a Contact resource by id. DELETE /api/contacts/{id}
- Find contacts by email
Search Contact resources filtered by email address. GET /api/contacts?email=
- Get contact
Retrieve a single Contact resource by id. GET /api/contacts/{id}
- List contacts
Retrieve the collection of Contact resources, paginated. GET /api/contacts
- List digital products
Retrieve the collection of payment Digital Product resources. GET /api/payment/digital-products
- List tags
Retrieve the collection of Tag resources. GET /api/tags
- Remove Tag
Removes tag from a contact
Action
Add contactCreate a contact. POST /v1/contacts
- Add segment
Create a contact segment. POST /v1/segments
- Add template
Create an email template. POST /v1/templates
- Delete contact
Delete a contact by ID. DELETE /v1/contacts/{id}
- Delete segment
Delete a segment by ID. DELETE /v1/segments/{id}
- Delete template
Delete a template by ID. DELETE /v1/templates/{id}
- Get contact
Fetch a contact by ID. GET /v1/contacts/{id}
- Get template
Fetch a template by ID. GET /v1/templates/{id}
- List segments
List contact segments. GET /v1/segments
- Update contact
Update a contact by ID. PUT /v1/contacts/{id}
- Update segment
Update a segment by ID. PUT /v1/segments/{id}
- Update template
Update a template by ID. PUT /v1/templates/{id}
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.