Quentn
Email MarketingConnect AI agents to Quentn, the German email marketing and automation platform, through its official API. Agents manage contacts and tags and trigger campaigns off events in the systems of record.
What This Integration Enables
Quentn is a German marketing automation platform, and the team running it works in German: the official API documentation Quentn publishes is German-language, and Get Users returns each account user's interface language and timezone alongside their roles. The connector is built against that documentation, and the platform is per-tenant, so the Base URL a workflow authenticates against is the same host the team logs in on. That is a small configuration detail with a real consequence: one FlowRunner account can drive several Quentn systems without any chance of a write landing in the wrong tenant.
What actually makes Quentn worth automating is that tags are not decoration. Quentn calls them terms internally, and campaigns use them as entry and exit conditions, which means adding a tag starts something and removing one stops it. An agent that manages tags is managing automation state, not metadata. The connector exposes that surface completely, alongside contacts with configurable duplicate detection, custom fields, reusable emails and Trigger Campaign for pushing a person into a campaign through a named API trigger element. FlowRunner agents can drive all of it, and the moments where a tag change would ripple through live campaigns are the moments where the flow stops and asks.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Tag hygiene that does not break a live campaign
An account accumulates tags. After a year of campaigns, nobody is sure which ones still matter. The agent calls Get Tags to pull every tag with its description and its deletion blocked flag, and immediately separates the protected ones, because Quentn refuses to delete a tag a live campaign depends on. The rest are candidates, and the agent posts them to the marketing channel with the campaign map the team maintains. Nothing is deleted by the agent's own judgement, because Delete Tag removes the tag from every contact that carries it and the API offers no way to count those contacts first.
Webinar registration into a campaign, with duplicates handled honestly
A registration lands from Zoom or Eventbrite. The agent calls Find Contacts By Email, which always returns an array, because Quentn permits several contacts to share one address. When exactly one record comes back, Add Contact Tags applies the webinar tag without disturbing the tags already there, and Trigger Campaign pushes the contact into the reminder sequence through that campaign's API trigger element. When more than one record comes back, the agent does not guess. It surfaces both records with their tags and comment timelines and lets a person say which one is the human being who registered.
A per-recipient email that a person still signs off
For a small, high-value announcement, the agent calls Create Email to build a reusable email with its own markers in the subject and body, retrieves it with Get Email to confirm the placeholders rendered as intended, and only then calls Send Email with the recipient list and per-recipient substitutions. Quentn caps a send at 1,000 recipients per request, so larger audiences are split across calls by the workflow rather than failing silently. Add Contact Comment writes the send and its outcome onto each contact's timeline, so the next person to open that record in Quentn sees what the automation did and why.
Human-in-Loop Highlight
Delete Tag is the sharpest edge in this connector, and the reason is not that it is destructive, it is that the agent cannot see what it is about to destroy. The tag disappears from every contact that carries it, and because Quentn campaigns use tags as entry and exit conditions, that silently changes who is inside a running sequence and who has just been let out of one. Quentn blocks deletion for tags a live campaign explicitly depends on, which catches the obvious cases, but the API reports no count of how many contacts carry a given tag, so an agent proposing a cleanup genuinely has no way to compute the blast radius before it commits.
So the flow stops there and hands over a case rather than an answer. It posts to the marketing channel: "Tag audit found 31 candidates. 9 are protected by a live campaign and were excluded. Of the remaining 22, these 4 appear in your campaign map as exit conditions: [list]. Delete the 18 unmapped tags, delete all 22, or review individually?" A marketing owner replies, and the human-in-the-loop step returns that choice to the flow, which runs Delete Tag only against what the person approved. The agent did the tedious half, the reading and the cross-referencing and the exclusion of the protected set. The half that changes who gets mailed next week belongs to someone who owns the campaigns.
Agent Capabilities
31 actionsContacts
10- Create Contact Creates a contact with built-in duplicate detection, requiring a valid email address or a full postal address. The duplicate check and merge behaviour are both configurable, so the same operation can behave as a create, an update or a safe upsert.
- Create Contacts In Bulk Creates many contacts in one request under the same duplicate rules, returning one result object per submitted record. Failed records carry an error flag and message, so a partial failure is visible rather than silent.
- Get Contact Retrieves a contact by its Quentn contact ID. Only the ID, name and email come back by default, so a workflow names the fields it actually needs rather than pulling everything.
- Find Contacts By Email Looks contacts up by email address, always returning an array because Quentn permits several contacts to share one address. This is how an email becomes the contact IDs every other operation requires.
- Update Contact Updates a contact by ID, writing only the values supplied. Standard fields, the email subscription status and custom field values can all change in one call, which makes it safe to run repeatedly with a partial payload.
- Delete Contact Permanently deletes a contact and the data attached to it. Used for deletion requests raised outside Quentn, with the correct record resolved by Find Contacts By Email first because it cannot be undone.
- Get Contact Comments Retrieves a contact's comment timeline with each entry's author and timestamps, paged in blocks and sortable oldest or newest first. This is the fastest way to surface recent notes when a workflow needs the human context on a record.
- Add Contact Comment Appends a note to a contact's timeline and returns the new comment ID. Agents use it to record the outcome of a call, a support interaction or an automated decision where the next person to open the record will see it.
- Update Contact Comment Rewrites the text of an existing comment, addressed by its comment ID. Quentn records the change timestamp so the edit remains visible in the timeline.
- Delete Contact Comments Deletes one or more comments from a contact's timeline. Used to strip notes that should not be retained, for example free text captured before a consent change.
Contact Tags
3- Get Contact Tags Retrieves the tags currently applied to one contact with their IDs, names and descriptions. Because tags drive campaign entry conditions, this is the quickest answer to why a person is or is not in a given flow.
- Add Contact Tags Adds tags to a contact without disturbing the ones already applied. This additive form is the correct way to tag from a workflow, since setting the whole terms field would silently remove everything else.
- Remove Contact Tags Removes specific tags from a contact and leaves the rest in place. Campaigns often use tags as exit conditions, so this is the usual way to take someone out of an automation without deleting their record.
Tags
5- Get Tags Retrieves the tags defined on the account with their IDs, descriptions and whether each is protected from deletion. Paged with a large default block, and the source of the IDs every tagging operation needs.
- Get Tag Retrieves one tag by numeric ID or by exact name. Lookup by name is useful when an external system only knows the human label, since Quentn tag names are unique and case sensitive.
- Create Tag Creates a tag, returning the existing tag's ID when the name is already taken rather than erroring. That behaviour makes it a safe find-or-create for workflows that tag on the fly.
- Update Tag Renames a tag or changes its description, writing only the values supplied. Renaming does not change which contacts carry it, so campaign entry conditions keep matching.
- Delete Tag Deletes a tag from the account and removes it from every contact that carries it. Tags a live campaign depends on are blocked from deletion, and everything else belongs behind a human decision.
Custom Fields
4- Get Custom Fields Retrieves every custom contact field with its internal name, label, description, type and whether it is mandatory. The returned field names are the keys the contact operations expect.
- Get Custom Field Retrieves a single custom field by numeric ID or internal field name. Used to confirm a field's type before writing to it, since Quentn validates types strictly on contact updates.
- Create Custom Field Creates a custom contact field, with the options depending on type: a maximum length for text, a display style and option set for selections, date or date and time for dates, and bounds for numbers. The internal name is generated from the label unless one is supplied.
- Delete Custom Field Deletes a custom field along with the values stored in it on every contact. This is destructive and irreversible, so the field's use should be confirmed before the call is made.
Campaigns
1- Trigger Campaign Pushes a contact into a campaign through an API trigger element, addressed by that element's numeric ID from its settings dialog. A full contact object creates or matches a person, or an existing contact ID pushes someone Quentn already knows.
- Create Email Creates a reusable email and returns its ID. Custom markers can be defined in the subject and body for per-recipient substitution at send time, and a context label such as Opt-In or Webinar Reminder is required so the email is classified correctly.
- Get Email Retrieves a stored email with its subject, HTML and plain text bodies, context label and default sender. The verification step before a programmatically created email reaches real recipients.
- Update Email Updates a stored email's subject, bodies, context label or default sender. Emails are reusable templates, so an edit changes what every future send of that email contains.
- Delete Email Deletes a stored email by ID. Used to clean up emails created programmatically for one-off sends so the template list stays readable.
- Send Email Sends a stored email to a list of existing contacts, with optional per-recipient placeholder substitution. A maximum of 1,000 recipients is allowed per request, so larger audiences are split across calls by the workflow.
- Get Senders Retrieves the sender addresses available for sending. Only confirmed senders are returned, which makes this the definitive list of valid sender IDs rather than a guess.
Users
2- Get Users Retrieves the account's users with their email, name, timezone, interface language, creation timestamp and roles. Used to resolve a contact owner into a real person, and to route an approval to someone in the right timezone.
- Get User Retrieves one account user by numeric ID or email address, including their roles. Checked before assigning contact ownership, so work is not routed to somebody without the permission to act on it.
Frequently Asked Questions
What can FlowRunner do with Quentn?
FlowRunner agents can run Create Contact, Create Contacts In Bulk, and Get Contact in Quentn, plus 28 more actions.
Does connecting Quentn to FlowRunner require OAuth?
No. Quentn connects to FlowRunner with an API key, no OAuth flow required.
Can Quentn trigger a FlowRunner workflow automatically?
Quentn doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Quentn
$100 in credits. No card required. Connect in minutes.