Resources · Make integration

Tarvent Make integrationAutomate Tarvent with Make.

Your Tarvent contacts, forms and campaigns can talk to the rest of your tools. The Tarvent Make integration offers 36 modules, including 17 triggers, for marketers who run email in Tarvent. This page shows how to connect it and build a first working scenario.

Try the Tarvent integration on MakeSee the 36 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Tarvent Make integration do for you?

The Tarvent Make integration links your Tarvent account to Make so that events in Tarvent (a form answer, a click, an unsubscribe) start actions in other apps, and the other way round. You build a scenario, the automation made of modules, where each module is one brick: a trigger, an action or a search.

Leads that land in the right place. Watch Submitted Form picks up each form answer, Update a Contact Tag labels the person, and Add or Remove a Contact from a Journey places them in the right follow-up sequence. Nobody copies a list by hand.

A cleaner database across tools. Watch Unsubscribed Contacts and Watch Bounced Contacts report the people you should stop emailing, so your CRM or your shop can stop too. In the other direction, Create a Contact brings in buyers or sign-ups from any app Make reads.

Campaigns driven by real events. Generate a Custom Event tells Tarvent what happened elsewhere, and Send a Campaign or Start or Stop a Journey reacts when your shop, your calendar or your billing tool says so.

Two limits to know. All 17 triggers are scheduled, so Make checks Tarvent on the scenario's clock rather than being notified. Make's documentation also lists the modules by name only, so the notes below describe what each name promises: test with Run once before you rely on a result. For a wider view of the tool, read the Make review, and if you are still choosing a platform, the n8n vs Make comparison sets the criteria side by side. To learn the editor properly, there is also a Make training.

Connect

How do you connect Tarvent to Make?

  1. 01

    Collect your Tarvent credentials

    In Tarvent, open the account overview from the main menu and copy the account ID shown in the top right corner. Then go to the API keys section of your account settings, create a new API key and copy it. You need a Tarvent developer account for this.

  2. 02

    Add a Tarvent module in Make

    Log in to Make, open your scenario, add any Tarvent module and click Create a connection. A connection is your Tarvent account linked to Make once, then reused by every Tarvent module. You can give it a name in the Connection name field.

  3. 03

    Paste the credentials and save

    Enter the account ID and the API key you copied from Tarvent, or follow the instructions Make shows on screen, then confirm. Make now lists the Tarvent data it can read when you fill the module fields.

First scenario

Build your first scenario with Tarvent

GoalWhen someone submits a Tarvent form, Make tags the contact and adds them to a journey.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to add the first module. Search for Tarvent and pick Watch Submitted Form.

  2. 02

    Connect your account

    Click Create a connection and paste your account ID and API key. Once connected, fill the trigger fields; Make shows the Tarvent items it can read.

  3. 03

    Tag the contact

    Click the + on the right of the trigger and add Update a Contact Tag. Map the contact from the form bundle, the item passed from one module to the next, and set the tag.

  4. 04

    Send them into a journey

    Add Add or Remove a Contact from a Journey after the tag module, choose the add option and the journey that should welcome these new leads.

  5. 05

    Test with Run once

    Submit your form once yourself, then click Run once. Open the bubble above each module to read the bundles it received and check that the right contact got the tag.

  6. 06

    Schedule and switch on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Each module run on a bundle counts as one operation on your plan.

Triggers

Tarvent triggers in Make

17 modules start a scenario when something happens in Tarvent. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Tarvent as soon as it happens.

Tarvent1Watch Added Contact

Watch Added Contact

triggerIn the docs only

You get a bundle for every person newly added to your Tarvent contacts, ready to copy into a CRM, a spreadsheet or a welcome flow in another app.

How it fires
scheduled. Make checks Tarvent on the scenario's schedule and passes on the new contacts it finds.
When to use it
your sales team works in another tool and wants each new subscriber there without exporting lists.
Watch out
on the Free plan the shortest gap between two checks is 15 minutes, so a contact can wait that long before anything moves.
Tarvent2Watch Added Contact Note

Watch Added Contact Note

triggerIn the docs only

Notes your team writes on a Tarvent contact can travel to the place where colleagues will actually read them: a CRM timeline, a support channel, a shared sheet.

