FlowRunner
PricingContact
Theme
Start Free

Tarvent

Email Marketing

Tarvent is a marketing automation platform built around audiences and journeys. Agents manage contacts, groups and segments, run campaigns and journeys, send transactional email, work with forms, surveys and landing pages, and export data through the GraphQL API.

Verified 78 actions API key available
Tarvent website Platform Documentation Capability data verified 2026-08-19
A pricing change means an active onboarding journey now teaches the wrong thing
Agent reads the journey with Get Journey and the affected audience with Get Audiences
Count Contacts sizes the selection before anything acts on it
Get Journey Contacts lists exactly who is part way through, and at which step
Agent posts the mid-journey population and the step distribution to the marketing channel
Agent confirms the replacement journey exists and its content is correct
A marketer chooses hard stop or soft stop, because that switch decides whether people mid-sequence are ejected or allowed to finish

What This Integration Enables

Tarvent is a GraphQL platform, and it does not soften that for you. One endpoint answers everything, including refusals, on HTTP 200. Introspection is disabled, so the schema cannot be explored at runtime. Everything hangs off an audience: contacts, groups, data fields, forms, campaigns, and journeys are all scoped to one. Groups and segments are the same object distinguished by a single flag, which means a segment's rules can be pasted straight into a bulk operation. The platform publishes several hundred queries and mutations, and rather than pretend a curated subset is the whole surface, this connector names the common ones and ships Run GraphQL as an honest escape hatch for the rest.

FlowRunner agents work that model directly: audiences and their data fields, contacts with tags and notes and custom events, the four-step campaign sequence from creation to schedule, journeys, transactional sending, templates, exports, and webhooks. The care goes into the places Tarvent gives you enough rope. Five bulk operations share a selection rule where contact IDs supersede a group and criteria, and where supplying none of the three selects the entire audience, so the connectors layer refuses an empty selection outright. Where a switch changes who gets swept up and the vendor supplies no default, FlowRunner does not invent one either. It asks.

Without FlowRunner

Selection rules with a dangerous default A bulk operation given no selector acts on the entire audience, and nothing about the call looks unusual
Errors that arrive as empty results A GraphQL endpoint answers 200 to refusals, so an unauthorized call reads as a contact who does not exist
Journeys stopped without knowing who is inside Ending a sequence means guessing how many people are part way through it

With FlowRunner

Selection sized before it is used Count Contacts runs first, and the connector refuses an empty selection rather than sending it
A refusal is a failed step The connector reads the errors array before the data, with the vendor's own path and code attached
The stop is an informed choice The agent shows who is mid-journey and at which step, and a person picks hard stop or soft stop

Use Case Scenarios

  • A campaign assembled through the sequence Tarvent actually requires

    Sending here is four steps, not one: create, update with content, mark ready, schedule. The agent walks that sequence, and on the update it treats list fields carefully, because omitting a field keeps it while sending an empty list clears it, and those are not the same instruction. Before scheduling, Get Domains confirms the sending domain is verified, which is the usual cause of a campaign that will not go out. Send Campaign Test puts the rendered message in a real inbox. The schedule itself takes an array of send times, one per variation, and Time Jumper decides whether everyone receives it at the same moment or at the equivalent local hour. Get Campaign Stats and Get Campaign Links then land in Snowflake for attribution work.

  • CRM state that reaches the audience without an export

    Deal stage changes in HubSpot reach the agent as they happen. It resolves the contact, calls Update Contact Tags to reflect the new stage, and uses Add Tag To Contacts for the cohort moves that affect many people at once. The replace operator on Update Contact Tags discards every tag the contact already has, so the agent uses it only when it genuinely means a full rewrite and adds tags individually otherwise. Create Contact Custom Event then records the stage change as a behavioral signal, which is what a journey trigger can watch for. Tags are addressed by name here rather than by ID, and Add Tag To Contacts creates a tag that does not exist yet, so a new stage does not need a setup step.

  • Meeting bookings that become a nurture without a manual import

    A booking in Calendly reaches the agent. Create Contact writes the invitee into the right audience, and the agent leaves the double opt-in bypass alone unless consent was genuinely captured on the booking form, in which case it records the opt-in timestamp and IP that make the bypass defensible. Add Contacts To Journey then enrolls them, with the selection expressed as explicit contact IDs rather than criteria so the blast radius is exactly the people who booked. Get Journey Contacts confirms the enrollment landed, and a summary posts to Slack.

