Automated Clay Table Setup Verification
When a new Clay table is set up for a campaign, WebRun checks that every enrichment column has a working data source connected and the fields the outreach step needs are actually mapped, posts the setup status to Slack, and pings Telegram the moment a step is blocking the table from running cleanly.
How do I check a new Clay table's enrichment setup before running it?
When a new Clay table is set up, WebRun checks that every enrichment column has a working data source and that the fields your outreach step needs are actually mapped. It posts the setup status to Slack and pings Telegram the moment something is blocking the table, so a broken enrichment column gets fixed before it burns credits across a full list.
- Broken enrichment columns are caught before a full run wastes credits
- The team sees setup status in Slack without opening the table
- Blocking gaps reach the table owner within minutes
Built for growth teams · GTM engineers · revenue operations · demand generation
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.clay.comin a real browser with your saved login - no setup, no API keys. -
1
Clay - check the new table's enrichment setup
clay.com
WebRun opens Clay to check the new table's enrichment setup. - Open Clay and review the columns on the newly created table
- Check that each enrichment column has a connected, working data source
- Confirm the fields the outreach sequence needs are mapped and populated
Done when Every column on the new table has a pass or fail setup status.
-
2
Slack - post the setup status
slack.com
WebRun opens Slack to post the setup status. - Post the table's setup status to the growth channel
- List which columns passed and which are missing a source or mapping
- Include the table name so it is easy to find
Done when The team has the new table's setup status in Slack.
-
3
Telegram - flag a blocking step
telegram.org
WebRun opens Telegram to flag a blocking step. - Send a Telegram ping only when a blocking step is found
- Name the column and what it is missing
- Skip the ping when the table is fully set up
Done when The table owner has been pinged about any blocking step.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it fix the broken enrichment column itself?
No. WebRun only checks and reports which column is missing a source or a mapped field. Reconnecting a data source is done by the table owner in Clay.
Why check this before the table runs?
A broken enrichment column can burn credits pulling incomplete data across an entire list. Catching it on a handful of rows first is cheaper than finding out after the full run.
What counts as a blocking step?
A column with no data source connected, or a field the outreach sequence needs that is still empty. Optional or unused columns are noted but do not count as blocking.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.