How it fires
scheduled. Each time the scenario runs, Make asks Tarvent for contact notes added since the previous check.
When to use it
an account manager logs a call summary in Tarvent and the sales lead wants it on the deal record.
Watch out
every note found becomes its own bundle, and each module that handles it uses an operation, the unit Make counts on your plan.
Tarvent3Watch Bounced Contacts

Watch Bounced Contacts

triggerIn the docs only

This trigger hands you the contacts whose emails bounced, so you can fix or flag a bad address instead of finding it later in a report.

How it fires
scheduled. Make looks for new bounces in Tarvent at the interval set on the first module.
When to use it
an online shop wants its customer file corrected when an address used for order emails turns out to be wrong.
Watch out
link it to Add a Contact to Suppression List only if you really want to stop mailing that person, since no module on this page takes someone off that list again.
Tarvent4Watch Clicked Contact

Watch Clicked Contact

triggerIn the docs only

Find out who clicked in your emails, person by person, and turn that interest into a follow-up in the tool your sales team already uses.

How it fires
scheduled. On every run of the scenario, Make pulls the clicks Tarvent recorded since the last check.
When to use it
a consultant wants a call task created in the CRM when a prospect clicks in a campaign.
Watch out
the same reader can click more than once, so add a filter or a lookup if you want a single follow-up per person.
Tarvent5Watch Contact Group Updated

Watch Contact Group Updated

triggerIn the docs only

You learn when a contact's group changes in Tarvent, which keeps the segments in your other tools in line with your email platform.

How it fires
scheduled. Make checks Tarvent for group changes each time the scenario's clock runs it.
When to use it
your events team keeps invitation lists in another app and needs them to mirror Tarvent groups.
Watch out
do not place Update a Contact Group in a scenario started by this trigger, or the change you make will be picked up again on the next run.
Tarvent6Watch Contact Status Updated

Watch Contact Status Updated

triggerIn the docs only

A status change on a Tarvent contact reaches your scenario as a bundle, so another system can react instead of waiting for someone to notice.

How it fires
scheduled. Make queries Tarvent on the scenario's schedule and returns the contacts whose status moved.
When to use it
your billing or member tool must reflect a change of status decided in Tarvent.
Watch out
the documentation gives no list of statuses, so run the trigger once with Run once and read the bundle before you map any value.
Tarvent7Watch Contact Tag Updated

Watch Contact Tag Updated

triggerIn the docs only

Tags are often how a marketing team marks interest, and this trigger lets that signal leave Tarvent for the tools where the next step happens.

How it fires
scheduled. Make checks for tag changes whenever the scenario runs, following the clock on the first module.
When to use it
a training company tags people interested in a workshop and wants the trainer's attendee sheet updated.
Watch out
a scenario started here that also runs Update a Contact Tag can set itself off again, so keep tag writing and tag watching in separate scenarios.
Tarvent8Watch Contact Updated

Watch Contact Updated

triggerIn the docs only

Any edit to a Tarvent contact record gives you a bundle, which is how you keep a second database aligned with Tarvent.

How it fires
scheduled. Make asks Tarvent for updated contacts at the pace of the scenario's schedule.
When to use it
both your CRM and Tarvent hold customer details and you want edits made in Tarvent copied across.
Watch out
if only tags, groups or status matter to you, the dedicated triggers on this page are more precise and will likely send fewer bundles, so fewer operations.
Tarvent9Watch Opened Contact

Watch Opened Contact

triggerIn the docs only

See which contacts opened your emails and feed that engagement into a lead score, a sales list or a follow-up task.

How it fires
scheduled. On each run, Make collects the opens Tarvent logged since the scenario last looked.
When to use it
a B2B team wants warm leads listed in a shared sheet after they open a campaign.
Watch out
opens can add up fast on a large list; place a filter right after the trigger so later modules, and their operations, only run for the contacts you care about.
Tarvent10Watch Performed Landing Page CTA

Watch Performed Landing Page CTA

triggerIn the docs only

Catch the visitors who acted on the call to action (CTA) of a Tarvent landing page and route them to the person who can answer them.

