15 native Attio workflows automating 156 accounts on auto follow-up

The situation

Regreener sells carbon credits and climate projects out of Amsterdam. They’d already moved from HubSpot → Pipedrive → Attio, but the third migration had landed them in a working CRM with no automation layer on top of it. Three problems were compounding:

• Two account tiers, two cadences, zero enforcement. Key accounts needed a 30-day follow-up rhythm, non-key accounts a 60-day one. In practice, follow-ups happened when someone remembered them.
• Framer forms dumped leads into a black hole. Three different forms (Get Started, Carbon Credits, Project Developer) lived on the marketing site. None of them landed in the CRM tagged with their source.
• Closed-won deals didn’t trigger anything. Delivery records weren’t being created, renewals weren’t being scheduled, and the email contact list drifted further from reality every month.

What we built

Five workflow groups, fifteen native Attio workflows, no n8n, no external glue. The whole thing runs inside Attio’s automation engine.

WF1  Tier-Based Tasks + List Routing  ──  6 workflows
WF2  Framer Forms → Attio              ──  3 webhooks
WF3  Deal Won → Delivery               ──  1 workflow
WF4  Deal Won → Renewal (+1 yr)        ──  1 workflow
WF5  Engagement → Email Contacts list  ──  2 workflows
                                        ─────────────
                                          15 workflows

1. Tier-based recurring tasks (6 workflows)

The core of the system. Two cycles — Key (30 days) and Non-Key (60 days) — running off a custom Next Follow-up Date attribute that gets seeded when a tier is first assigned and reset every time a salesperson logs an interaction. The “Find Records” limit of 10 per run naturally staggers task creation across days, so no single morning gets buried.

trigger:    daily (weekdays only)
find:       Companies WHERE tier = "Key" AND next_follow_up <= tomorrow LIMIT 10
loop:
  ├─ create task   "Follow up with {company.name}"  → owner
  ├─ adjust time   next_follow_up + 30 days
  └─ update record next_follow_up = adjusted

(non-key uses the same loop with +60 days)

Two extra workflows handle the bidirectional list assignment: when a company’s tier changes, it’s added to the relevant list and removed from the other.

2. Framer → Attio lead capture (3 webhooks)

Each Framer form has its own Attio webhook URL. The workflow extracts the email, creates or updates the Person record, waits 5 minutes for Attio’s auto-enrichment to pull the company from the email domain, then tags the company with the right Lead Source. Three sources, three webhooks, one consistent tagging schema.

3. Deal Won → Delivery record

The moment a deal hits “Won”, a Delivery record gets created with the company, deal value, owner, and people pre-mapped. No one has to remember to do it.

4. Deal Won → Renewal deal (+1 year)

Same trigger, different output: a new deal is created at the “Renewals” stage, dated one year from close. The pipeline now self-replenishes with renewal opportunities the day a deal closes.

5. Engagement → Email Contacts list

Two workflows watch the Last Interaction field. People interacted with in the last 365 days (and not flagged “Very Weak” connection strength) get added to the Email Contacts list. People who go cold get removed automatically. SendGrid stays in sync via Zapier.

Outcome

• 15 workflows live. All running natively inside Attio — no external infrastructure to maintain, no glue scripts to break, no API keys to rotate.
• 225 companies cleaned in one script run. Seeded follow-up dates, created staggered tasks (5 per person per weekday), aligned future dates. Zero errors during execution.
• 156 accounts on auto follow-up. 30 Key, 126 Non-Key. The system runs whether anyone’s watching or not.
• 30-day Won → Renewal pipeline. Every closed deal now seeds its own next renewal opportunity automatically.

Why native Attio, not n8n

Regreener is a small team. Every external service is something to monitor, debug, and pay for. The build deliberately stayed inside Attio’s native automation engine because the workflows didn’t need anything Attio couldn’t do — and keeping them in-platform meant Bernard could see every automation, edit any of them, and pause anything in seconds.

When n8n actually adds value (real-time dedup, complex multi-system orchestration), we use it. When Attio can do the job alone, that’s the right answer.