Vero Integration

Customer engagement platform for event-driven email and messaging campaigns. Turn Vero engagement into automated marketing workflows that keep leads and audiences moving. Start with Watch Bounced, then use Get Broadcast and Get Broadcast Content to trigger the next step.

Explore Documentation

3-day trialCancel anytimeUp to 10 minutes quick set up

GDPR
Data Encryption
2FA
Local Data Region

Supported triggers and actions for Vero integration

Triggers can detect changes in Vero and run actions that can create, search or modify data inside Vero automatically [3] — exactly how you set them.

Watch BouncedTriggers when an email bounces and is not delivered.
Watch ClickedTriggers when a customer clicks a link in an email.
Watch ComplainedTriggers when a customer marks an email as spam.
Watch ConvertedTriggers when a customer converts on a campaign.
Watch DeliveredTriggers when an email reaches the recipient's mail server.
Watch FailedTriggers when an email could not be sent because of an error.
Watch OpenedTriggers when a customer opens an email.
Watch ResubscribedTriggers when a customer subscribes again after unsubscribing.
Watch SentTriggers when Vero sends an email.
Watch UnsubscribedTriggers when a customer unsubscribes.
Watch User CreatedTriggers when a user profile is created through the API or an import.
Watch User UpdatedTriggers when a user profile is updated through the API or an import.
Get BroadcastReturns a single broadcast, including archived ones.
Get Broadcast ContentReturns one localized content of a broadcast message, including its body.
Get Broadcast MessageReturns a single message of a broadcast.
Get CampaignReturns a single legacy campaign by its ID.
Get Campaign ContentReturns one localized content of a legacy campaign message, including its body.
Get Campaign MessageReturns a single message of a legacy campaign.
Get JourneyReturns a single journey with its trigger and full step graph.
Get Journey ContentReturns one localized content of a journey message, including its body.
Get Journey MessageReturns a single message step of a journey without its content body.
Get TopicReturns a single preference center topic.
List Broadcast ContentsRetrieves the localized contents of a broadcast message, default content first.
List Broadcast MessagesRetrieves the messages of a broadcast, one per A/B test variation.
List BroadcastsRetrieves a list of broadcasts, newest first.
List Campaign ContentsRetrieves the localized contents of a legacy campaign message, one per locale.
List Campaign MessagesRetrieves the messages of a legacy campaign, one per A/B test variation.
List Journey ContentsRetrieves the localized contents of a journey message, default content first.
List Journey MessagesRetrieves the message steps of a journey with their sender and content summaries.
List JourneysRetrieves a list of journeys, most recently updated first.
List TopicsRetrieves a list of preference center topics.
Cancel User SubscriptionUnsubscribes a user from all messages sent by Vero.
Change User IdentifierChanges the identifier of an existing user, merging the two identities.
Create BroadcastCreates an unscheduled draft broadcast, optionally with the content of its first message.
Create Broadcast ContentAdds a localized version of a draft broadcast message, copied from its default content.
Create Broadcast MessageAdds an A/B test variation to a draft broadcast by copying its control message.
Create Campaign ContentAdds a localized version of a legacy campaign message, copied from its default content.
Create Journey ContentAdds a localized version of a journey message, copied from its default content.
Create TopicCreates a preference center topic that users can subscribe to.
Delete UserPermanently deletes a user together with all of their properties and activity.
Edit User TagsAdds tags to a user and removes tags from them in one step.
Identify UserCreates a user profile in Vero, or updates it when the user already exists.
Make an API CallPerforms an arbitrary authorized request to the Vero Campaigns API.
Set User SubscribedResubscribes a user who previously unsubscribed from all messages.
Track EventRecords an event for a user, creating the user profile if it does not exist yet.
Update BroadcastUpdates the name, labels or channel of a broadcast.
Update Broadcast ContentUpdates the subject, body or other details of a localized broadcast content.
Update Broadcast MessageUpdates the sender, reply address or active state of a message in a draft broadcast.
Update Campaign ContentUpdates the subject, body or other details of a localized legacy campaign content.
Update Journey ContentUpdates the subject, body or locale of a localized journey content.
Update TopicUpdates the name, description or default status of a preference center topic.

How to integrate Vero in automation workflow?

3 simple steps to make your Vero connected with other apps in automation workflows on WEXTL. Up to 10 minutes integration set up.

