Contact SalesStart Free

Connect Clay to Lookout

Send enriched Clay rows to Lookout as signals and verify the connection with one test row.

Last updated: July 12, 2026

Clay sends enriched table rows to Lookout, where they can start matching Motions. The credential direction is important: you create a Sanka token in Lookout and save it in Clay. You do not paste a Clay API key into Sanka.

Plan requirements

Lookout uses Clay's HTTP API integration. Clay's current Free and Launch plans do not include this feature; it is listed for Growth and Enterprise. If your Clay account is eligible, you can use a Clay trial for a one-row connection test. Check Clay pricing for current plan availability. You can still explore Lookout and prepare a draft Motion without Clay.

Create the Sanka token

  1. Open Lookout, select your workspace, and open Motions.
  2. Find Clay connector.
  3. Under Create a workspace token, click Generate Clay token.
  4. Copy the token immediately. It is shown only once.
Treat the token like a password. Do not send it in email or paste it into a shared table cell. If it is exposed, revoke it from Manage Sanka API tokens and create a new one.

Save the token securely in Clay

Clay recommends storing authentication in an HTTP API Headers account instead of writing a token directly into a table configuration.
  1. Open the target table in Clay.
  2. Click Add enrichment and select HTTP API.
  3. Open Select header account, then choose Add account.
  4. Add the Authorization header shown in Lookout, replacing the token placeholder with the token from the previous step.
  5. Name the account so your team can identify the Sanka workspace, then save it.
See Clay's HTTP API guide for the current Clay interface.

Configure the request

Return to the Clay connector section in Lookout and copy the displayed values.
  1. In Clay, choose POST as the method.
  2. Paste the Lookout endpoint.
  3. Select the saved header account and add the remaining displayed headers.
  4. Paste the JSON body template.
  5. Replace each placeholder with the matching Clay column, including company, contact, signal type, and event time where available.
Use a stable, unique value for the deduplication field. This prevents Clay retries from starting the same Motion more than once.

Send one test row

  1. In Clay, run the HTTP API enrichment for one test row only.
  2. Return to Lookout and wait for the Clay connector status to change to Connected.
  3. Open Runs, approvals & outcomes and confirm that the expected Motion received the signal.
  4. Review the Sanka workflow result before running additional rows.

Fix common errors

  • 401 or 403: confirm the Sanka token, the Bearer prefix, and the workspace header copied from Lookout.
  • 409 connector disabled: enable or reconnect the Clay connector in Lookout before retrying.
  • 400 body error: validate the JSON and confirm that text variables are enclosed in quotes.
  • Waiting for signal: verify that the Clay row actually ran and that you used the endpoint for the same Sanka workspace.
  • No Motion ran: confirm that the signal type matches an active Motion and that its conditions pass.
PreviousGet started with LookoutNextHarbor docs