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 prospect has meaningful activity, the Heat Score will reflect this by reaching a level above 70.
When a new Prospect is created
Fires when a new prospect is added in Leadcamp through manual actions or newly identified prospects through content or emails.
Common use case: assign new prospects to pre-sales SDRs, often in combination with Heat Score level criteria.
When a Prospect is updated
Looks for a change in any Prospect field in Leadcamp. This also includes any Salesforce fields that are mapped to a Prospect field.
Common use case: to start a rule based on an updated field, such as a role change.
When a Prospect is moved to a Pipeline Stage
Fires when a prospect moves from Pipeline Stage in the Pipeline Pipeline.
Common use case: syncing new prospects only when they reach the MQL stage.
When there's content interaction
Fires when the prospect interacts with content in general or a specific pre-defined piece of content.
Common use case: a prospect interacts with a specific piece of content, such as a demo video or deck.
When there's email interaction
Fires when a prospect has any email interaction, received an email, opens one or replies.
Common use case: push prospects to your CRM only when they open your email multiple times (in combination with Criteria)
When there's link interaction
Fires when a prospect has any link or a specified link interaction.
When there's website interaction
Fires when a prospect 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 prospect has accepted or declined a meeting (or any of both).
Common use case: let sellers know instantly when a hot prospect (in combination with Heat Score) declines a meeting
When there's specific web page interaction
Common use case: fire a trigger when a prospect visits the pricing page.
When a tag is assigned
Fires when a certain tag is assigned to the prospect.
Common use case: when a prospect 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 prospect fills out a demo form on your website
List of actions
Move to stage
When the trigger is fired, the prospect gets assigned to a specific Pipeline Stage.
Common use case: when a prospect reaches a Heat Score of 70, it gets moved to the SQL stage.
A recommendation for the lead owners is generated when the trigger is fired.
Common use case: when the prospect watches a pre-recorded demo, the pre-sale SDRs receive a follow-up recommendation.
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, ensure it isn't unnoticed.
Assign to user
When the trigger is fired, assign or re-assign the prospect to someone in the team.
Common use case: when specific activity happens, e.g., a demo form submission, assign the prospect to the right seller.
Push to CRM
When the trigger is fired, push the prospect to your CRM.
Common use case: pushing only some prospects to the CRM but only the ones there's activated engagement with/from.
When the trigger is fired, create a personal task or reminder.
Common use case: keep your top prospects in sight and remind yourself with a recurring reminder task.
When the trigger is fired, the prospect is archived.
Common use case: when the prospect reaches the "closed" Pipeline Stage or is listed as unqualified.
When the trigger is fired, a tag is assigned to the prospect.
Common use case: when a prospect watches a video on your website or views a certain piece of content, you can assign a relevant tag to help you remember.
Enroll is a cadence
When the trigger is fired, the prospect is enrolled in a specified cadence.
Common use case: when someone downloads a piece of content, you automatically follow up with emails.