skip to Main Content

Managing Actions

  1. Home
  2. Knowledge Base
  3. Getting Started
  4. Managing Actions

An “action” is the output of an Uncanny Automator recipe. It’s what the plugin does after the trigger conditions have been satisfied. An action might include anything from sending an email to setting a tag in Infusionsoft to enrolling a user in a remedial course on an educational website.

Watch a Video Demo

Adding Actions to your Recipe

Choose a Recipe Integration

To get started with a new action, choose the plugin that includes an action you want to trigger. If you want to send an email or perform another system task not associated with a plugin, choose WordPress. The integrations that are listed here will be different depending on what plugins Automator detects are installed (by plugin folder) and by whether or not the Pro version of the plugin is enabled.

Choose a Recipe Action

After choosing a plugin, a list of available actions for that integration is displayed. Choose the action here that you want to execute after the trigger conditions are met. Any text in blue indicates that a variable needs to be populated in the next step (and in the case of emails being sent, a lot of conditions must be set). These blue values are called “tokens” and are explained more in the next section.

Set a Recipe Condition

After choosing an action, any required conditions or variables can be set. If a value is needed, it will be displayed in a blue box in the action line. Click the blue box and enter appropriate values.

Available tokens for Uncanny Automator

 

Using tokens in actions

Some actions include the ability retrieve personal details and other variables from the WordPress database. We call these variables “tokens” in the Automator plugin. In the example above, you can see how the email fields can optionally include things like the admin email address for the site or the user’s email address. Since you will want to personalize recipes and the user experience across the site, these tokens allow significant customizations in your recipes and ensure that recipes are very flexible. Using tokens is highly recommended for emails in particular.

The list of available tokens depends on what triggers are included in a recipe. If the recipe includes a form submission as a trigger, for example, we make tokens available for things like the form name and the contents of form fields. This allows you to pass data from triggers into actions, like including a user’s job title that was captured in a registration form available in an email sent to the site admin about a new user.

Back To Top