How to send signals from Clay to a Custom API signals agent

This guide shows you how to send data from a Clay table to a Custom API signals agent in Duo Copilot, using Clay's HTTP API integration.

Before you start: you need a Custom API signals agent in progress in Amplemarket, with its webhook URL ready. See Build your own – Custom API signals for the full setup.

Step by step

1. Add an HTTP API column

In your Clay table, click + Add column and select HTTP API. The integration setup panel opens.

2. Configure the request

• Method: select POST.
• Endpoint: paste your Amplemarket webhook URL (for example https://api.amplemarket.com/custom_signals/.../entries).
• Body: define the JSON data with the fields you want to send. Type / to insert Clay column values. For example:

{
  "full_name": "/Full Name",
  "job_title": "/Job Title",
  "linkedin": "/LinkedIn Profile",
  "company_name": "/Company Name",
  "company_domain": "/Company Domain",
  "top_3_ai_products": "/Top 3 AI Products"
}

You can leave the other settings (Headers, Response values, Follow redirects, Retry on failure and so on) as they are.

3. Save without running

Open the Save menu and select Save and don't run. You want to send a single test row before running the whole table.

4. Run a single cell to test

On any row, hover over the HTTP API column and click Run cell to send one request. You should see a Status Code: 202 response, which confirms Amplemarket received it.

5. Finish setup in Amplemarket

Go back to your agent in Amplemarket. The test data should appear in the Signal step. Review the Enrichment mappings, set up Filters and Distribution, then in the Output step choose your AI personalization fields and write how the agent should approach these leads. Click Create Agent.

6. Run for all rows

Back in Clay, open the Save menu and select Save and run all rows to send all your data to Amplemarket. You can also use Run settings to control when the HTTP API column runs automatically (for example, only when a certain column has data, or with auto-update on).

Note: the test row from step 4 was sent before the agent was created, so it counted as test data and didn't create a lead. It's sent again when you run all rows, and this time it counts as a real signal.