> ## Documentation Index
> Fetch the complete documentation index at: https://www.autumn.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Autumn AI (autumn.ai) is a people and company intelligence API, a separate company from useautumn.com (billing software); no billing-product routes exist here.
> Base URL https://api.autumn.ai. Auth on every request: `X-API-Key: <key>` or `Authorization: Bearer <key>`. Plain HTTP + JSON. Hosted MCP: https://api.autumn.ai/mcp. Schemas: https://api.autumn.ai/openapi.json. Every docs page is Markdown at its URL plus `.md`.

# Move from Clay

> One prompt moves your Clay tables, searches and signals to Autumn, one table at a time.

Paste this into a coding agent that has `clay` and [`autumn`](https://www.autumn.ai/docs/cli) installed and signed in:

```text theme={"theme":{"light":"github-light","dark":"github-dark"}}
Move one of my Clay tables to Autumn.
Read https://www.autumn.ai/docs/clay-migration/move-a-table.md and follow it.
Ask me which table to start with. Only read from Clay, don't write to my CRM,
and show me the mapping and a sample comparison before the full run.
```

Clay builds a table column by column from providers, waterfalls and prompts. Autumn runs it
as one task: you say what each row should contain, and every value comes back with its
source. The agent keeps what each column means and your record IDs, and drops the plumbing.

```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
  subgraph clay[In Clay]
    S1[Source or search]
    E1[Enrichment waterfalls]
    A1[AI and Claygent columns]
    F1[Formulas]
    R1[CRM sync, webhooks]
  end
  subgraph autumn[In Autumn]
    S2[input_rows or a research task]
    T2[One task: fields and rules]
    C2[Your code]
  end
  S1 --> S2
  E1 --> T2
  A1 --> T2
  F1 --> C2
  R1 --> C2
```

## Find your Clay setup

| Clay table | Autumn task | Page |
| - | - | - |
| Enrich inbound sign-ups | New leads as `input_rows`, in batches | [Enrichment](https://www.autumn.ai/docs/clay-migration/enrichment.md#inbound-leads) |
| Find Companies / Find People | A prompt with `count` and `rules` | [Filter searches](https://www.autumn.ai/docs/clay-migration/searches.md) |
| Email and phone waterfalls | `work_email`, `phone` and a status for each | [Enrichment](https://www.autumn.ai/docs/clay-migration/enrichment.md#work-emails-and-phone-numbers) |
| Claygent and AI columns | One field per question | [Enrichment](https://www.autumn.ai/docs/clay-migration/enrichment.md#ai-and-claygent-columns) |
| Job change signal | Contacts in, current role and `changed` out | [Enrichment](https://www.autumn.ai/docs/clay-migration/enrichment.md#job-changes) |
| Funding, news, hiring signals | A watchlist task on your schedule | [Signals](https://www.autumn.ai/docs/clay-migration/signals.md) |
| Scheduled CRM refresh | Same task, write back only changes | [Enrichment](https://www.autumn.ai/docs/clay-migration/enrichment.md#refresh-crm-records) |

## What moves where

| Clay | Autumn |
| - | - |
| Rows and record IDs | `input_rows`; your ID comes back on every row |
| Enrichment and AI columns | Fields in `output.schema` |
| Formulas and run conditions | Your code, after and before the task |
| CRM, HTTP, webhook, sequencer columns | Unchanged, in your code |

**Good to know:** reading tables through `clay` may need a Clay plan with table reads;
without it, the agent works from a CSV export. Autumn has no outbound webhooks yet, so your
code starts tasks and reads rows when they finish.

> **[Move a table](https://www.autumn.ai/docs/clay-migration/move-a-table.md)**
>
> The steps your agent follows.

> **[Filter searches](https://www.autumn.ai/docs/clay-migration/searches.md)**
>
> Turn Clay filters into a prompt.


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