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 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
Sync Lead to Marketo
Update one or more fields on the lead record in Marketo, identified by the sender’s email address.
You can set:
- Static values — e.g.,
unsubscribed = true
- Dynamic values — tokens that resolve at runtime from Mary’s classification or extracted data, e.g.,
unsubscribedReason = [allGood] {{ classification }}: {{ rationale }}
Common tokens you can reference:
| Token | What it resolves to |
|---|
{{ classification }} | The category Mary assigned (e.g., Unsubscribe) |
{{ rationale }} | Mary’s plain-English reasoning for the classification |
{{ from.address }} | The sender’s email address |
{{ <fieldName> }} | Any field defined in Data Extraction for that category |
Add to Marketo Static List
Add the sender’s email address to a specific Marketo static list. The list is identified by ID, and allGood will display the list name for confirmation once you’ve selected it.
When adding a lead to a Marketo static list, the lead must already exist in Marketo. If it might not, add a Sync Lead to Marketo action before the Add to Marketo Static List action — the sync will create the lead if it doesn’t exist. allGood will warn you if this ordering is wrong.
Example: Unsubscribe actions
Here’s the action chain a typical Unsubscribe category would run:
Sync Lead to Marketo
Mark the lead as unsubscribed and record the reason for the audit trail.| Field | Value |
|---|
unsubscribed | true |
unsubscribedReason | [allGood] {{ classification }}: {{ rationale }} |
Add to Marketo Static List
Drop the lead into the Mary-managed unsubscribe list for downstream reporting and suppression.| Field | Value |
|---|
| Email address | {{ from.address }} |
| List | Unsubscribed by Mary (ID: 19044) |
{{ rationale }} token is particularly useful here — it gives your ops team a human-readable audit trail directly on the lead 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 Static List depends on the lead existing, put Sync Lead to Marketo first.
- Field dependencies. If a later action references a field set by an earlier action, make sure the order reflects that dependency.
Best practices
- Use the
[allGood] prefix in audit fields. Following the example above (unsubscribedReason = [allGood] ...) makes it easy to see at a glance which records were touched by Mary versus a human or another system.
- 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 Marketo instance before going live.
- Watch the order when adding to lists. Most static-list add failures we see are leads that didn’t exist yet. The warning banner will flag this, but it’s a good rule of thumb to lead with a Sync.
