> ## Documentation Index
> Fetch the complete documentation index at: https://80x.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Guides

> Guides are complete, follow-along Attio workflow builds, each with the exact trigger, blocks, credit math, and a test plan you can run.

Guides are complete, follow-along Attio workflow builds, each with the exact trigger, blocks, credit math, and a test plan you can run. Every build names its trigger and configures every block with real field values. It shows the per-run credit cost, then ends with a test you fire yourself. Ship it into your own workspace and watch it run.

Each build stands alone, so grab the one you need. If you would rather learn a whole job in order, the guided paths in [Learn](/learn) walk you through these same builds with the mental model first. These guides assume you have finished [Build your first workflow](/learn/build-your-first-workflow). When a concept is unclear, [How the engine works](/explanation) covers the why.

## Capture and qualify

When a new lead arrives, these builds fill in its company details, give it a score, and route it to the right rep. You pay for AI only when it changes what happens next, not on every lead.

<CardGroup cols={2}>
  <Card title="Cheapest-first enrichment waterfall" icon="layers" href="/guides/capture-and-qualify/enrichment-waterfall">
    Enrichment fills in missing fields like company size or industry. Run providers in cost order and stop at the first hit, so you never pay twice for one email.
  </Card>

  <Card title="Score leads into explainable bands" icon="gauge" href="/guides/capture-and-qualify/signal-scoring">
    Turn raw signals into a number and a hot, warm, or cold band a rep can read at a glance.
  </Card>

  <Card title="Webhook lead intake with safe upsert" icon="webhook" href="/guides/capture-and-qualify/webhook-lead-intake">
    A webhook lets an outside form send leads straight into Attio. Receive those leads and create or update a person without ever duplicating one.
  </Card>
</CardGroup>

## Route and sequence

Get the right rep on the right account at the right moment. Each build also keeps your enroll and exit steps clean, so no lead gets stuck in the wrong place.

<CardGroup cols={2}>
  <Card title="Slack deal alerts on stage change" icon="bell" href="/guides/route-and-sequence/slack-deal-alerts">
    Post a Slack message to the deal channel the moment a deal moves stage, with the value and owner inline.
  </Card>

  <Card title="Round-robin lead routing" icon="users" href="/guides/route-and-sequence/round-robin-routing">
    Assign each new lead to the next rep in a rotation, skipping anyone who is out of office.
  </Card>

  <Card title="Inbound routing by territory and seniority" icon="map" href="/guides/route-and-sequence/territory-routing">
    Send leads to the right pod by region and title, so an enterprise buyer never lands in an SMB queue.
  </Card>

  <Card title="Enroll and auto-exit sequences" icon="git-branch" href="/guides/route-and-sequence/sequence-enrollment">
    Enroll a lead on qualification and exit it automatically the instant it replies or books a meeting.
  </Card>
</CardGroup>

## Pipeline hygiene and lifecycle

Make the pipeline clean itself and hand off work on a schedule. Each build is tuned to avoid false positives, so an owner only hears from it when something real needs attention.

<CardGroup cols={2}>
  <Card title="Stale-deal sweep" icon="sparkles" href="/guides/pipeline-hygiene/stale-deal-sweep">
    Find deals with no activity for two weeks on a recurring schedule and nudge their owner.
  </Card>

  <Card title="Dedupe on create" icon="copy" href="/guides/pipeline-hygiene/dedupe-on-create">
    Catch a duplicate company or person the moment it is created and merge into the existing record.
  </Card>

  <Card title="Daily pipeline digest to Slack" icon="chart-bar" href="/guides/pipeline-hygiene/pipeline-digest">
    Send one scheduled summary of pipeline movement to Slack each morning instead of ad-hoc pings.
  </Card>

  <Card title="Daily renewal watch at 90, 60, and 30 days" icon="calendar-clock" href="/guides/pipeline-hygiene/renewal-watch">
    Watch every renewal date and alert the owner at three fixed checkpoints before it lands.
  </Card>

  <Card title="Hand off closed-won deals to Customer Success" icon="handshake" href="/guides/pipeline-hygiene/closed-won-handoff">
    Trigger a clean handoff to Customer Success the moment a deal reaches closed won.
  </Card>
</CardGroup>

## Signals and AI

Turn a signal into researched action that lands on the right person. The AI cost sits behind a filter, so you only pay when the lead is worth it.

<CardGroup cols={2}>
  <Card title="AI ICP-fit research and routing" icon="bot" href="/guides/signals-and-ai/inbound-lead-research">
    Research each inbound lead against your ideal customer profile, then route on the verdict.
  </Card>

  <Card title="Funding-signal outbound that beats competitors to a fresh raise" icon="trending-up" href="/guides/signals-and-ai/funding-signal-outbound">
    Detect a fresh funding round and trigger outbound before competitors see the news.
  </Card>

  <Card title="AI agents playbook" icon="brain" href="/guides/signals-and-ai/ai-agents-playbook">
    Decide when an agent earns its credits and how to keep its access read-only.
  </Card>
</CardGroup>

## Platform patterns

Use these when the native blocks are not enough. They are the escape hatches for everything Attio does not do out of the box.

<CardGroup cols={2}>
  <Card title="HTTP and JSON patterns" icon="code" href="/guides/platform-patterns/http-json-patterns">
    Call an external API, parse the response, and feed it back into a record.
  </Card>

  <Card title="App SDK custom blocks" icon="puzzle" href="/guides/platform-patterns/app-sdk-custom-blocks">
    Build a reusable custom block with the App SDK when no native block fits.
  </Card>
</CardGroup>

## Migrating from legacy

You can no longer create new legacy workflows; existing ones keep running, and Attio says sunset notice will come "well in advance." These guides move an existing build onto the new engine.

<CardGroup cols={2}>
  <Card title="Migrate legacy workflows" icon="arrow-right-left" href="/guides/migrating-from-legacy">
    Move an existing legacy workflow onto the new engine without losing its trigger or logic.
  </Card>

  <Card title="Block changes reference" icon="list-checks" href="/guides/migrating-from-legacy/block-changes">
    See which legacy blocks renamed, merged, or split in the new engine.
  </Card>

  <Card title="Pricing changes" icon="credit-card" href="/guides/migrating-from-legacy/pricing-changes">
    Compare what each build cost under the old model against the new credit model.
  </Card>
</CardGroup>

## What makes a good build

The best Attio workflow is boring. It starts with a precise trigger and an early filter that is free to run. From there it does the least it can. That means one small data lookup, one clear write or external action, then a check in the run viewer. It also names an owner and a way to roll it back. Reach for agents, the [Send HTTP request](/reference/utilities/send-http-request) block, and the [Execute code](/reference/calculations/execute-code) block when they remove real complexity, not because they are available.

*Last reviewed against the Attio Help Center, June 2026.*


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.