FlowRunner
PricingContact
Theme
Start Free

SALESmanago

Email Marketing

Connect AI agents to SALESmanago marketing automation. Agents upsert contacts, manage tags, and record external events like purchases and visits so campaigns respond to real customer behavior.

6 actions API key available
A new order completes in the storefront with a customer email attached
Get Contact checks whether the buyer already exists with tags, scoring, and opt-in status
Upsert Contact syncs name, phone, and company, preserving the existing opt-in state untouched
Add External Event records the purchase with its monetary value and product identifiers
Add Contact Tags applies the product-category tag that drives post-purchase automation
The agent verifies the event registered by re-reading the contact's profile
A marketing ops reviewer rules on any contact whose consent state is ambiguous before marketing touches them

What This Integration Enables

SALESmanago is a Customer Data Platform first and a campaign engine second: its automations, scoring, and segmentation are all functions of the behavioral data the profile holds. Starve it of events and it becomes an expensive email tool. FlowRunner agents keep the platform fed: they upsert contacts from every capture point, stream purchases, carts, and visits in as external events, and manage the tags that automations key on, so the campaigns marketing built inside SALESmanago respond to what customers actually did today. - Create or update contacts with tags and custom properties whenever a lead is captured anywhere - Feed purchases, carts, and visits in as external events with monetary values and product identifiers - Tag and untag contacts based on activity in other tools, keeping segments live - Look up full profiles, including scoring and opt-in status, by email - Page through the contact base for reporting and downstream sync Get Contact returning scoring and opt-in status alongside the profile is what makes closed-loop workflows possible: an agent can check what the platform currently believes about a contact before writing, verify after writing that the write took, and route on score thresholds the same way marketing does inside the platform. Multi-email lookup in a single call keeps reconciliation passes efficient even across large bases. SALESmanago is a European platform serving GDPR-governed audiences, and Upsert Contact writes marketing consent flags. That is exactly where FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) discipline plants itself: profile data moves freely, consent state moves only with proof.

Without FlowRunner

The CDP sees a fraction of behavior Purchases and visits happening outside SALESmanago never reach the profiles automations run on
Tagging is a batch job Segmentation tags get applied in monthly cleanups, so automations fire on stale membership
Consent state is fragile Imports and integrations quietly flip opt-in flags, and nobody notices until a complaint

With FlowRunner

Behavior streams into profiles Purchases, carts, and visits register as external events the hour they happen
Tags follow activity Contacts get tagged and untagged as they act, and automations fire on current truth
Consent changes are deliberate Opt-in flags change only with documented consent, and ambiguity goes to a person

Use Case Scenarios

The purchase that powers the automation

A [Shopify](/integrations/shopify) order lands. The agent upserts the buyer, then calls Add External Event with type Purchase, the order value, and product identifiers. Inside SALESmanago, the purchase updates scoring, moves the contact into post-purchase segments, and starts the win-back clock ticking from the right date. Marketing built those automations once; the agent makes sure every order, on every channel, actually reaches them, including phone orders and marketplace sales the tracking pixel never saw.

Form leads that arrive segmented

Responses come in from a [Typeform](/integrations/typeform) campaign. For each respondent, the agent calls Upsert Contact with the mapped fields and custom properties, then Add Contact Tags with the tags the answers earned: industry, interest level, campaign source, and anything else the form revealed. The contact enters SALESmanago already segmented, and the nurture automations keyed to those tags start on time instead of after the next manual import, which for a campaign-week lead is the difference between warm and cold.

The contact base reconciled weekly

Every Monday, the agent pages through List Contacts with an added-from window covering the prior week, appends each new contact's profile to [Google Sheets](/integrations/google-sheets), and posts a summary to [Slack](/integrations/slack). The same pass compares tags against the CRM's lifecycle stages and calls Add Contact Tags or Remove Contact Tags where the two systems disagree. Segment sizes in the Monday report match what the automations actually target, because the agent reconciled the two systems hours earlier, before anyone was awake to ask.

Human-in-Loop Highlight

Upsert Contact carries the flags that opt a contact into email and SMS marketing, and in a GDPR jurisdiction those flags are not preferences, they are legal records of consent. An agent that sets opt-in true while syncing a purchase has manufactured consent the customer never gave; one that silently sets it false has thrown away consent the company lawfully held. Both mistakes are invisible in the moment and expensive later. So FlowRunner agents treat consent fields as read-mostly: routine upserts sync names, phones, companies, and properties while leaving opt-in state exactly as found. The flag changes only when the workflow carries documented consent, a checked box on the form, a confirmed subscription event, and when provenance is ambiguous, the contact goes to a person with the evidence before any marketing automation is allowed to reach them. Profiles update at machine speed. Consent changes at the speed of proof.

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

6 actions

Contacts

3
  • Upsert Contact Creates or updates a contact matched by email, setting name, phone, company, tags, and custom properties, with optional create-only or update-only behavior and control of email and SMS opt-in. The consent-bearing write this page's human gate exists for.
  • Get Contact Retrieves full profiles for one or more emails in a single call: name, phone, tags, properties, scoring, and opt-in status. The read before any update or routing decision.
  • List Contacts Lists and paginates the contact base, filterable by an added-from and added-to window. The read behind reporting and reconciliation passes.

Tags

2
  • Add Contact Tags Adds tags to a contact by email, preserving existing tags, with an optional scoring weight. The write that keeps segments tracking behavior.
  • Remove Contact Tags Removes tags from a contact by email, ignoring tags not present. The cleanup that keeps automations from firing on expired membership.

Events

1
  • Add External Event Records a purchase, cart, visit, or other activity against a contact with optional monetary value, product identifiers, description, and detail fields. The feed that turns SALESmanago from an email tool into a behavioral platform.

Frequently Asked Questions

What can FlowRunner do with SALESmanago?

FlowRunner agents can run Upsert Contact, Get Contact, and List Contacts in SALESmanago, plus 3 more actions.

Does connecting SALESmanago to FlowRunner require OAuth?

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

Can SALESmanago trigger a FlowRunner workflow automatically?

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

Start building with SALESmanago

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