How it fires
scheduled. Make checks Tarvent for new CTA actions each time the scenario runs.
When to use it
a coaching business sends every CTA click on its offer page to the coach as a task in their planner.
Watch out
the doc lists no fields for this trigger, so look at a real bundle with Run once before you build the rest of the scenario.
Tarvent11Watch Replied Contact

Watch Replied Contact

triggerIn the docs only

Replies to your campaigns turn into bundles, so a real answer from a customer never sits unread in a mailbox nobody checks.

How it fires
scheduled. Make polls Tarvent for new replies on the scenario's schedule.
When to use it
a reply to your newsletter should open a ticket in your helpdesk or a message in the team chat.
Watch out
because checks are scheduled, a reply reaches your helpdesk on the next run, not the second it arrives; tell your team so nobody promises an immediate answer.
Tarvent12Watch Sent Campaign

Watch Sent Campaign

triggerIn the docs only

You get a record each time a campaign goes out from Tarvent, a clean starting point for reporting or for telling the rest of the company.

How it fires
scheduled. Make checks Tarvent for newly sent campaigns whenever the scenario's schedule comes around.
When to use it
a marketing lead logs every send in a planning sheet that sales and support read.
Watch out
if a later step needs more about the campaign than the trigger returns, add Search Campaigns after it and test what each module actually gives you.
Tarvent13Watch Sent Transaction

Watch Sent Transaction

triggerIn the docs only

Keep a trace, outside Tarvent, of every transactional email it sent: the one-to-one messages such as confirmations that your apps ask Tarvent to deliver.

How it fires
scheduled. Make asks Tarvent for sent transactional emails on each run of the scenario.
When to use it
support wants to check, inside its own tool, that a customer's confirmation really left.
Watch out
sent does not mean received; pair it with Watch Bounced Contacts when failed deliveries matter to you.
Tarvent14Watch Submitted Form

Watch Submitted Form

triggerIn the docs only

Every answer collected by a Tarvent form becomes a bundle you can route anywhere: a CRM, a sheet, a chat channel, a Tarvent journey.

How it fires
scheduled. Make checks Tarvent for new submissions on the scenario's schedule, every 15 minutes by default.
When to use it
a real estate agency wants each contact request from its form passed to the agent on duty.
Watch out
submit a test answer before you click Run once, otherwise the trigger has nothing to return and you have no data to map.
Tarvent15Watch Submitted Survey

Watch Submitted Survey

triggerIn the docs only

Survey responses leave Tarvent and land where decisions are made, for example a product team's feedback board or a manager's sheet.

How it fires
scheduled. Make pulls new survey responses from Tarvent each time the scenario runs.
When to use it
after a training session, the organiser wants satisfaction answers gathered in one sheet.
Watch out
each response is a separate bundle; add an aggregator, the Make module that groups bundles, if you want one summary instead of one row per answer.
Tarvent16Watch Transaction Created

Watch Transaction Created

triggerIn the docs only

You receive each new transactional message created in Tarvent, useful for an audit trail or for tracking what your apps ask Tarvent to send.

How it fires
scheduled. Make checks Tarvent for new transactions at the interval of the scenario.
When to use it
a software team logs every transactional message next to the customer record in its own database.
Watch out
judging by the names alone, this trigger follows creation while Watch Sent Transaction follows sending; run both once to see which fits your need.
Tarvent17Watch Unsubscribed Contacts

Watch Unsubscribed Contacts

triggerIn the docs only

Respect an unsubscribe everywhere: this trigger passes each opt-out to your other tools, so nobody keeps writing to that person from another app.

How it fires
scheduled. Make asks Tarvent for new unsubscribes on the scenario's clock.
When to use it
your CRM sends its own sequences and must stop when someone leaves your Tarvent list.
Watch out
the Free plan allows checks every 15 minutes at best; paid plans bring that down to 1 minute when the delay matters.
Modules

Tarvent actions and searches in Make

Tarvent gives you 19 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Tarvent1

Add a Contact to Suppression List

ActionIn the docs only

Stop Tarvent from emailing someone again by placing that contact on the suppression list straight from a scenario.