STEP 1

Select Vero in workflow

Pick Vero app in the workflow builder [4] - just one click to select the app.

STEP 2

Connect Vero

When prompted, authorize access to Vero in WEXTL once. Vero credentials are encrypted and never shared with WEXTL. Authorization will be reused in any future API calls [3].

WEXTL wants to integrate with your Vero account. Approve?

STEP 3

Build a workflow

Build your workflow with Vero yourself or with WEXTL® AI Builder. Connect Vero to any available integrations [5], or use HTTP node to go beyond them.

Vero

How Vero connects and integrates with WEXTL

Save and approve your credentials once — WEXTL® stores authorization information encrypted and reuses the authentication whenever Vero app is called in workflows. That allows your marketing automations to run without your attention, per defined schedule [7]. Explore documentation [6] for a detailed list of fields that Vero supports.

Full Vero API documentation

The following table illustrates what fields Vero integration require during authorization flow inside our workflow builder [4].

Demonstration of Vero connection step inside WEXTL Workflow Builder [4].

Field	Type	Help
Auth TokenRequired	password	Your project's Track API auth token (called a Tracking API Key in Vero 2.0), from Settings > Project > API Keys > Tracking Keys. It is sent as the auth_token query parameter. To check the token, saving this connection identifies a reserved user with the ID wextl-verify in your project, creating that profile the first time.

Connect Vero to popular apps on WEXTL

Enter a name of the other app you want to sync with Vero below. Click on selected app to explore integration options with Vero. If the app you search for is not available in WEXTL yet, you can use HTTP node [10] instead to integrate it directly.

Example automation with Vero integration

Select Watch User Created trigger from Vero - this will be a starting point in your automation. Whenever event happens in Vero, workflow will start [7] from Watch User Created node.

Search for Cancel User Subscription, connect it as the next step of integration sequence. You can use filters between Watch User Created and Cancel User Subscription, so only important data pass from Watch User Created to the next step. WEXTL gives you full control over the process of Vero automation. All parts of workflow are visible on the canvas [4].

Vero on WEXTL has 51 modules for combining marketing automations. Explore Vero documentation for more.

Vero

Watch User Created

Bloomreach

Performs action

Bloomreach

Triggers

Vero

Cancel User Subscription

Demonstration of how visual Vero automation [6] looks in WEXTL.

Frequently asked questions

Common questions about automating Vero in your workflows.

Vero has 12 triggers, including "Watch Bounced", "Watch Clicked", and "Watch Complained", and more. Triggers are start points of the workflow, and automations may start from them.

Integration has 39 actions, including "Get Broadcast", "Get Broadcast Content", and "Get Broadcast Message", and more. Refer to our Vero Documentation for detailed inputs and outputs.

No. Most automations are built visually on the canvas by picking triggers, actions, and mapping fields. You can add custom JavaScript with Functions when advanced logic is needed — but our customers do that in rare cases [4].

Yes. Connections are authenticated per account, credentials are encrypted at rest, and you can enforce approvals and team-level access controls on any automation.

The Vero integration on WEXTL runs directly on its vendor public API — every field name, authentication method, and rate limit is controlled by Vero official API and covered in documentation [3]. WEXTL handles the request signing and pagination for you.

Absolutely. Where Vero provides native webhooks, you can use instant triggers to eliminate polling delay. For custom webhooks, WEXTL offers Custom Webhook node, so you can start automation whenever Vero or any other service sends event to webhook URL.

WEXTL is an AI-first visual canvas. The platform allows you to describe automation in plain text — and AI will wire nodes for Vero inside the workflow builder [4]. You can also use built-in workflow nodes (AI Agent, Human in the Loop, Condition, Aggregate Results) in pair with Vero modules to craft complex integration flows with branches, filtering, and conditional logic. There are absolutely no limits of what you can build.

References

List of sources used to gather information about the Vero integration.

Vero integration source code, module specs and credentials implementation.
Internal Vero integration documentation, structured input and output parameters, scopes, and authentication methods.
Official Vero vendor API documentation — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
WEXTL® Visual Workflow Builder, anonymized data from our technical support team.
WEXTL® Apps Library
WEXTL® Vero App Documentation
WEXTL® Workflow Scheduler
WEXTL® HTTP node documentation

Vero Integration

Supported triggers and actions for Vero integration