Integration
Connect CallRail to systeme.io
When something happens in CallRail, 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 CallRail 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 CallRail and systeme.io
Triggers and actions 6 triggers ยท 10 actions
Trigger
Form CapturedTriggers when a form is captured.
- Outbound Call Completed
Triggers after an outbound phone call has been completed and its recording and transcription have been completed and attached. It contains the full data about the call. This trigger should not be expected to be real-time and has a maximum delay of 20 minutes after the hangup before it fires.
- Phone Call Started
Triggers when an inbound phone call is started.
- SMS Received
Triggers when an SMS message is received.
- SMS Sent
Triggers when an SMS message is sent.
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
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.