Human-in-Loop Highlight

Stop Journey takes a hard stop flag that the schema requires and gives no default to, and that flag is the entire decision. A hard stop ejects the contacts currently part way through the journey. A soft stop lets them finish while admitting nobody new. Neither is safer in the abstract. If the journey is teaching people a price that changed this morning, letting them finish means mailing them something untrue. If the journey is a renewal sequence three steps from a payment prompt, ejecting them silently drops those renewals on the floor. The API will not choose, and neither should an agent.

So the agent gathers the facts nobody wants to gather by hand and hands over the choice. It posts: "Onboarding journey needs stopping after today's pricing change. 1,840 contacts are currently inside: 1,210 at step 2 of 6, which is the pricing email, and 630 past step 4, which they have already received. A replacement journey is built and ready to start. Hard stop and ejects everyone into the new journey, or soft stop and let the 630 finish?" A marketer answers in one message. Everything else on this page, including the four-step campaign sequence and every bulk selection, the agent handles on its own.

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

78 actions

GraphQL and Account

2
  • Run GraphQL Sends an arbitrary query or mutation to Tarvent's endpoint. The honest escape hatch for the several hundred operations this connector does not name individually.
  • Get Me Reads the authenticated account context. The cheapest confirmation that both required headers are in place.

Audiences

12
  • Get Audiences Lists the account's audiences. Every other object is scoped to one of these, so this is usually the first read in a workflow.
  • Get Audience Reads one audience. Its statistics recalculation switch is not free, so ordinary reads leave it off.
  • Create Audience Creates an audience, including the full postal address block that anti-spam law requires in every message.
  • Update Audience Updates an audience's settings.
  • Delete Audience Deletes an audience and everything scoped to it. Used only in teardown workflows with review.
  • Get Audience Groups Lists the groups and segments in an audience. Both are the same object, distinguished by whether membership is recalculated.
  • Get Audience Group Reads one group or segment with its criteria.
  • Create Audience Group Creates a static group or a dynamic segment. A dynamic group with no criteria matches nothing, which the connector refuses to create.
  • Get Audience Data Fields Lists an audience's custom data fields, including the merge tag campaign content references.
  • Create Audience Data Field Creates a data field. Its three required flags decide whether it is mandatory, whether it appears on signup forms, and whether it is treated as consent data.
  • Get Audience Imports Lists import jobs and their state.
  • Schedule Audience Import Schedules an import of previously uploaded file content. Its switches change contacts the file never mentions, which is why they are required rather than defaulted here.

Contacts

17
  • Get Contacts Reads contacts with the same condition group shape used by segments and bulk operations.
  • Count Contacts Counts what a selection resolves to without acting on it. The rehearsal step before any bulk operation.
  • Get Contact Reads one contact.
  • Create Contact Creates a contact. Its double opt-in bypass turns an unconfirmed address into a subscribed one, so it belongs only where consent was captured elsewhere and recorded.
  • Update Contact Updates a contact's fields.
  • Update Contact Status Changes a contact's subscription status.
  • Update Contact Tags Sets tags on one contact. The replace operator discards every tag the contact already has.
  • Delete Contact Deletes one contact.
  • Bulk Delete Contacts Deletes contacts by ID, group, or criteria. With none of the three the selection is the entire audience, which the connector refuses to send.
  • Add Contacts To Group Adds a selection of contacts to a group.
  • Remove Contacts From Group Removes a selection of contacts from a group.
  • Add Tag To Contacts Tags a selection of contacts, creating the tag if it does not exist. Tags are addressed by name rather than ID.
  • Remove Tag From Contacts Removes a tag from a selection of contacts.
  • Get Contact Events Reads a contact's event history, paged by page number rather than by cursor.
  • Get Contact Notes Reads the notes recorded against a contact.
  • Create Contact Note Writes a note on a contact. Used to leave the reason an agent did something where the next person will find it.
  • Create Contact Custom Event Records a custom event against a contact. It answers a bare boolean, so there is no event record to read back, and it can start a journey whose trigger watches for that key.

