Salesforce Actions

Actions are what Mary does once she’s classified a reply and pulled out any extracted data. They run automatically the moment a match is confirmed, so by the time an email shows up in the Messages feed, the downstream work in Salesforce is already done. Actions are configured per category. A reply that lands in Unsubscribe runs one set of actions; one that lands in Left Company runs another.

​

Available action types

​

Forward Email

Forward the classified reply to another email address. This is the go-to action when a reply needs a human — for example, routing a Human Request reply to your shared sales inbox, or looping a specific rep in on Out-Of-Office replies for accounts they own. Forward Email is a generic action and works the same way regardless of which marketing automation platform you’re connected to. The Original Email dropdown controls what happens with the source message: Under Advanced:

​

Add to Worksheet

Push the sender into an allGood worksheet, optionally running it through the worksheet’s flow steps. This is how you take a classified reply and hand it off to another allGood workflow — for example, adding a Human Request sender to a follow-up worksheet that triages and routes them, or pushing extracted replacement contacts from Left Company replies into a new-lead worksheet. Add to Worksheet is a generic action and works the same way regardless of which marketing automation platform you’re connected to. Under Advanced:

​

Sync Contact/Lead to Salesforce

Create or update a record in Salesforce, identified by the sender’s email address. Mary looks the record up by email — preferring a Contact, then falling back to a Lead — then creates or updates it depending on the sync mode you choose. You can set:

• Static values — e.g., leadStatus = Unqualified
• Dynamic values — tokens that resolve at runtime from Mary’s classification or extracted data, e.g., allgood_reason = [allGood] {{ classification }}

Each row in the field map pairs a Salesforce field’s API name with a value or token. The email address is always included automatically — it’s the lookup key. You also choose a sync mode under the advanced tab: Common tokens you can reference:

​

Add to Salesforce Campaign

Add the sender to a specific Salesforce campaign as a campaign member. Mary looks the record up by email and adds them to the campaign you specify. The campaign is identified by its Campaign ID — the 15- or 18-character Salesforce Campaign record ID.

​

Unsubscribe in Salesforce

Opt the sender out of email in Salesforce. Mary looks the record up by email — preferring a Contact, then falling back to a Lead — and sets their email opt-out status. This is the cleanest way to honor an opt-out, because it uses Salesforce’s native email opt-out field rather than just flipping a custom field.

​

Example: Unsubscribe actions

Here’s the action chain a typical Unsubscribe category would run: The {{ rationale }} token is particularly useful here — it gives your ops team a human-readable audit trail directly on the record explaining why Mary marked someone as unsubscribed.

​

Stacking and reordering actions

You can configure multiple actions per category, and they run in the order they’re listed. Use the up/down arrows on each action row to reorder them. Click + Add Action to add more. Order matters in two cases:

• Dependent actions. If an Add to Salesforce Campaign depends on the record existing, put Sync Contact/Lead to Salesforce (in Create or Update mode) first.
• Field dependencies. If a later action references a field set by an earlier action, make sure the order reflects that dependency.

​

Conditional actions

Every action supports an only-if condition — a token expression that must evaluate to true for the action to run. This lets you fan out behavior within a single category. For example, only add to a “Hot Leads” campaign when an extracted intent field is high, while still running the rest of the chain for everyone. Actions that look a record up by email also expose a skip if not found toggle, which controls whether a missing record is treated as a quiet skip or a hard error.

​

Best practices

• Use the [allGood] prefix in audit fields. Following the example above (allgood_reason = [allGood] ...) makes it easy to see at a glance which records were touched by Mary versus a human or another system.
• Use field API names, not labels. The field map keys must be Salesforce’s API field names, not the friendly labels shown elsewhere in the UI. A field name that doesn’t exist will fail at execution time.
• Prefer the native unsubscribe. For opt-outs, use Unsubscribe in Salesforce rather than just setting a custom field — it updates Salesforce’s native email opt-out so suppression is honored everywhere.
• Test the full chain, not just the classification. The Test Suite validates categorization and extraction; once those pass, sanity-check the actions in a sandbox Salesforce instance before going live.
• Watch the order when adding to campaigns. Most campaign-add failures we see are records that didn’t exist yet. Lead with a Sync Contact/Lead to Salesforce in Create or Update mode to be safe.