Guidelines for Creating the Perfect JSON Format for Zapier Data

Stephen J. · 2024-10-31 00:41:17.271501+00

Hi there – looking for tips on the definitive format for the JSON body for sending my data to Zapier. Trying a bunch of different things all of them deliver an error…

Guidelines for Creating the Perfect JSON Format for Zapier Data | Clay

10 comments

· Sorted by Oldest

Bo (.
·
·
Hey, thanks for reaching out Can you send us the table url?
Stephen J.
·
·
Thanks Bo. Here’s the public link to the table. I’m stuck on two things:
Good formatting of the JSON to send the info back to Zapier
Whether I can have that triggering automatically, or do I have to do it manually?
Current workaround is sending it to Airtable automatically, then back to Notion, since I can’t see how webhooks can fire automatically. Thanks
Daniel K.
·
·
Hi Stephen! I think you forgot to send the table link :) Happy to look at your setup!
Stephen J.
·
·
Aha! Yep. How about this: https://app.clay.com/shared-table/share_EWF7vNKbvd6d
Bruno R.
·
·
Hi Stephen, thanks for reaching out! It looks like the endpoint you’re using for Zapier may be incomplete or incorrect. When setting up a webhook in Zapier, be sure to copy and paste the entire URL provided to ensure it works properly. https://downloads.intercomcdn.com/i/o/w28k1kwz/1235382858/0cd9bca20a42139ccaa897f0da40/CleanShot+2024-10-31+at+11_06_35%402x.png?expires=1730389500&signature=76d9a1ca0d790df71158a66ca087734b72f4d4b69a196f012c88239b4f01c005&req=dSIkE8p2n4laUfMW1HO4zW0D5xdsjdO2x%2Bse3zUjTjkvj8gAichKVrYnihTn%0Ak%2BAx%0A As for your question on how to effectively structure your JSON body for the HTTP API enrichment column - we recently made some changes to our HTTP API enrichment column: In JSON, numbers are unquoted to enable arithmetic operations, while strings are quoted to preserve their exact format, including special characters or leading zeros. Quotation marks distinguish text data from numeric values for parsing and accurate data interpretation. In our recent update to the HTTP API enrichment column, we aligned it with standard JSON structuring practices. Here's a video going over these updates as well: https://www.loom.com/share/5eb34faae5574887b26d90d9c68d1440. I hope this was helpful.
Stephen J.
·
·
Thanks Bruno. Is it possible to get the webhook to trigger automatically or on a regular basis?
Bruno R.
·
·
Webhooks are designed to respond to specific triggers. Once you publish the Zap, data will automatically stream for each Clay table record added and pushed through the HTTP API.
Stephen J.
·
·
Ok thanks Bruno, will check it out and let you know if issues
Channeled
APP
·
·
Hi Stephen J.! 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 Stephen J.!

Bo (.
·
·
Hey, thanks for reaching out Can you send us the table url?
Stephen J.
·
·
Thanks Bo. Here’s the public link to the table. I’m stuck on two things:
Good formatting of the JSON to send the info back to Zapier
Whether I can have that triggering automatically, or do I have to do it manually?
Current workaround is sending it to Airtable automatically, then back to Notion, since I can’t see how webhooks can fire automatically. Thanks
Daniel K.
·
·
Hi Stephen! I think you forgot to send the table link :) Happy to look at your setup!
Stephen J.
·
·
Aha! Yep. How about this: https://app.clay.com/shared-table/share_EWF7vNKbvd6d
Bruno R.
·
·
Hi Stephen, thanks for reaching out! It looks like the endpoint you’re using for Zapier may be incomplete or incorrect. When setting up a webhook in Zapier, be sure to copy and paste the entire URL provided to ensure it works properly. https://downloads.intercomcdn.com/i/o/w28k1kwz/1235382858/0cd9bca20a42139ccaa897f0da40/CleanShot+2024-10-31+at+11_06_35%402x.png?expires=1730389500&signature=76d9a1ca0d790df71158a66ca087734b72f4d4b69a196f012c88239b4f01c005&req=dSIkE8p2n4laUfMW1HO4zW0D5xdsjdO2x%2Bse3zUjTjkvj8gAichKVrYnihTn%0Ak%2BAx%0A As for your question on how to effectively structure your JSON body for the HTTP API enrichment column - we recently made some changes to our HTTP API enrichment column: In JSON, numbers are unquoted to enable arithmetic operations, while strings are quoted to preserve their exact format, including special characters or leading zeros. Quotation marks distinguish text data from numeric values for parsing and accurate data interpretation. In our recent update to the HTTP API enrichment column, we aligned it with standard JSON structuring practices. Here's a video going over these updates as well: https://www.loom.com/share/5eb34faae5574887b26d90d9c68d1440. I hope this was helpful.
Stephen J.
·
·
Thanks Bruno. Is it possible to get the webhook to trigger automatically or on a regular basis?
Bruno R.
·
·
Webhooks are designed to respond to specific triggers. Once you publish the Zap, data will automatically stream for each Clay table record added and pushed through the HTTP API.
Stephen J.
·
·
Ok thanks Bruno, will check it out and let you know if issues
Channeled
APP
·
·
Hi Stephen J.! 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 Stephen J.!