About the Wix Automations Action Provider Service Plugin

The Action Provider service plugin allows you to implement an action that Wix users can add to automations on their sites. This means you can take actions in your service in response to events that happen on Wix sites or in the site dashboard. For example, in response to a trigger, your service can send an email, generate an invoice, or update another Wix service using its APIs.

The Action Provider service plugin lets you do the following:

• Invoke your action.
• Validate the input values to the action and return an error to the Wix user if they're invalid.
• Display the limits you enforce on the number of actions a Wix user can perform.

Before you begin

It’s important to note the following points before starting to code:

• Once you publish an app with a custom action, there are limitations to the changes you can make to the input schema you define when configuring your action. Learn more about editing a published input schema.
• Wix does not validate breaking changes to an input schema that uses composition. To ensure the user doesn't make errors when configuring an action that uses composition in its schema, we recommend performing the validation on your end.

Terminology

• Input schema: A JSON Schema object that defines the fields that Wix needs to pass to your service plugin methods. Learn more about the input schema.
• UI schema: The JSON schema that defines the UI for your action configuration in the user's site dashboard.

How to set up an action

To configure your action in your app's dashboard:

1. Select Automations from the left menu, then select Create New > Action.

2. Give your action a name. This is displayed to users when they add the action in the Automations UI.

   Notes:

   • Your action key is generated automatically from the action name. Once you save your action you cannot change the action key.
   • The action key is not displayed to users.

3. Add a short description explaining what your action does. The description is displayed to users when they select your action. This is an optional field.

4. Choose whether to hide the action, so it doesn't appear as an individual action on a user site. You should do this if the action is part of a pre-installed automation.

5. Under Service plugin endpoints, enter your base provider URI and select the service plugin methods you intend to implement.

6. Configure your input schema.

7. Optionally, configure your action's UI.

8. Save and test your action.

When a user installs your app, your actions become available for their automations, as shown here: