Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Vero

Vero is an event-based messaging platform. Increase conversions and customer satisfaction by sending more targeted emails.

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

Overview

Connect Vero with Flows360

Vero is an event-based messaging platform. Increase conversions and customer satisfaction by sending more targeted emails.

Use the Vero 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 7 actions and 11 triggers.

Available actions

  • Alias a User
  • Create or Update User
  • Delete User
  • Resubscribe User
  • Track Event
  • Unsubscribe
  • Update User Tags

Available triggers

  • Email Bounced
  • Email Clicked
  • Email Complained
  • Email Converted
  • Email Delivered
  • Email Opened
  • Plus 5 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: Vero
  • Package: @activepieces/piece-vero@0.1.7
  • Exact artifact digest: sha256:e14f035b0d7bd0b0e81e716b555d6c4cc86811fe94b9d75383ed49f1568674ec
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

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

Action contracts

  • Alias a User (aliasAUser), Change a user's identifier by merging two user identities into one Classification: read.
  • Create or Update User (createOrUpdateUser), Create a new user profile or update an existing user profile with custom properties Classification: read.
  • Delete User (deleteUser), Delete a user and all their properties and activities permanently. This action is irreversible. Classification: read.
  • Resubscribe User (resubscribeUser), Globally resubscribe a user to all communications Classification: read.
  • Track Event (trackEvent), Track a custom event for a user Classification: read.
  • Unsubscribe (unsubscribe), Globally unsubscribe a user from all communications Classification: read.
  • Update User Tags (updateUsersTags), Add or remove tags from a user profile Classification: read.

Trigger contracts

  • Email Bounced, webhook.
  • Email Clicked, webhook.
  • Email Complained, webhook.
  • Email Converted, webhook.
  • Email Delivered, webhook.
  • Email Opened, webhook.
  • Email Sent, webhook.
  • New User, webhook.
  • Resubscribe User, webhook.
  • Unsubscribe User, webhook.
  • Update User, 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 objects18
Supported actions7
Triggers11

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Auth Token Required · protected credential

Supported objects

ObjectReadWriteNotes
Alias a User Yes No Change a user's identifier by merging two user identities into one
Create or Update User Yes No Create a new user profile or update an existing user profile with custom properties
Delete User Yes No Delete a user and all their properties and activities permanently. This action is irreversible.
Resubscribe User Yes No Globally resubscribe a user to all communications
Track Event Yes No Track a custom event for a user
Unsubscribe Yes No Globally unsubscribe a user from all communications
Update User Tags Yes No Add or remove tags from a user profile
Email Bounced Yes No webhook trigger declared by the pinned package.
Email Clicked Yes No webhook trigger declared by the pinned package.
Email Complained Yes No webhook trigger declared by the pinned package.
Email Converted Yes No webhook trigger declared by the pinned package.
Email Delivered Yes No webhook trigger declared by the pinned package.
Email Opened Yes No webhook trigger declared by the pinned package.
Email Sent Yes No webhook trigger declared by the pinned package.
New User Yes No webhook trigger declared by the pinned package.
Resubscribe User Yes No webhook trigger declared by the pinned package.
Unsubscribe User Yes No webhook trigger declared by the pinned package.
Update User Yes No webhook trigger declared by the pinned package.

Supported actions

Alias a User · Read

Change a user's identifier by merging two user identities into one

alias_auser · Risk: low · Retry: safe

Inputs

  • id · string · Required, The old unique identifier of the user
  • new_id · string · Required, The new unique identifier of the user
Create or Update User · Read

Create a new user profile or update an existing user profile with custom properties

create_or_update_user · Risk: low · Retry: safe

Inputs

  • id · string · Required, The unique identifier of the user
  • email · string · Required, The email address of the user
  • data · object · Optional, Custom user properties (e.g., first_name, last_name, timezone). Reserved properties: language, timezone, userAgent
  • channels · array · Optional, Device tokens for push notifications and other communication channels
Delete User · Read

Delete a user and all their properties and activities permanently. This action is irreversible.

delete_user · Risk: low · Retry: safe

Inputs

  • id · string · Required, The unique identifier of the user to delete
Resubscribe User · Read

Globally resubscribe a user to all communications

resubscribe_user · Risk: low · Retry: safe

Inputs

  • id · string · Required, The unique identifier of the user
Track Event · Read

Track a custom event for a user

track_event · Risk: low · Retry: safe

Inputs

  • userId · string · Required, Unique database identifier for the user
  • userEmail · string · Required, Email address of the user
  • eventName · string · Required, Name of the event being tracked
  • eventData · object · Optional, Event-specific data and properties
  • extras · object · Optional, Additional metadata for the event (e.g., source, createdAt)
Unsubscribe · Read

Globally unsubscribe a user from all communications

unsubscribe · Risk: low · Retry: safe

Inputs

  • id · string · Required, The unique identifier of the user
Update User Tags · Read

Add or remove tags from a user profile

update_users_tags · Risk: low · Retry: safe

Inputs

  • id · string · Required, The unique identifier of the user
  • add · array · Optional, An array of tags to add to the user
  • remove · array · Optional, An array of tags to remove from the user

Triggers

Email Bounced · Webhook

Triggered when an email bounces

Inputs

  • instruction · string
Email Clicked · Webhook

Triggered when an email is clicked

Inputs

  • instruction · string
Email Complained · Webhook

Triggered when an email is marked as complained

Inputs

  • instruction · string
Email Converted · Webhook

Inputs

  • instruction · string
Email Delivered · Webhook

Inputs

  • instruction · string
Email Opened · Webhook

Triggered when an email is opened

Inputs

  • instruction · string
Email Sent · Webhook

Inputs

  • instruction · string
New User · Webhook

Triggered when a new user is created

Inputs

  • instruction · string
Resubscribe User · Webhook

Inputs

  • instruction · string
Unsubscribe User · Webhook

Inputs

  • instruction · string
Update User · Webhook

Inputs

  • instruction · string

Setup

Setup

  1. Add the Vero 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:
  • No provider credential fields are declared by the pinned package.
  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-vero@0.1.7; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 7 actions and 11 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 Vero 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-vero@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