You are here:
Choosing the Right Automation Option
When you want to incorporate automation into your Sales Engagement cadences or handle large groups of records at one time with bulk actions, it’s important to clarify your use case. Pinpointing the resulting trigger origin can help you select the most effective option for your needs.
Required Editions
| Available in: Lightning Experience |
| Available with Sales Engagement, which is included with Sales in Performance, Einstein 1, and Unlimited Editions, and available for an extra cost in Professional and Enterprise Editions. Sales Engagement is also available for an extra cost in Service and Lightning Platform. |
| Automation Tool | Trigger Origin | Supported Actions | Who Creates Them? | Notes |
|---|---|---|---|---|
| Automated actions | A record is created. A record is created *and* every time a field in the conditions is edited. Only applies to these objects:
|
Field updates aren’t supported. |
Rep Actions apply only to records they own. |
Cadence assignee can be the rep or another user. Trigger conditions support:
For sales reps and managers. For large-scale automations, use Flow. |
| Cadence step flows | A target starts a cadence step. | Screen flow-supported actions that include (but aren't limited to):
|
Salesforce admins Developers |
Cadence builders can use active cadence step flows when creating cadences. |
| Cadence autolaunched flows | The associated step completes. | Flow-supported actions that include (but aren’t limited to):
|
Admins Developers |
Cadence builders can add an active cadence autolaunched flow to any action step. Add a flow to the completion of each cadence step, one step at a time. Add a flow to the last step at the completion of a cadence, one cadence at a time. |
| Platform standard tools (Flow Builder, Apex, APIs, Batch Class) | Inserts or updates to standard or custom objects, or any other platform triggering event. Excludes cadences, cadence steps, and engagements. |
Platform-supported actions that include (but aren’t limited to):
|
Admins Developers |
Optional: Define the solution at the org level. |
| Change Data Capture | The start or end of a cadence. The start of a cadence step. A global automation solution across multiple cadences. |
Platform-supported actions that include (but aren’t limited to):
|
Admins Developers |
Optional: Define the solution at the org level. Create a one-time triggering solution that ties into flows by using platform events. Use when your requirement affects multiple cadences rather than configuring an autolaunched flow for every cadence step. |
