Limitations of Clay Webhooks: Issues with Complete Data Push

Marielle C. · 2024-12-02 14:16:04.710322+00

Does clay have limit on webhooks? I used webhook but the entire list didnt pushed through

Limitations of Clay Webhooks: Issues with Complete Data Push | Clay

12 comments

· Sorted by Oldest

Channeled
APP
·
·
Yes, there are specific rate limits for webhooks in Clay. Each workspace is limited to processing up to 10 records per second, with a maximum burst capacity of 20 records. Additionally, each webhook payload must not exceed 100KB in size.If you're working with multiple webhook sources in your workspace, you'll need to either: 1. Modify your sending rate to stay within these limits 2. Consider batching your requests to manage noisier data streamsIf you need assistance with optimizing your webhook implementation or if you have any further questions, please don't hesitate to ask. If you require more in-depth support, you can request human assistance by clicking on "Talk to a person". Source: Import Data to Clay Using Webhooks
Channeled
APP
·
·
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Marielle C.
·
·
Is it possible to continue pushing the remaining leads the next day? just dont want to mess up the workflow
Marielle C.
·
·
Had the same issue in another clay table too: https://app.clay.com/workspaces/13635/tables/t_rgH9YXrTzPM3/views/gv_ZzZ7kZ6284En
Marielle C.
·
·
And in other clay tables as well, please let us know if its clay or leadmagic side, would really appreciate your assistance 🙏
Bruno R.
·
·
Hi Marielle, thanks for reaching out! Yes, Clay webhook tables have a 50k record limit for pushing records through a table. We also enforce some additional rate limits: * 10 records per second sustained rate * 20 records maximum burst capacity Could you share more context about the issue you're encountering with importing records to this webhook? From my end, it appears to be working correctly—I ran some tests, and the webhook seems to be monitoring as expected. Let me know where you're running into trouble, and I'd be happy to help further!
Marielle C.
·
·
Hi Bruno, the whole list is not pushing In this clay table it should be 11k but only 2.3k pushed https://app.clay.com/workspaces/13635/tables/t_rgH9YXrTzPM3/views/gv_ZzZ7kZ6284En In another table, it should be 13k but it run only until 7755 (the total of this table should be 19k (including the first webhook) https://app.clay.com/workspaces/344295/workbooks/wb_pdPEr5CtepAY/tables/t_xmVhiojGBKnu/views/gv_6YEt6A9RvtZF
Loading attachments
Bruno R.
·
·
I notice the tables now reflect 13k and 26k records, respectively. Could this have been a temporary refresh issue with the application responsible for pushing these records to Clay?
Marielle C.
·
·
Hi Bruno, i also contacted source of webhook which is leadmagic, i think the issue is from their side, thank you for your help
Daniela D.
·
·
Hey Marielle! Thanks for the reply. Let us know if you still run into any issues here.
❤️1
Channeled
APP
·
·
Hi Marielle C.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Channeled
APP
·
·
Thank you so much for sharing your feedback Marielle C.!

Channeled
APP
·
·
Yes, there are specific rate limits for webhooks in Clay. Each workspace is limited to processing up to 10 records per second, with a maximum burst capacity of 20 records. Additionally, each webhook payload must not exceed 100KB in size.If you're working with multiple webhook sources in your workspace, you'll need to either: 1. Modify your sending rate to stay within these limits 2. Consider batching your requests to manage noisier data streamsIf you need assistance with optimizing your webhook implementation or if you have any further questions, please don't hesitate to ask. If you require more in-depth support, you can request human assistance by clicking on "Talk to a person". Source: Import Data to Clay Using Webhooks
Channeled
APP
·
·
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Marielle C.
·
·
Is it possible to continue pushing the remaining leads the next day? just dont want to mess up the workflow
Marielle C.
·
·
Had the same issue in another clay table too: https://app.clay.com/workspaces/13635/tables/t_rgH9YXrTzPM3/views/gv_ZzZ7kZ6284En
Marielle C.
·
·
And in other clay tables as well, please let us know if its clay or leadmagic side, would really appreciate your assistance 🙏
Bruno R.
·
·
Hi Marielle, thanks for reaching out! Yes, Clay webhook tables have a 50k record limit for pushing records through a table. We also enforce some additional rate limits: * 10 records per second sustained rate * 20 records maximum burst capacity Could you share more context about the issue you're encountering with importing records to this webhook? From my end, it appears to be working correctly—I ran some tests, and the webhook seems to be monitoring as expected. Let me know where you're running into trouble, and I'd be happy to help further!
Marielle C.
·
·
Hi Bruno, the whole list is not pushing In this clay table it should be 11k but only 2.3k pushed https://app.clay.com/workspaces/13635/tables/t_rgH9YXrTzPM3/views/gv_ZzZ7kZ6284En In another table, it should be 13k but it run only until 7755 (the total of this table should be 19k (including the first webhook) https://app.clay.com/workspaces/344295/workbooks/wb_pdPEr5CtepAY/tables/t_xmVhiojGBKnu/views/gv_6YEt6A9RvtZF
Loading attachments
Bruno R.
·
·
I notice the tables now reflect 13k and 26k records, respectively. Could this have been a temporary refresh issue with the application responsible for pushing these records to Clay?
Marielle C.
·
·
Hi Bruno, i also contacted source of webhook which is leadmagic, i think the issue is from their side, thank you for your help
Daniela D.
·
·
Hey Marielle! Thanks for the reply. Let us know if you still run into any issues here.
❤️1
Channeled
APP
·
·
Hi Marielle C.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Channeled
APP
·
·
Thank you so much for sharing your feedback Marielle C.!