VERO n8n INTEGRATION: AUTOMATE VERO WITH N8N

This action serves as the foundation for any Vero automation workflow. It allows you to either create a new user in your Vero database or update an existing user's information—the system intelligently determines which operation to perform based on whether the user ID already exists.

Key parameters:

• Credential to connect with: Dropdown selection for your Vero account authentication—required to authorize the operation
• Resource: Set to "User" to indicate this action targets user data
• Operation: Set to "Create or Update" defining the dual-purpose nature of this action
• ID: Text field for the unique user identifier—accepts expressions for dynamic values
• JSON Parameters: Toggle to switch between structured fields or raw JSON input for complex data
• Additional Fields: Expandable section for custom user attributes like name, email, or any custom properties
• Data: Section for adding specific data items as key-value pairs

Use cases:

• Automatically create Vero users when they register on your platform via webhook
• Sync updated profile information from your CRM to Vero nightly
• Import users from a Google Sheet or Airtable base into Vero in bulk

Tagging users in Vero enables powerful segmentation for your email campaigns. This action lets you programmatically add one or more tags to any user, enabling dynamic audience building based on behavior, preferences, or any criteria you define.

Key parameters:

• Credential to connect with: Dropdown for selecting your Vero account credentials—required
• Resource: Preset to "User" indicating the target entity type
• Operation: Set to "Add Tags" specifying the tagging action
• ID: Text input for the user's unique identifier—required to target the correct user
• Tags: Text field where you specify tags to add—required, accepts comma-separated values or expressions

Use cases:

• Tag users as "premium" when they upgrade their subscription
• Add a "webinar-attendee" tag when someone registers for an event
• Apply product interest tags based on pages viewed or actions taken

The inverse of adding tags, this action removes specified tags from a user profile. Essential for maintaining accurate segmentation when user status changes or when cleaning up outdated classifications.

Key parameters:

• Credential to connect with: Authentication dropdown—required
• Resource: Set to "User" for user-targeted operations
• Operation: Set to "Remove Tags" defining the removal action
• ID: Text input for user identification—required
• Tags: Text field listing tags to remove—required, supports dynamic expressions

Use cases:

• Remove "trial-user" tag when someone converts to paid
• Clean up campaign-specific tags after a promotion ends
• Remove "inactive" tag when a user returns and engages again

User aliases in Vero allow you to update a user's identifier without losing their historical data. This action is particularly valuable when migrating from temporary IDs (like anonymous visitor IDs) to permanent ones (like account IDs after signup).

Key parameters:

• Credential to connect with: Vero account credential selection—required
• Resource: Set to "User" as this operates on user records
• Operation: Set to "Alias" specifying the alias modification
• ID: Text field for the current user ID you want to change—required
• New ID: Text field for the new alias ID to assign—required

Use cases:

• Convert anonymous visitor IDs to registered user IDs upon signup
• Update user identifiers when migrating to a new ID scheme
• Merge user records by aliasing duplicate accounts

When users who previously unsubscribed want to receive your emails again, this action re-enables their subscription status. Critical for win-back campaigns and GDPR-compliant preference management.

Key parameters:

• Credential to connect with: Authentication credential dropdown—required
• Resource: Set to "User" indicating user-level operation
• Operation: Set to "Re-Subscribe" defining the resubscription action
• ID: Text input for the user ID to resubscribe—required

Use cases:

• Automatically resubscribe users who click a "subscribe again" link
• Re-enable subscriptions for users who complete a double opt-in flow
• Batch resubscribe users imported from a preference center update

This action removes a user from your Vero mailing list while preserving their profile data. Essential for honoring unsubscribe requests, managing email preferences, and maintaining compliance with email regulations.

Key parameters:

• Credential to connect with: Vero account credentials—required
• Resource: Set to "User" for user operations
• Operation: Set to "Unsubscribe" specifying the unsubscription
• ID: Text field for the user ID to unsubscribe—required

Use cases:

• Process unsubscribe requests from your app or support system
• Automatically unsubscribe users who haven't engaged in 12 months
• Honor bulk unsubscribe requests from a preference management form

The most destructive action available, this permanently removes a user and all their data from Vero. Use with caution—typically reserved for GDPR "right to erasure" requests or cleaning test data.

Key parameters:

• Credential to connect with: Authentication dropdown—required
• Resource: Set to "User" indicating the target resource type
• Operation: Set to "Delete" specifying permanent removal
• ID: Text input for the user ID to delete—required

Use cases:

• Honor GDPR deletion requests automatically from your privacy dashboard
• Clean up test users after QA cycles
• Remove churned users after a defined retention period

Event tracking forms the backbone of behavioral email marketing in Vero. This action sends custom events to Vero, enabling you to trigger automated emails based on specific user actions like purchases, feature usage, or milestone achievements.

Key parameters:

• Credential to connect with: Vero account credential—required
• Resource: Set to "Event" indicating event-type operations
• Operation: Set to "Track" specifying event recording
• ID: Text input for the user ID associated with the event
• Email: Text field for user's email address
• Event Name: Text input for the event identifier (e.g., "purchase_completed")—critical for triggering automations
• JSON Parameters: Toggle for switching to raw JSON input
• Data: Section for adding event-specific properties as key-value pairs
• Extra: Section for metadata or additional context

Use cases:

• Track "purchase_completed" events with order value and product details from Stripe
• Record "feature_activated" events when users enable specific functionality
• Log "milestone_reached" events for onboarding progress emails