Integration
Connect systeme.io to Peerdom
When something happens in systeme.io, your agent does the next thing in Peerdom. 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 Peerdom 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 Peerdom
Triggers and actions 6 triggers ยท 34 actions
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
Trigger
New GroupTriggered when a new circle is created
Trigger
New MapTriggers when a new map is created.
Trigger
New PeerTriggers when a new peer is created.
Trigger
New ProjectTriggers when a new project is created.
Trigger
New RoleTriggers when a new role is created.
Action
Add GoalCreate a goal on a role or circle. POST /goals
Action
Assign Role to PeerAssigns an existing role to a peer in Peerdom.
Action
Create GroupCreates a new group in Peerdom.
Action
Create PeerCreates a new peer in Peerdom.
Action
Create RoleCreates a new role in Peerdom.
Action
Delete GroupDelete a group by id. DELETE /groups/{id}
Action
Delete PeerDelete a peer by id. DELETE /peers/{id}
Action
Delete RoleDelete a role by id from a live or draft map. DELETE /roles/{id}
Action
Get GroupGet a single group by id. GET /groups/{id}
Action
Get PeerGet a single peer by id. GET /peers/{id}
Action
Get Peer by E-MailGet Peer by a Given E-Mail.
Action
Get ProjectGet a single project by id. GET /projects/{id}
Action
Get RoleGet a single role by id from a live or draft map. GET /roles/{id}
Action
List GroupsList all groups. GET /groups
Action
List MapsList all maps in the tenant. GET /maps
Action
List PeersList all peers in the tenant. GET /peers
Action
List ProjectsList all projects. GET /projects
Action
List RolesList all roles. GET /roles
Action
Unassign Peer From RoleUnassign peer from a given role.
Action
Update GoalUpdate a goal by id. PATCH /goals/{id}
Action
Update GroupUpdates an existing group (circle, bubble, pod, etc.) in Peerdom.
Action
Update PeerUpdates an existing peer in Peerdom.
Action
Update ProjectUpdate a project by id. PATCH /projects/{id}
Action
Update RoleUpdates an existing role in Peerdom.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.