Triggers are a helpful automation tool within Insites that help you to save time and connect Insites to other products or services.
A trigger is made up of an event (the thing that causes the trigger to fire) and an action (the thing you want to happen as a consequence).
Very simply put: when A happens, do B.
Here are some examples of triggers you could set up:
When an audit is generated & they don't have Google Ads -> Add an ads product to the proposal
When an audit completes -> Push the data to your CRM
When a lead generates an audit -> Email your sales inbox
How to access Triggers
Triggers can be added from your account settings. To access this:
Click your profile icon top right, from any page
Select Account Settings from the drop-down menu
Choose API & Integrations from the top menu
Choose Triggers from the left menu
Adding a trigger
Hit add a new trigger and you'll be walked through the steps to add a trigger. The trigger builder is broken down into 5 steps:
Event - what should cause this trigger to run
Rules - should this trigger only fire under specific circumstances
Actions - what should we do when the trigger is fired
Config - name the trigger, so you can identify it later
Confirm - review the selections you've made and confirm creation of the trigger
Selecting an event
The first panel will ask you to select the event that will cause your trigger to run. Currently available triggers are:
On completion of a business report - this will fire when ANY report is generated in your account, whether via a sales agent, batch or via the lead generation widget
On completion of a lead gen report - this will fire for lead generation reports that are generated
On form completion on a lead gen report - if you have a secondary data collection form on your lead generation report, this event will fire when that form is submitted
On share of a report via email - this will fire when a report is shared by any user via email
You can optionally add a delay for the trigger. This will mean that the action will be triggered some time later. An example of how you might use this is as follows: when a report is shared via email, 2 days later send a follow up email.
If you want your trigger to apply every time the event occurs, you can skip this step.
If, however, you would like to control when the trigger applies (e.g. only when the audit finds broken links, or only when the audit finds the website is slow) then you can use our rule builder to ensure the trigger only fires when your criteria are met.
Right now the following actions are provided:
Add a product to the proposal - Use this to automate the creation of proposals based on the contents of the audit
Send an email notification - Use this to send an email to a customer as a follow-up, or a notification to your sales team
Post data to a URL - Use this to push the data into other systems, or cause other follow-up actions to occur
You can add multiple actions to occur for one trigger (e.g. when this trigger fires, send me an email AND post the data to my CRM).