Chapter 5/8 • 15 min read

Workflows

Native automations

⏱️ TL;DR: Attio Workflows automate CRM tasks without code. Create triggers based on record changes, schedule recurring actions, and build multi-step automations. Native workflows are simpler than Make.com but handle 80% of common use cases.

What Are Attio Workflows?

Attio Workflows are native automations built directly into the CRM. Unlike external automation tools like Zapier or Make.com, workflows run inside Attio with zero latency and full access to your data model.

Workflows follow a trigger → action pattern: when something happens (trigger), Attio automatically does something (action). You can chain multiple actions and add conditions for complex logic.

Workflow Triggers

Triggers define when a workflow runs. Attio supports several trigger types:

Record Triggers

  • Record created: When a new company, person, or deal is added
  • Record updated: When any field changes on a record
  • Field changed: When a specific field changes value
  • Record enters list: When a record is added to a specific list

Time-Based Triggers

  • Scheduled: Run at specific times (daily, weekly, monthly)
  • Field date: Trigger X days before/after a date field

💡 Pro Tip

Use "field changed" triggers instead of "record updated" when you only care about specific changes. This prevents workflows from running on every minor edit.

Workflow Actions

Actions are what happens when a workflow triggers. Available actions include:

  • Update record: Change field values on the triggering record
  • Create record: Add a new company, person, or deal
  • Create task: Assign a task to a team member
  • Send notification: Alert team members via Slack or email
  • Send email: Send templated emails to contacts
  • Add to list: Move records into specific lists
  • Remove from list: Remove records from lists
  • Webhook: Send data to external systems

Building Your First Workflow

Here's how to create a basic workflow:

  1. Go to Settings → Workflows
  2. Click "Create workflow"
  3. Choose your trigger (e.g., "Deal created")
  4. Add conditions if needed (e.g., "Deal value > $10,000")
  5. Add actions (e.g., "Create task for account manager")
  6. Test with a sample record
  7. Activate the workflow

Common Workflow Examples

Lead Assignment

Trigger: New lead created
Action: Assign to sales rep based on territory (using conditions)

Deal Stage Notifications

Trigger: Deal stage changes to "Proposal Sent"
Action: Notify sales manager via Slack, create follow-up task for 3 days later

Contract Renewal Reminder

Trigger: 60 days before contract end date
Action: Create renewal task, add to "Renewals" list, notify account manager

Enrichment Trigger

Trigger: Company created with domain filled
Action: Trigger enrichment (via webhook to Clay or Clearbit)

Conditions and Filters

Conditions let you control when workflows run. You can filter based on:

  • Field values (equals, contains, greater than)
  • Record type or list membership
  • User assignments
  • Date comparisons

Use conditions to prevent workflows from running on irrelevant records. For example, only trigger "high-value deal" notifications when deal value exceeds $50,000.

Workflows vs External Automation

When should you use Attio Workflows vs Make.com or Zapier?

Use Attio Workflows for:

  • Internal CRM automations (field updates, tasks, notifications)
  • Simple integrations via webhooks
  • Anything that only involves Attio data

Use Make.com/Zapier for:

  • Complex multi-app integrations
  • Data transformation and formatting
  • Syncing with external systems (email tools, accounting, etc.)

📚 Best Practice

Start with native workflows for simple automations. Graduate to Make.com only when you need features Attio doesn't support natively. This keeps your automation stack simpler and more maintainable.