How to Use Finish Actions

Finish Actions update a Prospect’s record automatically when they interact with something you sent, instead of requiring manual follow-up.

On this page:

• What triggers them
• What they can do
• Creating a Finish Action
• Automating with AppConnect

What triggers them

Finish Actions attach to four things: redirect links, hosted files, form submissions, and list emails. When a Prospect interacts with any of them, the actions you configured fire immediately against their record.

What they can do

• Add a Prospect to a list after they click a link, receive a tag, or update their form values.
• Fire a follow-up sequence when a Prospect opens or unsubscribes from a list email, including sending a follow-up email.
• Raise or lower a Prospect’s score based on information added to their record, for example adjusting the score once their industry is known.

⚠️ Finish Actions don’t expire. An action attached to an old email fires whenever that email is opened, including months later when someone is clearing out an inbox.

Creating a Finish Action

Open the redirect link, hosted file, form handler, or list email you want the action to run from, go to its Finish Actions tab, and click Add Finish Action. Give the action a name, set the criteria that decide when it runs, and Save.

Finish Actions draw from the same library of actions available in Journeys. See Journeys for the full list, including adding a Prospect to a list, adjusting or setting a score, converting to a Lead or Contact, assigning an owner, notifying a user, firing a webhook, running a Lambda function, and triggering an AppConnect recipe.

⚠️ Multiple actions read the record as it was when they started. When several Finish Actions run together, each one evaluates the Prospect’s field values as they stood when the actions began, not after an earlier action changed them. An action that depends on a value a previous action just set may not fire as expected.

Automating with AppConnect

Accounts with AppConnect can build recipes to automate Finish Action processes. The custom trigger must be tied to the Prospect record.