Overview

Tracker Actions are automations that are triggered once all Tracker Rules are matched.

Notes:

There are no limits to the number of Actions that a Tracker can support.
Currently we do not execute Actions in any particular order.

Action Types

When creating an Action, you can select from a number of different automations.

The behavior of each of these is captured below.

Update Field

This action type allows you to automatically update a related object field. The main use case or this is labeling data automatically, so your reps don't have to. It requires you to specify the related object Name, API field name and the value that you want to set it to.

Notes:

When setting checkbox fields, you can specify 1 and 0 to denote if the object is checked or unchecked, respectively.
When setting pick-lists, simply put the exact value of the pick-list.

Append to Field

This action type allows you to append a value to an existing text field. The main use case or this is applying specific tags to an object to make it easy to search/report on specific events (for example, 'customer-bad-language'). It requires you to specify the related object Name, API field name and the value that you want to append your tag to.

Notes:

This action works with any text field.
If the text field to be updated is empty, it will simply update the field to your tag. If the text field is not empty, the action will automatically append a comma and a space (", ") before updating you tag.
When setting pick-lists, simply put the exact value of the pick-list.
If updating a multi-select pick-list, we will simply add the value you specify.

Increment Field

This action type allows you to increment a number field on a related object by a positive or negative number.

Notes:

This action type only works on number fields. Using it on another field type will fail silently

Create Contact

This action allows you to create Contacts automatically if specific criteria are met.

Notes:

To check if the contact exists, create a Rule that checks Contact.Id and use the operator 'is blank, empty or null'.
- NOTE: to ensure no duplicate contacts are created, it is essential that your activity tracking software is highly accurate in associating tasks to the right WhoId/WhatId
Often you'll want to associate the Task with the Contact that's being created. To do this, create another action of type 'Update Object Field' and set the WhoId = {{Contact.Id}}.

Create Opportunity

This action allows you to create Oppts automatically from specific conversion events (eg: meeting booked with an account still in prospecting stage).

This allows for better tracking of funnel metrics such as opportunity age, and minimizes the chances of reps not putting opportunities into CRM altogether until they have been qualified.

Notes:

The JSON object supports macros. However, they must be wrapped in quotes, as per the example below.

Create Follow Up Task

Follow up tasks can be created automatically in Salesforce with the following configurable fields:

Assignee, Priority, Due Date (Days In Future), Task Subject and Task Comments.

TaskSubject/Comment fields can be enriched using macros to deliver clear instructions to the user on what is expected of them, so they can execute the task with minimal research. For example:

Prospect - {{Contact.Name}} at {{Account.Name}}, {{Contact.Title}}

Follow up to voicemail left 7 days ago, which was the {{TrulyActivity.Cadence_Step}} time that you tried to reach them in the current outbound campaign.

Share that we have a webinar we'd like to invite them to.

Notify By Email

Email notifications can be sent to a fixed email address (eg: renewals@truly.co) or to the owner of any entity related to the task, including:

Task Assignee, Account Owner, Opportunity Owner, Contact Owner and Lead Owner

Notes:

Only a single fixed email address is supported
A single action can send to a fixed email address or an entity owner, not both (you can create multiple Actions for this behavior)

Notify By Webhook

Webhooks can be used to push information to third party systems in real-time. Popular use cases for this are Slack Notifications and Zapier triggers.

Notes:

Webhook URLs must use HTTPS
Request method is configurable: GET, POST, PUT
The JSON object supports macros. However, they must be wrapped in quotes, as per the example below.
The domain of the webhook must be whitelisted in the Salesforce Admin under Remote Site Settings (Admin >> Security >> Remote Site Settings >> Add Domain). Please note that salesforce requires whitelisting at the subdomain level, so a remote site of 'slack.com' will not match 'api.slack.com'.

{
"Event Name" : "Opportunity Closed", 
"Amount": "{{Opportunity.Amount}}"
}