Systeme.io
Overview
The Systeme.io integration lets you automatically subscribe users to your Systeme.io contact lists via supported form submissions. You can dynamically map custom contact fields, assign tags, and update existing contacts if they already exist.
🔧 Setup Instructions
To connect your Systeme.io account:
Go to your Systeme.io Dashboard.
Click Profile > Settings > Public API Keys.
Create a new API key or copy your existing one.
Paste the API key into the Systeme.io settings in AFI.
Once the API key is saved, it will appear in the dropdown during integration setup.
📥 Supported Actions
| Task | Description |
|---|---|
| Subscribe to List | Adds a contact to your Systeme.io account and optionally assigns tags |
🔁 Field Mapping
You can map the following fields when setting up the integration:
Email (required)
First name
Last name
Phone
Country
Any custom contact fields defined in your Systeme.io account
⚠️ Note: Systeme.io imposes a 255 character limit for each custom field. Submissions with longer text will result in an error (422 - Unprocessable Entity). It’s recommended to limit long-text fields in your form settings.
🏷️ Tags
If tags exist in your Systeme.io account, you can map a tag field and pass the correct Tag ID from the form data. The contact will be automatically tagged after creation or update.
Example format:Event Volunteer: 123456, Premium Subscriber: 654321
Use one tag ID at a time during runtime. Only the ID will be passed to the API.
🔄 Contact Update Logic
If a contact already exists with the provided email:
AFI will update the contact with the new mapped field values
Then it will assign any tag if provided
If the contact does not exist:
A new contact will be created using the mapped data
🧪 Troubleshooting
Make sure all mapped fields are valid and do not exceed character limits.
If you see a
422error in AFI logs, check for:Long text fields (above 255 characters)
Invalid tag ID
Country name not matched to a valid ISO code
To test, try creating a new form integration with minimal fields like only email and a valid tag ID. Once that works, incrementally add more fields and test each time.
