---
title: "Voyado events"
description: "Events the Voyado integration handles and what each does."
sidebar:
  label: Events
---

The integration handles merchant user events, account automations, and optional back-in-stock signals. All Voyado contacts live under the configured API base URL and carry the custom fields described on the main page. When a store group list or market is configured, user events outside that scope are ignored.

## Merchant users

| Event | What Enad sends |
|---|---|
| User created | A Voyado contact create with email, names, language, phone, social security number, verified flag, communication preferences, address, and member terms, plus the custom fields and attributes documented on the main page. |
| User updated | A patch of the existing contact. Fields missing on the Enad side keep the values already stored in Voyado. |
| User deleted | With **Hard delete user** on, or for non-soft deletes, the contact is deleted. Otherwise it is anonymized: names, phone, social security number, address, and all communication preferences are cleared, the verified flag set to false, and the `accountDeleted` automation fired. |

Enad finds the contact first. It looks up an existing Voyado contact by email, phone number, or social security number, according to **User lookup strategy**, and the returned Voyado contact ID is stored on the Enad user and reused. A contact already linked to a different Enad user fails with a permanent error. When an identifier matches several contacts, the first one is used and the choice is logged.

## Automations

Each automation resolves the contact, by stored Voyado ID, then by email, and as a last resort creates it, and triggers a custom event. These are Voyado custom triggers by exact name, so automations in Voyado fire on these IDs:

| Event | Voyado trigger |
|---|---|
| Password reset | `resetPassword` with the password reset link |
| Email verification sent | `verifyEmail` with the verification token, fired both on sign-up and when a new verification email is requested |
| Email verified | `accountConfirmed` after verification, or `accountConfirmedThirdParty` for third-party sign-ups. Fires once; later verifications are skipped. |
| User deleted | `accountDeleted`, after the contact is anonymized |
| User activated | `userActivated` |
| User inactivated | `userInactivated` |
| Any other status | Nothing |

## Back in stock

| Event | What Enad sends |
|---|---|
| Stock change from zero or below to a positive quantity | A stock-level signal for the variant, with SKU and external ID. Requires **Sync back in stock**. |
| Any other stock change | Ignored, in both directions. |

## Field mapping

| Enad data | Voyado destination |
|---|---|
| Email, phone, language, names | Standard contact fields |
| Store group | `enadStoreGroup` custom field |
| Market | `enadMarket` custom field |
| Verified status | `enadVerified` custom field |
| Member terms acceptance | `memberTerms` custom field |
| Attributes | `attr_<template-key>` custom fields |
| Street address | `street` |
| Postal code | `zipCode` |
| City | `city` |
| Country | `country` |
| Consent toggles | `acceptsEmail`, `acceptsPostal`, `acceptsSms` |

## Related

- [Voyado](/integrations/voyado)
- [Voyado configuration](/integrations/voyado/configuration)