FlowRunner
PricingContact
Theme
Start Free

Systeme.io

Email Marketing

Connect AI agents to Systeme.io, the all-in-one marketing platform. Agents sync contacts, assign and remove tags to trigger automations, enrich records through custom contact fields, and manage the contact list end to end.

9 actions API key available
Systeme.io website ↗ Platform Documentation ↗ Capability data verified 2026-07-28
A new buyer completes checkout in the storefront
List Contacts filters by exact email to see whether the buyer already exists
Create Contact adds the buyer with name and order details in custom fields
Update Contact patches the existing record instead when a match is found
Agent selects the segment tag based on what was purchased
Tag assignments that will drop the contact into a live email automation get confirmed by the list owner when the mapping is new or ambiguous
Assign Tag places the contact into the post-purchase sequence
The marketing channel logs who entered which sequence, from which source

What This Integration Enables

Systeme.io compresses the whole funnel stack, pages, emails, courses, automations, into one tool, and the contact record is the hub everything routes through. Tags are not labels there; they are triggers. Assign a tag and an automation fires, emails send, a course unlocks. That makes the contact list the control panel of the business, and this integration hands FlowRunner agents the controls: creating and enriching contacts from every system that meets a customer, and assigning the tags that set Systeme.io's machinery in motion. - Sync new leads and customers from forms, stores, and spreadsheets into the contact list - Assign and remove tags to trigger automations and keep segments current - Enrich contacts through custom fields, with slugs discovered at runtime from List Contact Fields - Look up, update, and remove contacts as part of broader marketing and CRM workflows Because a tag is a trigger and a delete is forever, the writes here are exactly where FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) step belongs. The connector is also schema-aware by design. Custom fields in Systeme.io are account-specific, so agents call List Contact Fields at runtime and map incoming data to the slugs that actually exist, rather than assuming a fixed shape. When a source system adds a field the account does not have, the mismatch surfaces as a flagged exception instead of a silently dropped value, which is the difference between a sync you trust and one you audit quarterly.

Without FlowRunner

Funnels only see funnel traffic Buyers from the store and respondents from surveys never enter Systeme.io unless someone imports them
Tagging is manual, so segmenting is optional Contacts arrive untagged, sit in no automation, and get the generic newsletter or nothing
The contact list decays quietly Bounced, unsubscribed, and duplicate contacts accumulate with no owner for cleanup

With FlowRunner

Every channel feeds the machine Stores, forms, and spreadsheets create or update contacts within minutes, custom fields populated
Tags route people automatically Each source assigns its segment tag on entry, and Systeme.io's own automations take it from there
List hygiene is a supervised sweep Agents surface bounced and duplicate contacts with evidence, and a person approves what gets removed

Use Case Scenarios

Buyers enter the post-purchase sequence the same hour

An order lands in [Shopify](/integrations/shopify). The agent checks List Contacts by email, creates or updates the contact with the buyer's name and product in custom fields, then calls Assign Tag with the product line's segment tag. Systeme.io's automation picks the contact up and runs the post-purchase sequence the marketer already built. The funnel tooling finally sees the customers who bought outside the funnel.

Survey respondents routed into the right nurture

A [Typeform](/integrations/typeform) survey asks what respondents are trying to accomplish. The agent creates each respondent with Create Contact, writes their answers into custom fields discovered via List Contact Fields, and assigns the nurture tag matching their stated goal. Three different answers route into three different sequences, automatically, with the mapping defined once and applied every time.

The audience report and the hygiene sweep in one pass

On a schedule, the agent pages through List Contacts, mirrors the audience into [Google Sheets](/integrations/google-sheets) for reporting, and posts the topline counts to [Slack](/integrations/slack). The same sweep filters for bounced and unsubscribed contacts and for duplicate emails, and files the findings as a cleanup proposal. Growth numbers and list hygiene stop being separate chores; both fall out of one scheduled pass.

Human-in-Loop Highlight

Delete Contact permanently removes a contact by ID, and the API offers no undo: the email history, tag assignments, and custom field record of that relationship are gone. The flow that needs it most is the one with the highest stakes, honoring an erasure request, where deleting the wrong numeric ID erases a different person's record while leaving the requester's data in place. So the FlowRunner erasure flow separates finding from destroying: the agent matches the request email via List Contacts, pulls the full record with Get Contact, and presents it, "Erasure request from [email protected]. Matched contact 48213, registered 2024-03-02, tags: customer, course-b. Confirm deletion." A person confirms the identity match, the agent deletes and logs the confirmation ID as compliance evidence. The same restraint applies at batch scale to Assign Tag, because in Systeme.io a tag assignment is a send button: the agent states which automation a tag will fire before a person approves a bulk assignment.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via email
Human decides
Agent resumes with decision

Agent Capabilities

9 actions

Contacts

5
  • List Contacts Retrieves contacts with filtering by exact email, tag IDs, bounced, unsubscribed, and needs-confirmation states, and registration date ranges, with cursor pagination. The matching and hygiene sweep in one operation.
  • Get Contact Retrieves one contact with email, custom field values, assigned tags, and registration metadata. The evidence step before updates and deletions.
  • Create Contact Creates a contact from an email plus custom field slug and value pairs. The intake write for every lead source.
  • Update Contact Patches a contact's custom fields by ID; only supplied fields change. The safe enrichment write.
  • Delete Contact Permanently deletes a contact by ID. Cannot be undone. The operation this page's human gate exists for.

Tags

3
  • List Tags Retrieves the account's tags with IDs and names. The lookup behind every segmentation decision.
  • Assign Tag Assigns a tag to a contact, which in Systeme.io commonly fires an automation. Treated as a send operation, not a label, in FlowRunner flows.
  • Remove Tag Detaches a tag from a contact without deleting the tag itself. Used to exit contacts from segments and sequences.

Contact Fields

1
  • List Contact Fields Retrieves the account's custom field definitions with slugs, names, and types. The schema discovery that keeps Create Contact and Update Contact writing valid data.

Frequently Asked Questions

What can FlowRunner do with Systeme.io?

FlowRunner agents can run List Contacts, Get Contact, and Create Contact in Systeme.io, plus 6 more actions.

Does connecting Systeme.io to FlowRunner require OAuth?

No. Systeme.io connects to FlowRunner with an API key, no OAuth flow required.

Can Systeme.io trigger a FlowRunner workflow automatically?

Systeme.io doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Systeme.io

$100 in credits. No card required. Connect in minutes.