Attio CRM Sales Operations Automation RevOps

12 Attio Automations We Build for Every Client (With Exact Configuration)

12 essential Attio automations we implement after 30 days of manual use, with triggers, actions, and key configuration notes.

Nacho Lafuente

Nacho Lafuente

February 14, 2026

Attio's automation engine is incredibly powerful. It is also the easiest way to accidentally destroy your CRM.

When teams discover the automation builder, they tend to over-engineer everything. They build 30 intricate workflows that fire constantly, overwhelm their reps with Slack alerts, and eventually get completely ignored.

After auditing and rebuilding Attio instances for dozens of scaling B2B companies, we have landed on exactly twelve automations that actually matter. These 12 workflows remove manual data entry, prevent deals from slipping through the cracks, and keep leadership informed—without turning your Slack workspace into an unreadable wall of noise.

Here is the exact playbook we deploy for every client.

The 12 Automations at a Glance

#The WorkflowThe TriggerThe ActionWhere we build it
1New Deal KickoffDeal is createdAuto-assign owner + create 24h taskAttio Native
2Meeting PrepStage → Meeting ScheduledCreate pre-call research checklistAttio Native
3Proposal ChaserStage → Proposal SentCreate 3-day follow-up taskAttio Native
4CS HandoverStage → Closed WonGenerate structured handover note + alert CSAttio Native
5The 7-Day NudgeDaily CheckSlack DM rep: "This deal is going cold"n8n
6The 14-Day EscalationDaily CheckSlack alert rep + Manager: "Deal at risk"n8n
7The 48h Dead StartDaily CheckSlack alert rep: "New deal, zero activity"n8n
8Duplicate CatcherPerson createdFlag potential duplicate for mergeAttio Native
9Inbound RouterInbound Deal createdAuto-route to rep + assign urgent 4h SLAAttio Native
10Weekly Pipeline DigestEvery Monday at 9AMPost formatted pipeline summary to Slackn8n
11Monthly Win/Loss1st of the monthPost win rate metrics to Slackn8n
12Renewal RadarDaily CheckAlert AM 60 days before contract expiryn8n