When to use it
a customer asks your support team to stop all emails, and the request arrives in the helpdesk rather than in Tarvent.
Watch out
treat it as a firm decision, because none of the 36 modules takes a contact off that list.
Tarvent2

Add or Remove a Contact from a Journey

ActionIn the docs only

Put a contact into a Tarvent journey, the automated path you design in Tarvent, or pull them out, based on what happened in another tool.

When to use it
a lead books a demo in your calendar app and should leave the nurturing journey.
Watch out
the same module does both moves, so check which option is selected before it runs on real contacts.
Tarvent3

Create a Contact

ActionIn the docs only

Add a new person to Tarvent from any source Make can read: a shop order, a webinar sign-up, a spreadsheet row.

When to use it
your webshop runs outside Tarvent and each buyer should join your audience.
Watch out
run Search Contacts first when the same email may already exist, so you do not end up with duplicates.
Tarvent4

Create an Audience Group

ActionIn the docs only

Open a new group in a Tarvent audience from a scenario, handy when your groups follow something that starts elsewhere, like a new event or product line.

When to use it
an events company opens a group for each event published in its ticketing tool.
Watch out
check with Search Audience Groups first, since creating the same group twice would split your contacts.
Tarvent5

Execute a GraphQL Query

ActionIn the docs only

Reach Tarvent data the other modules do not cover: as its name says, this module sends a GraphQL query you write yourself.

When to use it
no ready-made module fits your need and someone on the team is comfortable writing GraphQL.
Watch out
the documentation gives no example, so start with a query that only reads data and test it with Run once.
Tarvent6

Generate a Custom Event

ActionIn the docs only

Tell Tarvent about something that happened outside it, such as a finished course or a paid invoice, by sending an event you name yourself.

When to use it
your learning platform knows when a student completes a lesson, and Tarvent should know too.
Watch out
keep event names consistent, otherwise Search Custom Events will return a list nobody can read later.
Tarvent7

Search Audience Groups

SearchIn the docs only

Find the groups inside your Tarvent audiences, so a later module can work on the right one.

When to use it
before Update a Contact Group, when the group to use comes from a form answer in another app.
Watch out
a search returns zero, one or several bundles; add a filter so the next module does not run once per group found.
Tarvent8

Search Audiences

SearchIn the docs only

List the audiences in your Tarvent account, which matters when one account serves several brands or lists.

When to use it
an agency manages several client audiences in one Tarvent account and must pick the right one per client.
Watch out
when nothing matches, the search returns no bundle and the modules after it have nothing to work on.
Tarvent9

Search Campaigns

SearchIn the docs only

Look up campaigns already in Tarvent and reuse their details in a report, a dashboard or a note to your team.

When to use it
Watch Sent Campaign gives you too little and a report needs more about each campaign.
Watch out
several campaigns can match the same search, so decide which one counts before mapping anything.
Tarvent10

Search Contacts

SearchIn the docs only

Find a person in Tarvent before you create, update or tag them, so the scenario always works on the right contact.

When to use it
a form in another app sends an email address and you need to know whether that person already exists.
Watch out
each match is its own bundle, so with several matches the rest of the scenario runs once per contact.
Tarvent11

Search Custom Events

SearchIn the docs only

Check which custom events already exist in Tarvent, including those sent with Generate a Custom Event.

When to use it
before sending a new event, to reuse an existing name instead of creating a near duplicate.
Watch out
it is mostly a setup aid; inside a live scenario, every search still costs an operation on your plan.
Tarvent12

Search Journeys

SearchIn the docs only

Retrieve your Tarvent journeys so a later step can pick the one to start, stop or add a contact to.

When to use it
before Add or Remove a Contact from a Journey, when the journey depends on data from another tool.
Watch out
rename a journey in Tarvent and any filter built on its old name stops matching.
Tarvent13

Send a Campaign

ActionIn the docs only

Launch a Tarvent campaign from a scenario, at the moment an event in another tool says it is time.

When to use it
a product goes live in your shop and the announcement campaign is already prepared in Tarvent.
Watch out
an email that has gone out cannot be called back, so test the scenario on a test audience before you switch it on.
Tarvent14

Send a Transaction Email

ActionIn the docs only

