Integration
Connect systeme.io to APIs.guru
When something happens in systeme.io, your agent does the next thing in APIs.guru. 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 APIs.guru 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 APIs.guru
Triggers and actions 1 trigger ยท 16 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
Find APIs by providerReturns all APIs listed for a given provider. GET /{provider}.json (provider input path param)
- Find service names by provider
Returns all serviceNames registered for a given provider (providers that host multiple APIs under sub-services). GET /{provider}/services.json (provider input path param)
- Get API metrics
Returns basic aggregate metrics about the APIs.guru directory (numSpecs, numAPIs, numEndpoints, etc). GET /metrics.json
- Get API specification
Retrieves one version of a particular API's OpenAPI spec by provider and api version, optionally scoped to a serviceName. GET /specs/{provider}/{api}.json or /specs/{provider}/{service}/{api}.json (provider, api, optional service input params)
- List APIs
Returns the full catalog of all APIs indexed by APIs.guru, keyed by provider/api. GET /list.json
- List providers
Returns the full list of API providers known to APIs.guru. GET /providers.json
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.