A step-by-step guide to setting up a Clay workbook that receives contact signals over a webhook and keeps one always-current row per person — automatically.
Template: Clay shared workbook
What this does
Every time a new signal fires (e.g. a competitor-engagement or deal event), it's sent to Clay as a webhook. Without any setup, Clay would just keep appending a new row for every event, so the same person shows up again and again with stale copies scattered across the table.
This template fixes that. It uses two tables:
- All Rows — the raw webhook landing table. Every event is appended here, untouched. This is your complete history / audit log.
- Master — a clean view with exactly one row per person, always showing their latest signal. Older duplicates are deleted automatically.
Setup
1. Create workbook using template
Open the shared workbook and create yours using the template. You'll get both tables (All Rows and Master) pre-wired.
2. Get the webhook URL
- Click the Pull in data from a webhook node
- Copy the Webhook URL
3. Point your signal source at the webhook
Paste that URL into the Send to Webhook node in your Letterdrop workflow.
Add 2 custom fields based on contact type
Type | Variable Name | Value |
Direct connection | contact_type | Contact with signal |
Buying committee | contact_type | Extended Buying Committee |
Troubleshooting: "I don't see all columns in the Master sheet"
If a column exists and is populated in All Rows but it's not showing up in the Master table, it's because the template can't carry over column mappings — it only sends the data and the table config. You just need to tell the Send step to include that column and then map it on the Master side. Here's how:
- In All Rows, find the Send data to table column and click Edit config.
- Make sure all the columns you want are checked — including the one that's missing. Anything unchecked won't be sent to Master.
- Click Save, then Run for all rows so the data flows through.
- Go to the Master table — the field is now arriving in the data, but it may need its own column. Create a new column for it (map it to the incoming field).
Why this happens: when you duplicate a template, Clay copies the data-send action and table settings but not the individual column mappings. So a few of the field-to-column mappings on the Master side need to be set up on your end — this is expected, not a bug.