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

# Clay integration

> Append each completed call as a row in your Clay table via the table's webhook source: TL;DR, summary, next steps, caller number, or AMD verdict. Direct, no Zapier hop.

The Clay integration appends one row to your Clay table per completed call.
Clay's public API is read-only for tables, so rows arrive through your
table's **webhook source** — Clay's supported inbound path — delivered
directly from PyAI with one column per field.

## What you need

* Your Clay table's **webhook source URL**: in the table, add a source →
  **Webhook** → copy the generated URL.

## Connect

1. In PyAI Console, open **Integrations** and find **Clay** under Sales
   engagement.
2. Click **Connect**, paste the webhook source URL, and pick your events.
3. Press **Test**. A sample row lands in the table so you can check the
   columns.
4. Done. Rows append after every completed call.

## Which columns land

| Recap rows                                                                                   | AMD rows                                                                                                                    |
| -------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| event, occurred\_at, call\_id, status, pack\_id, tldr, summary, next\_steps, customer\_phone | event, occurred\_at, call\_id, status, answered\_by, answered\_by\_twilio, confidence, decision\_ms, reason, session\_label |

The row is flat, so every field is a column your table formulas and
enrichments can use immediately.

## Troubleshooting

* **Rows stop landing after the table changed.** If the webhook source was
  removed or regenerated, its URL changed. Copy the new URL and update the
  connection.
* **Columns look different than expected.** Clay maps fields by name on
  arrival; check the webhook source's field mapping in the table settings and
  rename columns to match the list above.
* **When to use Zapier instead.** The Clay integration is the direct
  single-table path. For multi-step flows (filters, branching, several tools
  at once), use the Zapier integration and point a Zap at Clay instead.