Automations are no-code workflows that run on a Wix site when a configured event happens. They connect a real-world event to the response that follows it. For example, a new contact being added on the site can trigger a welcome email, with no code involved. Wix ships a library of built-in automations, and you can extend that library with custom triggers and actions.
Automations follow a trigger-action model:
- Triggers and actions. A trigger is an event reported to Wix when something happens on a site. An action is the work that runs in response, using data from the trigger as input. A single automation pairs 1 trigger with 1 or more actions.
- When triggers fire. Triggers can fire in real time, as soon as the event occurs, or on a schedule relative to a future moment, such as 24 hours before a booking. When a trigger's data references a Wix contact, the platform can attach the full contact record so downstream actions can use it. Wix users can also configure filter conditions to limit when an automation runs.
- How actions work. Actions declare the input they need, and Wix generates a configuration UI from that declaration. An action can also return data for later actions in the same automation to consume.
- Built-in and custom automations. The built-in automation library covers common scenarios, with triggers like new contacts and completed orders, and actions like sending emails and pushing notifications. Custom triggers and actions add new entries to this library. Apps can additionally ship pre-installed automations that are wired up on a site automatically when the app is installed.
The development path determines how you interact with automations:
- Sites: Wix users can build automations in the site's dashboard. From a site's backend, you can publish a custom trigger that fires an automation from any backend code, and a custom action that runs when an automation reaches that step.
- Wix-managed headless projects: Don't extend automations. To react to the same events from a headless backend, subscribe to Events or orchestrate work in an external automation tool that calls Wix APIs.
- Self-managed headless projects: Don't extend automations. To react to the same events from a headless backend, subscribe to Events or orchestrate work in an external automation tool that calls Wix APIs.
- Wix-managed apps: Can add custom triggers, custom actions, and pre-installed automations to the automations library, and these become available to every site that installs the app. The backend behind these extensions can be built with the CLI or self-hosted. Blocks-only apps can't include automation extensions.
- Self-managed apps: Can add custom triggers, custom actions, and pre-installed automations to the automations library, and these become available to every site that installs the app. The backend behind these extensions can be built with the CLI or self-hosted. Blocks-only apps can't include automation extensions.
- Blocks apps: Don't include automation extensions.