Content

Automation Rules revolve around specific triggers, or activities, that set each rule into motion. These actions occur based on the selected Automation Rule trigger, which is the activity that causes Leadcamp to fire the rule.

Each time you construct an Automation Rule, you will start by choosing a trigger. Then you will define the Automation Rule Criteria for how the Automation Rule will occur, followed by one or more desired actions.

Here is a complete list of the available Automation Rule triggers:

Here is a complete list of the available Automation Rules actions:


List of triggers

When a Heat Score reaches a certain level

Common use case: when a lead has meaningful activity, the Heat Score will reflect this by reaching a level above 70.

When a new Lead is created

Fires when a new lead is added in Leadcamp through manual actions or newly identified leads through content or emails.

Common use case: assign new leads to pre-sales SDR's, often in combination with Heat Score level criteria.

When a Lead is updated

Looks for a change in any Lead field in Leadcamp. This also includes any Salesforce fields that are mapped to a Lead field.

Common use case: to start a rule based on a field that is updated, such as a role change.

When a Lead is moved to a Pipeline Stage

Fires when a lead is moves from Pipeline Stage in the Pipeline View.

Common use case: syncing new leads only when they reach the MQL stage.

When there's content interaction

Fires when the lead interacts with content in general or a specific pre-defined piece of content.

Common use case: a lead has interactions with a specific piece of content such as a demo video or deck.

When there's email interaction

Fires when a lead has any email interaction, received an email, opened one or replied.

Common use case: push leads to your CRM only when they open your email multiple times (in combination with Criteria)

When there's link interaction

Fires when a lead has any link, or a specified link interaction.

When there's website interaction

Fires when a lead has general website interactions. For specific pages, see this trigger)

Common use case: often used in combination with Heat Score levels to filter on meaningful website activity.

Where there's meeting interaction

Fires when a lead has accepted or declined a meeting (or any of both).

Common use case: let sellers know instantly when a hot lead (in combination with Heat Score) declines a meeting

When there's specific web page interaction

Common use case: fire a trigger when a lead visits the pricing page.

When a tag is assigned

Fires when a certain tag is assigned to the lead.

Common use case: when a lead gets (e.g.) the tag "key account", it's assigned to a different seller

When a form is submitted

Fires when a form is submitted on your website.

Common use case: when a lead fills out a demo form on your website


List of actions

Move to stage

When the trigger is fired, the lead gets assigned to a specific Pipeline Stage.

Common use case: when a lead reaches a Heat Score of 70, it gets moved in the SQL stage.

Create recommendation

When the trigger is fired, a recommendation for the lead owners is generated.

Common use case: when the lead watches a pre-recorded demo, the pre-sale SDRs receive a recommendation to follow up.

Send email notification

When the trigger is fired, notify someone from the team about the activity.

Common use case: when the Heat Score reaches a certain level, make sure it isn't left unnoticed.

Assign to user

When the trigger is fired, assign or re-assign the lead to someone in the team.

Common use case: when specific activity happens, e.g. a demo form submission, assign the lead to the right seller.

Push to CRM

When the trigger is fired, push the lead to your CRM.

Common use case: not pushing all leads to the CRM but only the ones there's activate engagement with/from.

Create task

When the trigger is fired, create a personal task or reminder.

Common use case: don't lose your top leads out of sight and remind yourself with a recurring reminder task.

Archive lead

When the trigger is fired, the lead is archived.

Common use case: when the lead reaches the "closed" Pipeline Stage or is listed as unqualified.

Assign tag

When the trigger is fired, a tag is assigned to the lead.

Common use case: when a lead watches a video on your website or views a certain piece of content, you can assign a relevant tag to help you remember.

Did this answer your question?