Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Systeme.io

Systeme.io is a CRM platform that allows you to manage your contacts, sales, and marketing campaigns.

CategoryMarketing
Authenticationcustom
Version0.1.9
Published scopes0 published scopes
Last updatedSeptember 30, 2026

Overview

Connect Systeme.io with Flows360

Systeme.io is a CRM platform that allows you to manage your contacts, sales, and marketing campaigns.

Use the Systeme.io connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 5 actions and 3 triggers.

Available actions

  • Create Contact
  • Add Tag to Contact
  • Remove Tag from Contact
  • Find Contact by Email
  • Update Contact

Available triggers

  • New Contact
  • New Sale
  • New Tag Added to Contact

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Systeme.io
  • Package: @activepieces/piece-systeme-io@0.1.9
  • Exact artifact digest: sha256:2c51116ec18bbb4509dd2a5e04f2ff68e4ccb6343913d2cbfbe0563964bf5862
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Contact (createContact), Create a new contact with email and contact fields from your Systeme.io account, with optional tags Classification: read.
  • Add Tag to Contact (addTagToContact), Assign a tag to an existing contact - select an existing tag or create a new one Classification: read.
  • Remove Tag from Contact (removeTagFromContact), Remove a tag that is currently assigned to an existing contact Classification: read.
  • Find Contact by Email (findContactByEmail), Locate an existing contact by email address Classification: read.
  • Update Contact (updateContact), Update fields (name, phone, custom fields) of an existing contact using fields from your Systeme.io account Classification: read.

Trigger contracts

  • New Contact, webhook.
  • New Sale, webhook.
  • New Tag Added to Contact, webhook.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

Authenticationcustom
Supported objects8
Supported actionsNot published
Triggers3

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Contact Yes No Create a new contact with email and contact fields from your Systeme.io account, with optional tags
Add Tag to Contact Yes No Assign a tag to an existing contact - select an existing tag or create a new one
Remove Tag from Contact Yes No Remove a tag that is currently assigned to an existing contact
Find Contact by Email Yes No Locate an existing contact by email address
Update Contact Yes No Update fields (name, phone, custom fields) of an existing contact using fields from your Systeme.io account
New Contact Yes No webhook trigger declared by the pinned package.
New Sale Yes No webhook trigger declared by the pinned package.
New Tag Added to Contact Yes No webhook trigger declared by the pinned package.

Triggers

New Contact · Webhook

Fires when a new contact is created

New Sale · Webhook

Fires when a new purchase is made within a funnel

New Tag Added to Contact · Webhook

Fires when a specific tag is assigned to a contact

Setup

Setup

  1. Add the Systeme.io connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-systeme-io@0.1.9; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 5 actions and 3 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Runtime execution evidence is managed separately from package metadata.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Systeme.io connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-systeme-io@0.1.9 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com