Skip to main content
Use the Clay integration when you want qualified lead events from traxy to flow into a Clay workflow or table. Clay delivery uses a webhook-style connection. traxy sends a signed POST request to the Clay webhook URL you configure.

​
Before you connect Clay

Owners and admins can connect Clay and change delivery settings. Make sure you have:
  • a Clay account
  • a Clay table, workflow, or webhook destination ready to receive lead data
  • the Clay webhook URL
  • an optional bearer token if your Clay endpoint expects one
Use a secure https:// URL. traxy cannot send to insecure endpoints.

​
Connect Clay

  1. Open Integrations.
  2. Open Clay.
  3. Add an Integration Name.
  4. Paste the Webhook URL from Clay.
  5. Add an Auth Header if your Clay endpoint expects one.
  6. Click Connect.
  7. Review the Qualified Lead Detected trigger.
  8. Choose whether to keep auto-send on.
  9. Set the ICP match threshold for automatic delivery.
  10. Decide whether to enable Send repeat engagement from qualified leads.
  11. Click Save Configuration.
  12. Click Send Test Payload before you rely on the workflow.
If you connect Clay but do not keep a valid webhook URL saved, Clay delivery stays disabled.

​
Choose manual or automatic delivery

Clay can work in two ways:
  • Manual delivery from the leads table when you want to review each lead first
  • Automatic delivery when you want traxy to send new qualified leads to Clay as soon as they meet your threshold
Automatic delivery is non-retroactive. It sends leads that qualify after auto-send is turned on. Repeat engagement delivery only works when the Clay trigger and auto-send are both enabled. If you turn auto-send off, repeat engagement delivery turns off too.

​
Send leads manually

Use manual delivery when you want to control which leads enter Clay.
  1. Open Leads.
  2. Select one or more leads.
  3. Choose the send action.
  4. Select Clay.
  5. Confirm the send.
traxy queues the selected leads for delivery to the configured Clay webhook.

​
Review the payload

The Clay integration page includes Payload & Help with sample JSON for first qualified lead delivery and repeat engagement delivery. The payload includes event metadata plus lead, profile, company, contact, and engagement data. Use the sample payload in traxy as the source of truth when you map fields in Clay.

​
Verify requests

Clay requests are signed. Each request includes X-Traxy-Signature and X-Traxy-Timestamp so your receiver can verify that it came from traxy. If you add an auth header, use the bearer format shown in the app.

​
Test and troubleshoot

Use Send Test Payload before you turn on an important workflow. The test is one immediate request. Lead deliveries can retry temporary failures. Automatic delivery may pause if repeated failures are not fixed. If you send manually from Leads, you may see states such as queued, delivered, or failed. Fix the underlying Clay issue first, then retry from the lead. Review automatic settings carefully before you enable them for a shared workspace.

​
Disconnect Clay

Use Disconnect when you want traxy to stop sending events to Clay. Disconnecting Clay does not change existing Clay tables, workflows, or records.