Defines a single operation that should happen as part of the automation logic. Examples of actions include sending an email, generating an invoice, or updating another Wix service. The action provider is required to define an input schema for the action to run. The action may also return an output schema that can be used in the following automation steps.
An automated process that consists of a trigger and at least one action. Complex automations can also contain delay and condition building blocks. Automations on a site can either be created by users, or installed by apps.
Criteria that allow the creation of complex logic in the automation flow. A condition determines whether the steps that follow it should be executed or not. Conditions can also include an else path, which specifies what action or set of actions should be taken if the initial conditions are not met.
For example: A site automation is triggered when a customer makes a table reservation. The condition checks if the party size is greater than 8. If true, the site owner receives a notification. Else, a confirmation email is sent to the guest email.
A time period that is intentionally inserted between two steps in the automation flow. It can serve the logic of an automation that is built in phases, such as a drip campaign or reminders for a specific event.
An event is anything that happens in the provider's service. A provider can choose to report to Wix any event that occurs. When an event is reported, it activates any automations that use the related trigger. A reported event contains a payload that meets the schema requirements defined by the app that created the trigger.
Only the apps that own the trigger can call Report Event to initiate the trigger.
An event can be a real-time event or a scheduled event.
A JSON schema that defines the inputs an action requires to run. These inputs can either be dynamic values taken from the previous automation step (such as a trigger payload or another action's output schema), or static values filled in by the user. Read about the action input schema to learn more.
A JSON schema that defines the data an action outputs when it executes. The next step in the automation flow can use this data.
A JSON schema that defines the data reported to Wix when an event occurs. Developers are required to define a payload schema when they create a trigger. Read more about the trigger payload schema.
The event that initiates the automated process. An event becomes a trigger when you choose to expose it by reporting it to Wix.
Examples of triggers include a site visitor submitting a form or a customer completing a purchase. The trigger contains relevant data in the form of a payload schema. The data can be used later in the automation flow. In the automation builder, triggers are segmented into categories and apps, and users can select them out of the trigger catalog.