← Back to Salestrics Today

Auto Add-On: Campaigns and Nurture Without Zapier

Mid-market teams outgrow manual follow-up before they need a full MAP stack. The Auto add-on runs campaigns and nurture on the same account graph as CRM, mail, and pipeline — $10/person/mo on any standalone tier, included on Salestrics One. The trap is buying Auto for every rep while only marketing builds sequences, or turning on nurture before mail on account works. This 2026 playbook maps when to attach Auto, who holds the seat, first campaigns to ship, and how Auto differs from Flow approvals.

What Auto is for

Auto is campaign and nurture automation on the revenue graph — triggers from pipeline stage, mail activity, and account fields without exporting lists to a separate MAP.

  • Nurture sequences — timed mail on accounts with exit rules
  • Campaign enrollment — segment-based programs with caps
  • Re-engagement — stale opps and dormant contacts with RevOps approval
  • Agent-readable — MCP summarizes who is in which program

Product page: Salestrics Auto. Add-on catalog: Flow, Ledger, Insight SQL guide and Changelog #17.

Auto vs Flow vs external Zapier

ToolPrimary useTypical owner
AutoCampaigns, nurture, re-engagementMarketing / RevOps
FlowApprovals, routing, internal workflowsRevOps / ops
Zapier (external)Legacy bridge during migrationRetire after cutover

Auto on the graph beats Zapier when triggers need live mail and stage context — not CSV exports. See automation without Zapier.

Buy order (recommended)

  1. Mail on account — sequences send from org mail on the account
  2. Stage hygiene — triggers reference real pipeline motion
  3. One to two Auto seats — builder + backup, not full pod
  4. First campaign — single segment, measurable exit criteria
  5. Flow — when approvals gate discounts or legal review on campaign enrollments

Mail policy: mail on account. Outbound motion: outbound sequence playbook.

Seat map

RoleAuto seat?Notes
Marketing opsYesBuilds and publishes campaigns
Demand genYesOwns nurture calendar
AEUsually noConsumes sequences; personal mail on account
RevOpsOptionalOne seat if RevOps owns lifecycle
CSOptionalRenewal nurture on Resolve accounts

First campaigns to ship

  • Inbound SLA nurture — form fill to meeting book; pairs with inbound SLA
  • Post-demo follow-up — 3-touch sequence on opp stage Demo Held
  • No-show recovery — trigger from Connect outcome — no-show playbook
  • Renewal window — 90-day pre-expiry on active accounts
  • Re-engagement — dormant contacts with single clear CTA

Start with one campaign, measure reply and meeting rates for 30 days before adding complexity.

Governance before scale

  • Enrollment caps — max contacts per program per week
  • Suppression lists — customers in active support cases excluded
  • Human approval — first send on new templates; Flow can gate if needed
  • Unsubscribe discipline — honor exits on graph; no shadow lists
  • Token awareness — heavy AI-generated copy burns Assistant pools — token governance

When One beats Auto add-on math

Auto at $10/person × eight builders is $80/mo — fine standalone. Add Ledger, Flow, Insight SQL, dual Momentum and Resolve lines, and One Team at $499 often wins — One vs standalone.

Anti-patterns

  • Auto on every AE — marketing builds; sales sends from mail
  • Nurture before mail policy — sequences from personal inboxes
  • Duplicate Zapier + Auto — same trigger in two systems
  • No exit rules — contacts stuck in dead campaigns
  • Whole-book blast — burns domain reputation and tokens

90-day Auto review

  • Active campaigns — retire programs with <2% engagement
  • Seat usage — who logged in to Auto last 30 days
  • Deliverability — bounce and spam signals on org mail
  • One math — rerun if add-ons and lines stacked

Worked example: inbound-to-meeting nurture

A mid-market team receives 40 inbound leads per week from the website:

  1. Trigger — form submit creates contact + opp in Momentum
  2. Auto enroll — 4-touch sequence over 10 days from org mail
  3. Exit rules — meeting booked, reply received, or manual disqualify
  4. SLA alert — no reply day 3 pings owner in Connect chat
  5. RevOps review — weekly conversion form → meeting rate

One marketing ops seat on Auto ($10/mo) builds; five AEs on Momentum Team consume. No Auto seat per AE required.

Integrations to retire after Auto

Legacy toolReplace with
Mailchimp list sync to CRMAuto nurture on graph
Zapier new-lead → sequenceNative trigger on opp create
Spreadsheet nurture trackerAuto enrollment dashboard

MCP prompt (campaign audit)

List contacts enrolled in active Auto campaigns with no mail reply in 14 days. Recommend pause or exit per program rules — read only.

Related reading