Campaigns

15
  • Get Campaigns Lists campaigns and their state.
  • Get Campaign Reads one campaign.
  • Create Campaign Creates a campaign. The first step of the four-step send sequence.
  • Update Campaign Sets a campaign's content and settings. Several list fields keep their value when omitted and clear when sent empty, which are different instructions.
  • Mark Campaign As Ready Marks a campaign ready to schedule.
  • Mark Campaign As Not Ready Returns a campaign to a not-ready state so it can be edited again.
  • Schedule Campaign Schedules the send. The send time is an array, one entry per variation, and the local-time option changes when each recipient receives it.
  • Pause Campaign Pauses a running campaign. The reversible one.
  • Resume Campaign Resumes a paused campaign.
  • Stop Campaign Stops a campaign permanently. Unlike pause, this one is final.
  • Delete Campaign Deletes a campaign.
  • Send Campaign Test Sends a test copy to named addresses. The rendering check before a schedule.
  • Get Campaign Stats Reads a campaign's performance figures.
  • Get Campaign Links Reads per link click data for a campaign.
  • Get Campaign Recipients Lists who a campaign was sent to. The answer to a support question about one recipient.

Journeys

8
  • Get Journeys Lists journeys and their state.
  • Get Journey Reads one journey's definition.
  • Create Journey Creates a journey.
  • Start Journey Starts a journey so it begins admitting contacts.
  • Stop Journey Stops a journey. Its required hard stop flag decides whether contacts part way through are ejected or allowed to finish, and it is the operation this page's human gate exists for.
  • Add Contacts To Journey Enrolls a selection of contacts into a journey.
  • Remove Contacts From Journey Removes a selection of contacts from a journey.
  • Get Journey Contacts Lists who is currently inside a journey and where. The read that makes a stop decision an informed one.

Transactional

4
  • Send Transaction Sends a transactional message built from header, content, recipients, and settings. The answer carries one row per recipient, so a partially refused send is not an error at the call level.
  • Get Transactions Lists transactional sends. Group name, tags, and metadata are set at send time and are what the reports group by.
  • Get Transaction Reads one transactional send.
  • Get Transaction Events Reads delivery and engagement events for a transactional send.

Templates

4
  • Get Templates Lists templates.
  • Get Template Reads one template.
  • Create Template Creates a template.
  • Delete Template Deletes a template. Campaigns referencing it stop resolving, so cleanup checks first.

Tags

4
  • Get Tags Lists the account's tags.
  • Create Tag Creates a tag.
  • Rename Tag Renames a tag by its old and new names rather than by an ID. Content and rules that reference the old name follow the rename.
  • Delete Tag Deletes a tag, changing who matches every rule that referenced it.

Assets and Exports

7
  • Get Domains Lists sending domains and their verification state. The usual explanation for a campaign that will not go out.
  • Get Forms Lists the audience's signup forms.
  • Get Surveys Lists surveys.
  • Get Landing Pages Lists landing pages.
  • Get SMS Campaigns Lists SMS campaigns and their state.
  • Get Exports Lists export jobs and their state.
  • Create Export Starts an export job. The route for moving Tarvent data into a warehouse on a schedule.

Webhooks

5
  • Get Webhooks Lists registered webhooks and their event filters.
  • Get Webhook Reads one webhook registration.
  • Create Webhook Registers a webhook against an entity and event pair.
  • Update Webhook Changes a webhook's target or filters.
  • Delete Webhook Removes a webhook registration.

Frequently Asked Questions

What can FlowRunner do with Tarvent?

FlowRunner agents can run Run GraphQL, Get Me, and Get Audiences in Tarvent, plus 75 more actions.

Does connecting Tarvent to FlowRunner require OAuth?

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

Can Tarvent trigger a FlowRunner workflow automatically?

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

Start building with Tarvent

Free plan, no card required. Connect in minutes.