About the Wix Automations APIs

Wix Automations allow site collaborators to automate business processes. All Wix apps can provide automations to users.

Why are automations necessary?

As a site’s traffic increases, it becomes harder for the user to manage certain site actions on their own. For example, a user with an online store doesn’t have time to send invoices manually if they receive dozens of customer orders per day. Likewise, it’s too time-consuming for the owner of a fitness site to manually manage hundreds of new sign-ups daily.

Wix Automations remove the burden of handling these processes from site owners, by automating them. This leaves site owners free to focus on growing their business, instead of dealing with the details of various business operations.

Overview of automations

Every automation has a trigger, and at least one action. The trigger is an event that gets reported to Wix by an app. Below are some examples of events that can trigger an automation:

  • A customer submits a form.
  • A customer completes a purchase.
  • A site visitor navigates to a page.
  • A customer books a session.

When the app reports the event, it initiates the automation, which then carries out the actions. Each action is a single business operation that can receive data from the trigger. The following are examples of actions:

  • Send a confirmation email.
  • Generate an invoice.
  • Send a chat message.
  • Send booking data to a 3rd-party service.

Triggers and actions are the essential building blocks of automations. However, automations can also contain delays and conditions. Delays prevent an action from running for a some period of time after an event is reported. Conditions determine whether an action runs or not based on customizable logic. Delays and conditions allow users to build much more complex automations than what is possible with just triggers and actions.

With the Automations SDK, you can currently provide triggers to users.

Terminology

For a comprehensive glossary of Wix Automations terms, see Terminology.

Did this help?