Finish Actions are used to automate updates from Redirect Links, Hosted Files, Form Submissions, and List Emails to other records.
When a Prospect interacts with marketing material you send them, any Finish Actions you’ve setup will immediately make changes to their associated record, instead of forcing users to make updates manually.
If you have an AppConnect subscription, you can build Recipes to automate your Finish Action processes. Learn more.
Plans
Finish Actions are available to all Insightly Marketing users.
Set Up
When you open a Redirect Link, Hosted File, Form Submission, or List Email record:
Click the Finish Actions tab.
Click Add Finish Action.
Enter a name and fill out the action’s criteria.
Click Save Finish Action.
Types of Actions
Users can select the following Finish Actions, which will vary by object:
Name | Definition |
|---|---|
Send Email | An Email will be sent to the Prospect. The user building the Journey can choose which email and schedule the send date and time. |
Add Tags | Add tags to the Prospect. |
Remove Tags | Remove tags from the Prospect. |
Adjust Score | Increases or decreases the Prospect's score. |
Assign Owner | Assigns the Prospect record to another user. |
Change Field Value | Updates a field's information. For example, changing a Prospect's "Opted Out" field from unchecked to checked. |
Notify User | Sends a notification to a specified user. |
Add to Marketing List | Adds the Prospect to a specified List. |
Remove from List | Removes the Prospect from a specified List. |
Convert to Lead | Creates a Lead record in Insightly CRM for the Prospect. The Prospect record will still exist in Insightly Marketing. The two records will not share the same record ID. Users will be prompted to enter the Lead Status, Lead Owner, and Lead Source. |
| Convert to Contact | Creates a Contact record in Insightly CRM for the Prospect. The Prospect record will still exist in Insightly Marketing. The two records will not share the same record ID. |
Execute Lambda Function | Creates a trigger to execute a specific Lambda function. |
Fire Webhook | Fires or sends an outgoing HTTP POST webhook to an address specified in the action. |
Create CRM task | Creates a task in Insightly CRM, assigns it to a CRM user, and links it to the Lead or the Contact associated with the Prospect from the Finish Action. When creating this Finish Action, you can use Merge tags to automatically add data to the Task Name and Description fields by clicking the “i” icon in the field box. The content is taken from the Prospect’s data. |
Notify User | Sends a notification to a specified user. In the Notification Type dropdown, the default setting is App Notification, which will only notify users within the Insightly App. Users can select App Notification + Email to receive an email notification in addition to the App notification. |
Important Details
Finish Actions don’t expire. For example, if a Prospect is cleaning out their inbox two months from now and they open the email and click on links, the finish actions will still fire.
Finish actions execute every time the action is taken regardless of how many clicks occur in a given period.
After your Email is sent, you can still edit or reorder the Email’s Finish Actions. The actions are not retroactive, so edits will only execute on Prospects who take the action in the future.
If you have multiple Finish Actions, they will only execute based on the Prospect's original field values. For example, say a Prospect started with a score of 5 and was updated to 10 as a result of the first action.
If the section action were to execute for Prospects with a score of 10 or more, it would not execute because it was originally 5.
“On click” Finish Actions apply to both HTML and text version hyperlinks of your sent Email.
When a Form submission is received, Insightly will check the IP Address and the user. If five or more Form submissions are received in a five minute time period from the same IP Address and user, Insightly will not process the submission and it will be discarded.
The submitter will receive an HTTP 500 error. This will occur even if the user is blank or null.This SPAM check also occurs in Finish Action sequences for Redirect Links, Hosted Files, Form submissions, List Emails, etc.
Use cases
Use Finish Actions to:
Add a Prospect to a List after they click a link, are assigned a specific tag, or when the Prospect’s form values are updated.
When a Prospect opens or unsubscribes from a List Email, users can configure a series of Finish Actions to fire after that event occurs. If a Prospect were to open the Email, you could configure a Finish Action to send a follow up Email.
If a Prospect record is updated to indicate they are in the construction industry, use a Finish Action to raise or lower their Prospect score.
Learn More
Read the following articles to learn more about using Finish Actions: