Home
Events
Groups
Members

00 Clay Announcements
01 Community General
01 Props and Wins
01 Watercooler
01 Welcome and Intros
02 Bugs
02 Starting with Clay
02 Support
03 Feedback & Requests
03 Tutorials & Inspiration
04 FT Job Opps
Gtm Career Advice
Member Spotlight

Community Guidelines

Powered by Tightknit

Webhook Trigger Issue: HTTP Column Firing Twice in Clay Tables | Clay

Webhook Trigger Issue: HTTP Column Firing Twice in Clay Tables

·

·

For some reason - my HTTP column that points to a webhook table is firing the webhook twice: Primary Table https://app.clay.com/workspaces/432722/workbooks/wb_G2o7rmdgA4nK/tables/t_7evMFsXRcAUm/views/gv_cDdjZXbmRNra Webhook Table: https://app.clay.com/workspaces/432722/workbooks/wb_EbmEziDg5K9r/tables/t_HjBPoiFn6EvF/views/gv_iPkZwbE3bjW8 I thought it was because the conditions might've been flipping on and off - but I watched it run in real time multiple times and this doesn't seem to be the case.

3 comments

· Sorted by Oldest

Channeled
APP
·
·
This issue could be related to the auto-update settings in your HTTP column. By default, HTTP columns update whenever a new row is added, which can sometimes cause duplicate webhook firing. To resolve this, you can try these steps: 1. Delete the affected HTTP column 2. Create a fresh column 3. When setting up the new column, make sure to check your auto-update settings and adjust them according to your needs 4. Re-map your data to ensure everything is configured correctly If you need the column to update only under specific circumstances, you can use the conditional run feature to set precise criteria for when the webhook should fire.
Source: HTTP API integration overview | Documentation | Clay University
Channeled
APP
·
·
Was that helpful?
Channeled
APP
·
·
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in 02 Support.