Available Automations Actions

Step

Overview

Special Cases

Example Use Cases

Pause a campaign for the user

Pauses an ongoing email campaign for the specific user who triggered the automation.

The email campaign system only allows a campaign to be sent to each account once. 

If the campaign is already paused, nothing happens.

When a campaign email is clicked, stop the campaign.

Pause a campaign for the account

Pauses an ongoing email campaign for the account and all users and contacts associated with it.

The email campaign system only allows a campaign to be sent to each account once. 

If the campaign is already paused, nothing happens.

When an opportunity is closed for the account, stop the “Prompt First Contact” campaign

Send a campaign to the user

Starts an email campaign for the specific user who triggered the automation.

The email campaign system only allows a campaign to be sent to each account once. 

If the campaign is already paused, nothing happens.

When a user is interested in a product, start an email campaign advertising the product.

Send a campaign to the account

Starts an email campaign for the account and all users and contacts associated with it.

The email campaign system only allows a campaign to be sent to each account once. If it has already been sent, nothing happens.

An error occurs when a campaign is sent to an account without users. This can be seen in the activity log.

When Website Pro is activated, send the “How to Use Website Pro” campaign

Create a fulfillment task

Creates a task in Task Manager. The fulfillment agent (a person assigned to the task) may be the default agent or a specific individual.

If the assigned agent does not exist, no one will be assigned.

When the “Design a Business Card” product is activated, assign the partner’s primary business card designer.

Create a fulfillment project

Creates a project in Task Manager. The project will be created based on the selected template.

If Task Manager is not active, it will be activated. If this action is twice in a single workflow, this will result in a rejected activation.

When the Website product is activated, create the Website Builder project from the Website Builder template

Add the account to a list

Adds the account to a list.

If the account is already on the list, nothing happens.

When a payment fails, add the account to the “Overdue Payments” list

Remove the account from a list

Removes the account from a list.

If the account is not on the list, nothing happens.

When an email campaign does not receive a response, remove the account from the “Responsive Accounts” list.

Notifications

Send a notification to the user

Sends an in-app and email notification to an account group user. Supports generic notifications (in app or email) as well as targeted notifications (e.g. abandoned shopping cart)

Consider using the generic send user notification action instead once taken out of draft as this is more flexible.

There is only limited support for items that can be used within {{ braces }}.

When a shopping cart is abandoned, send a notification in an hour.

Notify a digital agent

Sends both an in-app and email notification to a fulfillment agent.

Consider using the generic send notification actions instead once taken out of draft as these are more flexible.

There is only limited support for items that can be used within {{ braces }}.

When a website design product is activated a fulfilment agent who can design websites is notified.

Notify a partner admin

Sends both an in-app and email notification to a fulfillment agent.

Consider using the generic send notification actions instead once taken out of draft as these are more flexible.

There is only limited support for items that can be used within {{ braces }}.

When a high-income product is deactivated, notify partner administrators so they can investigate.

Notify a salesperson

Sends both an in-app and email notification to a salesperson.

Consider using the generic send notification actions instead once taken out of draft as these are more flexible.

There is only limited support for items that can be used within {{ braces }}.

When an opportunity is created for a French-language client, notify French-fluent salespeople.

Notify the user

Sends a notification to an account group user. Supports generic notifications (in app or email) as well as targeted notifications (e.g. abandoned shopping cart)

There is only limited support for items that can be used within {{ braces }}.

When a shopping cart is abandoned, send a notification in an hour.

Products

Activate a product

Activates a product for the account.

Only free tier LBOT products are currently allowed to avoid accidental billing. This may change in the future.

When an account is added to the “Wants a Website” list, activate Website Express.

Deactivate products

Deactivates a product(s) for the account.  The product can be turned off immediately or at the end of the current billing cycle.

Unlike activate, this can deactivate any product.

When a trial period ends, deactivate the trial product.

Sales

Assign a sales team

Assigns a random salesperson from the indicated sales team to the account. If the account already has a salesperson, they can optionally be replaced.

When a trial product is activated, assign a salesperson from the team responsible for that product.

Assign a salesperson

Assigns a specific salesperson to the account. Multiple individuals from across multiple teams can be selected, in which case, one will be randomly assigned. If the account already has a salesperson, they can optionally be replaced.

When a highly technical product is activated, assign a highly knowledgeable salesperson.

Log activity and hotness rating

Logs a business activity and increases the hotness rating (if the existing rating is lower than the new level).

Hotness ratings cannot be decreased using this step. This is to ensure that manually assigned high-hotness ratings are not accidentally downgraded.

When an email campaign is clicked, mark the account as a hot lead.

Create a sales task

Creates a task for a salesperson. The salesperson can be a specific individual or the default person assigned to the account.

If there is no assigned salesperson no one will be assigned to the task.

When an email campaign is clicked, create a task to follow up on that lead.

Unassign salespeople

Removes all salespeople from the account.

None

When an opportunity is closed, remove all salespeople from the account.

Tags

Add tags

Adds a tag to an account. New tags can be specified as well.

When creating a new tag the tag name must be selected from the dropdown list that appears, much like the user would for any other tag.

If the tag is already on the account it will not be added again.

When an account is added outside of the partner’s city, tag as “Remote Client”

Remove tags

Removes a tag from an account.

If the step is removing a tag that does not yet exist (e.g. one specified in “Add Tags”) it will not appear in the dropdown list. It can, however, be specified manually.

If the step is removing a tag that does not yet exist (e.g. one specified in “Add Tags”) it will not appear in the dropdown list. It can, however, be specified manually.

Delays

Delay until an event happens

Allows a workflow to pause and wait for an additional trigger for a specified amount of time. The time can be specified in minutes, hours, or days.

Like an if-else branch, delay-until steps have an EVENT HAPPENED and EVENT DID NOT HAPPEN branch (equivalent to the YES and NO branches, respectively). The delay-until step also merges after these branches.

If the automation is switched off mid-delay, the workflow will instantly stop. No steps after the delay will be executed.

When an account is added, wait for seven days for a product to be activated. If a product is activated, mark as a hot lead. If a product was not activated, send an email campaign. After either branch completes, remove the account from the “New Accounts” list.

Delay

Allows a workflow to pause. This is useful when actions that caused a trigger take time to fully complete, e.g. populating a Snapshot Report. The time can be specified in minutes, hours, or days. 

If the automation is switched off mid-delay, the workflow will instantly stop. No steps after the delay will be executed.

When a Snapshot Report is created, wait two days for the report to populate then send an email campaign about the report’s contents.

Conditions

If/else branch

Adds a decision point, allowing the workflow to split into YES and NO workflows. The workflow may “merge” back together after the branches complete.

The conditions that can be specified in the if/else branch are the same as those in a trigger’s condition (trigger filter)

If no steps exist in a branch that is followed, the automation will still count as having been run for an account. If the user is trying to run the automation only when a specific set of conditions is true for the first time, specify these in the trigger’s condition (trigger filter) 

When a Canadian account is added, check the location. If the location is in a French-speaking region (YES branch), assign a French-speaking salesperson. Otherwise (NO branch) assign an English-speaking salesperson. After either branch completes (merge step) add the account to the “Canadian Clients” list

Workflow

A/B Branch

Adds a split to the events moving through an automation so that you can run an experiment based on a percentage of those events

You’ve created 2 onboarding campaigns and want to see which one performs better. The trigger is Account Created, then set up an A/B Branch of 50%/50% and on each one of those branches, you can start the different campaigns.