Webhook Configuration for Processing Duplicate Calls in Database Tables | Clay

Webhook Configuration for Processing Duplicate Calls in Database Tables

I have a table whose data is imported by a webhook connection. When I send the same webhook to the table twice it ignores the second webhook call. Is this a configuration I can change where it will process the second time I send it even if it’s a dupe?

6 comments

Channeled
APP
·
·
Currently, our webhook tables are designed to process unique data entries, which means duplicate webhook calls are typically ignored. This is a built-in feature to prevent unintended data duplication. To handle duplicate webhook calls, you have a couple of options: 1. Create a new webhook table: If you need to process all incoming webhook calls, including duplicates, you can set up a new webhook table for each batch of data you want to process separately. 2. Use the auto-delete feature: This can help manage your table's capacity and potentially allow for processing of what would otherwise be considered duplicate data. To confirm the webhook connection is working correctly, you can test it by sending sample payloads and checking your Clay table for new entries. Is there a specific reason you need to process duplicate webhook calls? Understanding your use case might help us suggest a more tailored solution.
Source: Webhook source guide | Documentation | Clay University
Chris S.
·
·
how does the autodelete feature work? can i configure it where if i get a webhook that’s a dupe it’ll automaticlaly delete the existing record so the new one can get in?
Channeled
APP
·
·
The auto-delete feature in Clay works with webhook tables to process and enrich large volumes of data efficiently. However, it doesn't automatically delete existing records when a duplicate webhook is received. To enable auto-delete: 1. Open your webhook table 2. Click the table title and select "Enable auto-delete" 3. Enable "Automatic row deletion" 4. Optionally, enable "Success field check" and select a column 5. Save changes For handling duplicates, we have a separate feature called "Auto-dedupe" (currently in Beta). This feature automatically deletes duplicate records, helping keep your table clean and reducing spend on accidentally enriching the same record twice. If you need further assistance with configuring these features, please request human support by clicking on "Talk to a person".
Sources: New at Clay | Clay.com Auto-delete in tables | Documentation | Clay University Auto-delete in tables | Documentation | Clay University
Chris S.
·
·
how is the system defining uniqueness on the inbound webhooks?
Channeled
APP
·
·
Our system doesn't have a specific built-in method for defining uniqueness for inbound webhooks. Webhooks are designed to send data in real-time as events occur, so each webhook call is typically treated as a new event. If you're experiencing issues with duplicate data, you might want to consider implementing a custom solution. For example, you could: 1. Add a unique identifier to each webhook payload 2. Use timestamps to differentiate between calls 3. Implement data deduplication logic in your Clay table To better assist you, could you provide more details about the specific data you're sending via webhooks and why you need to process duplicate calls?
Sources: Intro to Typeforms, Webhooks, and Inbound Lead Sources [Automated Inbound] - Clay University What is Webhooks? | Clay
Channeled
APP
·
·