(Note: Automations strictly contained within the CRM are built using Attio's native engine. Anything requiring complex APIs, time-based scheduling, or deep Slack formatting is built in n8n. See our GTM Stack Architecture Guide for why).

🚨 The Two Golden Rules of Automation

Before you build a single block, you must follow these two rules. If you break them, your CRM will fail.

Rule 1: Stabilize your data model first. Every automation depends on specific custom fields and object structures. If you build workflows before your data model is locked in, you will spend your weekends fixing broken logic every time you rename a field. Get your foundation right first.

Rule 2: Do it manually 20 times first. If you haven't manually executed a workflow 20 times, you do not understand the edge cases well enough to automate it. Automate the reality of what your team actually does, not your fantasy of what they should do.

Category 1: Deal Velocity (Attio Native)

These should be turned on during Week 1. They immediately enforce process.

1. New Deal Kickoff

The Problem: Deals are manually created but sit unassigned and untouched for days.

The Fix:

  • Trigger: Deal created.
  • Action: Round-robin assign an owner (or assign to default AE). Create an immediate task: "Send intro sequence/book discovery" due in 24 hours. Ping a #new-deals Slack channel.

2. Meeting Prep Enforcer

The Problem: Reps jump into discovery calls completely blind.

The Fix:

  • Trigger: Deal stage moves to Meeting Scheduled.
  • Action: Create task for the owner: "Pre-call prep: LinkedIn review, tech stack check, draft 3 discovery questions" due 24 hours before the 'Meeting Date' field.

3. The Proposal Chaser

The Problem: Reps send pricing and then assume the prospect will reply. They don't.

The Fix:

  • Trigger: Deal stage moves to Proposal Sent.
  • Action: Automate a task due in 3 days: "Follow up on Proposal." If the 'Expected Close Date' is blank, force it to Today + 30 days.

4. The Clean CS Handover

The Problem: Sales closes a deal, pops champagne, and throws a messy client over the fence to Customer Success with zero context.

The Fix:

  • Trigger: Deal stage moves to Closed Won.
  • Action: Generate a formatted note on the Deal record (Contract Value, Promises Made, Key Stakeholders) and assign an urgent task for the AE to fill it out. Alert the #cs-handovers Slack channel so onboarding can begin immediately.

Category 2: Deal Health Alerts (n8n)

Warning: Only deploy these once reps are actively logging their emails and meetings. If adoption is low, these alerts will fire constantly and reps will mute the channel.

5. The 7-Day Nudge

The Problem: Reps get busy and forget about deals that require follow-up.

The Fix: Every morning at 8:00 AM, n8n queries Attio for open deals with zero logged activity in the last 7 days. It sends a gentle Slack DM to the rep: "Hey, no activity on [Company] in 7 days. Is this still active?"

6. The 14-Day Escalation

The Problem: A deal is dead, but the rep is keeping it in their pipeline for vanity padding.

The Fix: At 14 days of silence, n8n escalates. It pings both the rep and the Sales Manager: "ALERT: [Company] has sat dead in [Stage] for 14 days. Close it or follow up today."

7. The 48-Hour Dead Start

The Problem: Inbound leads or newly sourced deals sit unworked.

The Fix: If a deal was created 48 hours ago and has zero logged activity, n8n DMs the rep instantly: "You own [Company] but haven't touched it. Outreach required today."

(Pro-Tip: Configure n8n to only fire these alerts Tuesday through Thursday mornings. Alerts sent at 4 PM on a Friday go straight into the void).

Category 3: Lead Management (Attio Native)

8. The Duplicate Catcher

The Problem: Database rot. Reps don't check if "Acme Corp" exists before creating "Acme".

The Fix:

  • Trigger: Person/Company created.
  • Action: Attio checks for matching email domains. If a match is found, assign a task to the creator: "Merge potential duplicate."

9. The Inbound Router (4-Hour SLA)

The Problem: Expensive inbound leads go cold because they aren't engaged fast enough.

The Fix:

  • Trigger: Deal created where Source = Inbound.
  • Action: Route immediately to the correct territory AE. Create a critical task: "Respond to Inbound" due in precisely 4 hours. DM the rep directly in Slack with the booking link.

Category 4: Executive Reporting (n8n)

Build these in Month 3, once you have clean data flowing.

10. The Monday Pipeline Digest

The Problem: Leadership hates logging into CRMs just to see if the team is on track.

The Fix: Every Monday at 9:00 AM, n8n pulls aggregate data from the Attio API. It formats it into a beautiful Slack message for the executive channel:

  • Total Open Deals & Value
  • New Deals Added Last Week
  • Value broken down by Pipeline Stage
  • List of Stalled Deals

11. Month-End Win/Loss

The Problem: Nobody looks back at the tape to see why deals actually died.

The Fix: On the 1st of the month, n8n calculates the previous month's Win Rate, Average Deal Size, and Sales Cycle Length, and posts the retrospective directly to the team channel.

Category 5: Account Management (n8n)

12. The 60-Day Renewal Radar

The Problem: Account Managers realize a client is renewing next week, panic, and fail to upsell.

The Fix: n8n scans Attio daily. If a Company's 'Renewal Date' field hits exactly Today + 60 Days, it assigns a task and DMs the AM: "Time to start the renewal conversation for [Company]."

What We Absolutely Refuse to Automate

Avoid these attractive traps at all costs:

  • Auto-closing inactive deals: Don't let an AI close a deal just because a rep forgot to log an email. Use alerts instead. Let humans close deals.
  • Sending emails out of Attio: Attio's native integration is for logging relationship context, not running outbound sequences. Connect your outbound tool via API.
  • Scraping LinkedIn for Companies: Scraping tools are messy. Automatically creating CRM records from raw scrapes leads to chaotic data. Send scrapes to Clay first for validation, then push to Attio.
The Automation Graveyard: Every messy Attio instance we audit is filled with abandoned automations. Before you build a workflow, ask yourself: "If this fires, what exact physical action will the recipient take?" If the answer is "Oh, it's just nice to know," delete it. Informational alerts become noise. Actionable alerts drive revenue.

We build this exact 12-step automation engine as part of our Growth Scale implementation package. If you are tired of logging data manually or want to see how this architecture works in the real world, book an audit call with us.

Nacho Lafuente

Nacho Lafuente

February 14, 2026

Share