Send one person a one-to-one email through Tarvent, such as a confirmation or a notice, when something happens in another app.

When to use it
your booking tool records an appointment and the client should get the confirmation from your usual sender.
Watch out
keep it for individual messages; for a whole list, Send a Campaign is the module built for the job.
Tarvent15

Start or Stop a Journey

ActionIn the docs only

Turn a whole Tarvent journey on or off from a scenario, without logging in to Tarvent.

When to use it
a promotion ends in your shop and the journey that pushes it should stop at the same time.
Watch out
it acts on the journey for everyone in it; to move a single person, use Add or Remove a Contact from a Journey.
Tarvent16

Update a Contact Group

ActionIn the docs only

Move a contact into the right Tarvent group when something changes outside your email tool.

When to use it
a customer upgrades their subscription in your billing tool and now belongs in the premium group.
Watch out
avoid it in a scenario started by Watch Contact Group Updated, because your own change would be picked up again.
Tarvent17

Update a Contact Notes

ActionIn the docs only

Write context onto a Tarvent contact, like a ticket outcome or a call summary, so marketers see it next to the email history.

When to use it
your helpdesk closes a ticket and its summary should follow the customer into Tarvent.
Watch out
run it once on a test contact to see whether it adds to the existing notes or replaces them.
Tarvent18

Update a Contact Status

ActionIn the docs only

Change a contact's status in Tarvent based on a decision taken in another system, so both tools tell the same story.

When to use it
your CRM marks a deal as lost and the contact's status in Tarvent should follow.
Watch out
the documentation lists no statuses, so try it on a test contact with Run once before mapping a value.
Tarvent19

Update a Contact Tag

ActionIn the docs only

Label a contact from a scenario, turning an answer or an action elsewhere into a tag your campaigns can target.

When to use it
a form answer shows interest in a specific workshop and that interest should become a tag.
Watch out
tags spelled differently become different tags, so map the value from a fixed list rather than free text.
Need help

Need help automating Tarvent with Make?

A person reads every message.

FAQ

Tarvent and Make: common questions

01Is the Tarvent Make integration free?
Yes. Tarvent is a standard app in Make, so you can use it on the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, lift the cap on active scenarios and allow 40 minutes per run, with usage counted in credits, meaning operations, each month. On the Tarvent side you need your own account; Tarvent's pricing page covers that subscription.
02What does connecting Tarvent to Make require?
A Tarvent developer account and an API key. In Tarvent, copy the account ID shown at the top right of the account overview, then create a new API key in the API keys section of your account settings and copy it too. In Make, add any Tarvent module, click Create a connection, name it if you like, and paste the two values. The connection is saved once and every Tarvent module in your scenarios reuses it, so you only do this setup a single time per account.
03Do Tarvent triggers in Make fire instantly?
No. All 17 Tarvent triggers are scheduled: Make checks Tarvent at the interval set on the first module of the scenario, every 15 minutes by default. On the Free plan 15 minutes is also the shortest possible gap, while paid plans go down to 1 minute. So a form answer or an unsubscribe reaches your other tools on the next run, not the second it happens. If that delay is a problem for a given use, shorten the schedule on a paid plan rather than looking for an instant trigger, which Tarvent does not offer in Make.
04What if a Tarvent module is missing in Make?
It depends on what you need. Tarvent has no Make an API Call module, so there is no generic request module to fall back on. The closest option is Execute a GraphQL Query, which lets someone comfortable with GraphQL ask Tarvent for data the other modules do not cover. If that is not enough, the missing step can sometimes be handled by another app in the same scenario. When neither route works, the help form at the bottom of this page puts you in touch with a Make specialist.
05Should Tarvent users pick Make or n8n?
It depends on your criteria rather than on a winner. On Make, Tarvent comes with 36 modules: 17 scheduled triggers, 13 actions and 6 searches, available from the Free plan, but without a generic API call module. Before choosing, list the Tarvent events and actions your process needs and check whether each platform covers them natively, then look at how each one counts usage against your volume. The n8n vs Make comparison linked above sets these criteria side by side without pushing one tool.
Same platform

Other docs you might need on this stack.

Browse all integrations