Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Tarvent

Tarvent is an email marketing, automation, and email API platform that allows to you to send campaigns, manage contacts, automate your marketing, and more.

CategoryMarketing
Authenticationcustom
Version0.1.7
Published scopes0 published scopes
Last updatedSeptember 24, 2026

Overview

Connect Tarvent with Flows360

Tarvent is an email marketing, automation, and email API platform that allows to you to send campaigns, manage contacts, automate your marketing, and more.

Use the Tarvent connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 18 actions and 17 triggers.

Available actions

  • Create/Update Contact
  • Add/Remove Contact Tag
  • Add/Remove Contact From Audience Group
  • Add Note To Contact
  • Add/Remove A Contact From A Journey
  • Subscribe/Unsubscribe Contact From Audience
  • Create An Audience Group
  • Start/Stop Journey
  • Plus 10 additional declared actions.

Available triggers

  • Contact Added
  • Contact Added Or Removed From A Group
  • Contact Profile Updated
  • Contact Status Changed
  • Contact Tag Added Or Removed
  • Contact Note Added
  • Plus 11 additional declared triggers.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Tarvent
  • Package: @activepieces/piece-tarvent@0.1.7
  • Exact artifact digest: sha256:25dcd1bf77381f2ca40e28549ec05c2b182f2af6d6728b7ec772214baab4995a
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create/Update Contact (tarvent_create_contact), This action is used to create or update a contact in an audience. Classification: read.
  • Add/Remove Contact Tag (tarvent_update_contact_tag), Adds or removes a tag from contact. Classification: read.
  • Add/Remove Contact From Audience Group (tarvent_update_contact_group), Adds or removes a contact from an audience group. Classification: read.
  • Add Note To Contact (tarvent_create_contact_note), Adds a note to a contact. Classification: read.
  • Add/Remove A Contact From A Journey (tarvent_update_contact_journey), Adds or removes the contact from a journey. Classification: read.
  • Subscribe/Unsubscribe Contact From Audience (tarvent_update_contact_status), Subscribes or unsubscribe a contact in an audience. Classification: read.
  • Create An Audience Group (tarvent_create_audience_group), Creates an audience group in the selected audience. Classification: read.
  • Start/Stop Journey (tarvent_update_journey_status), Starts or stops a journey. Classification: read.
  • Send A Transactional Email (tarvent_create_transaction), Sends a transactional email. NOTE: This will use your email API credits. Classification: read.
  • Send Campaign (tarvent_send_campaign), Sends a copy of a campaign. Classification: read.
  • Generate A Custom Event (tarvent_generate_custom_event), Generate a custom event in your Tarvent account. Classification: read.
  • Find Audience (tarvent_get_audiences), Finds an audience by name or tags. Classification: read.
  • Find Audience Group (tarvent_get_audience_groups), Finds an audience group by name. Classification: read.
  • Add Contact To Suppression List (tarvent_create_suppression_filter), Creates a suppression filter in your account to suppress a contact. Classification: read.
  • Find Campaign (tarvent_get_campaigns), Finds a campaign by name, status or tags. Classification: read.
  • Find Contact (tarvent_get_contact), Finds a contact by your custom key data field (typically this is by email). Classification: read.
  • Find Custom Event (tarvent_get_custom_event), Finds a custom event by name. Classification: read.
  • Find Journey (tarvent_get_journey), Finds a journey by name, status or tags. Classification: read.

Trigger contracts

  • Contact Added, webhook.
  • Contact Added Or Removed From A Group, webhook.
  • Contact Profile Updated, webhook.
  • Contact Status Changed, webhook.
  • Contact Tag Added Or Removed, webhook.
  • Contact Note Added, webhook.
  • Contact Unsubscribed, webhook.
  • Form Submission Received, webhook.
  • Landing Page CTA Performed, webhook.
  • Survey Submission Received, webhook.
  • Campaign Or Transactional Link Clicked, webhook.
  • Campaign Or Transactional Email Opened, webhook.
  • Contact Replied, webhook.
  • Campaign Or Transactional Email Bounced, webhook.
  • Campaign Sent, webhook.
  • Transaction Created, webhook.
  • Transaction Sent, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects35
Supported actionsNot published
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Account ID Required
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create/Update Contact Yes No This action is used to create or update a contact in an audience.
Add/Remove Contact Tag Yes No Adds or removes a tag from contact.
Add/Remove Contact From Audience Group Yes No Adds or removes a contact from an audience group.
Add Note To Contact Yes No Adds a note to a contact.
Add/Remove A Contact From A Journey Yes No Adds or removes the contact from a journey.
Subscribe/Unsubscribe Contact From Audience Yes No Subscribes or unsubscribe a contact in an audience.
Create An Audience Group Yes No Creates an audience group in the selected audience.
Start/Stop Journey Yes No Starts or stops a journey.
Send A Transactional Email Yes No Sends a transactional email. NOTE: This will use your email API credits.
Send Campaign Yes No Sends a copy of a campaign.
Generate A Custom Event Yes No Generate a custom event in your Tarvent account.
Find Audience Yes No Finds an audience by name or tags.
Find Audience Group Yes No Finds an audience group by name.
Add Contact To Suppression List Yes No Creates a suppression filter in your account to suppress a contact.
Find Campaign Yes No Finds a campaign by name, status or tags.
Find Contact Yes No Finds a contact by your custom key data field (typically this is by email).
Find Custom Event Yes No Finds a custom event by name.
Find Journey Yes No Finds a journey by name, status or tags.
Contact Added Yes No webhook trigger declared by the pinned package.
Contact Added Or Removed From A Group Yes No webhook trigger declared by the pinned package.
Contact Profile Updated Yes No webhook trigger declared by the pinned package.
Contact Status Changed Yes No webhook trigger declared by the pinned package.
Contact Tag Added Or Removed Yes No webhook trigger declared by the pinned package.
Contact Note Added Yes No webhook trigger declared by the pinned package.
Contact Unsubscribed Yes No webhook trigger declared by the pinned package.
Form Submission Received Yes No webhook trigger declared by the pinned package.
Landing Page CTA Performed Yes No webhook trigger declared by the pinned package.
Survey Submission Received Yes No webhook trigger declared by the pinned package.
Campaign Or Transactional Link Clicked Yes No webhook trigger declared by the pinned package.
Campaign Or Transactional Email Opened Yes No webhook trigger declared by the pinned package.
Contact Replied Yes No webhook trigger declared by the pinned package.
Campaign Or Transactional Email Bounced Yes No webhook trigger declared by the pinned package.
Campaign Sent Yes No webhook trigger declared by the pinned package.
Transaction Created Yes No webhook trigger declared by the pinned package.
Transaction Sent Yes No webhook trigger declared by the pinned package.

Setup

Setup

  1. Add the Tarvent connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • Account ID (accountId), required.
  • API Key (apiKey), required; stored as a sensitive connection value.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-tarvent@0.1.7; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 18 actions and 17 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Tarvent connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-tarvent@0.1.7 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com