Issue with Pulling Data from Webhook: Source Not Configured Error

Amber Charitos · 2025-01-18 10:59:42.153055+00

Hi, since yesterday when using `Pull in data from webhook table` column I am getting `source is not configured` when no changes were made and the source has been configured for a few months. This is happening across multiple workbooks - anyone seen this before? Or have suggestions for resolving?

Issue with Pulling Data from Webhook: Source Not Configured Error | Clay

9 comments

· Sorted by Oldest

Channeled
APP
·
·
To resolve the "source is not configured" error, you'll need to check and potentially reconfigure your webhook source. Here's how to verify and fix the configuration: 1. Go to your table and click on the Source Column to open the Source column menu 2. Select "Sources" to view the connected source 3. Click on your webhook source 4. Click "Edit source" in the source panel that opens on the right 5. Verify that: • The webhook URL is still valid • The authentication token (if you're using one) is properly set up • All other source settings are correctly configuredIf the settings appear correct, try re-saving the configuration by clicking "Submit" to refresh the connection. Sources: Table sources overview | Documentation | Clay University Webhook integration guide | Documentation | Clay University
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!
Amber Charitos
·
·
The source menu is what I shared in the screenshot, no area to edit anything.
Bo (Clay)
·
·
Hey, thanks for reaching out, Amber! I do not see any mention of an error. On my end, everything looks good. I would recommend sending data again and it should appear. Can you let me know if that's fixed on your end? https://downloads.intercomcdn.com/i/o/w28k1kwz/1341339872/0de5018923113340b32cd6f748a1/CleanShot+2025-01-18+at+_34TNk3Qhda%402x.png?expires=1737221400&signature=11bc1aaae913e0c0f6895107b3a54ba47ffd9e53cead4b3c5a99a198b7b23cc8&req=dSMjF8p9lIlYW%2FMW1HO4zd6SJkuSWAFYHf64SbmSLzYdbj%2F80ZbZ2ypTcHKL%0AH9Ft%0A
Channeled
APP
·
·
Hi Amber Charitos! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Malik
·
·
This happened to me yesterday, and today just now as well Bo (Clay)
Loading attachments
Daniel Kupka (Clay)
·
·
Hey there, thanks for reaching out! ☺️ That's strange. May I ask what browser and resolution you are using? Also, can you do a hard reset for me? A hard refresh will clear the cache for the page that you're on and load the most recent version of the page. This can often resolve issues with outdated content or errors that have been fixed on the server side but are still being displayed due to cached data. Here are the steps you can follow depending on your operating system and browser: For Mac: * Chrome/Firefox: Press Cmd + Shift + R * Safari: Press Cmd + Option + R For PC: * Chrome/Firefox/Microsoft Edge: Press Ctrl + F5
Malik
·
·
I am using Chrome and for resolution, 1920x1080. The issue isn't happening anymore, but I will see if I can reproduce it and respond back if it happens again
owen (Clay)
·
·
Got it, appreciate you trying to recreate it though! If you continue to run into this let us know and we'll dive in deeper. :)

Channeled
APP
·
·
To resolve the "source is not configured" error, you'll need to check and potentially reconfigure your webhook source. Here's how to verify and fix the configuration: 1. Go to your table and click on the Source Column to open the Source column menu 2. Select "Sources" to view the connected source 3. Click on your webhook source 4. Click "Edit source" in the source panel that opens on the right 5. Verify that: • The webhook URL is still valid • The authentication token (if you're using one) is properly set up • All other source settings are correctly configuredIf the settings appear correct, try re-saving the configuration by clicking "Submit" to refresh the connection. Sources: Table sources overview | Documentation | Clay University Webhook integration guide | Documentation | Clay University
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!
Amber Charitos
·
·
The source menu is what I shared in the screenshot, no area to edit anything.
Bo (Clay)
·
·
Hey, thanks for reaching out, Amber! I do not see any mention of an error. On my end, everything looks good. I would recommend sending data again and it should appear. Can you let me know if that's fixed on your end? https://downloads.intercomcdn.com/i/o/w28k1kwz/1341339872/0de5018923113340b32cd6f748a1/CleanShot+2025-01-18+at+_34TNk3Qhda%402x.png?expires=1737221400&signature=11bc1aaae913e0c0f6895107b3a54ba47ffd9e53cead4b3c5a99a198b7b23cc8&req=dSMjF8p9lIlYW%2FMW1HO4zd6SJkuSWAFYHf64SbmSLzYdbj%2F80ZbZ2ypTcHKL%0AH9Ft%0A
Channeled
APP
·
·
Hi Amber Charitos! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Malik
·
·
This happened to me yesterday, and today just now as well Bo (Clay)
Loading attachments
Daniel Kupka (Clay)
·
·
Hey there, thanks for reaching out! ☺️ That's strange. May I ask what browser and resolution you are using? Also, can you do a hard reset for me? A hard refresh will clear the cache for the page that you're on and load the most recent version of the page. This can often resolve issues with outdated content or errors that have been fixed on the server side but are still being displayed due to cached data. Here are the steps you can follow depending on your operating system and browser: For Mac: * Chrome/Firefox: Press Cmd + Shift + R * Safari: Press Cmd + Option + R For PC: * Chrome/Firefox/Microsoft Edge: Press Ctrl + F5
Malik
·
·
I am using Chrome and for resolution, 1920x1080. The issue isn't happening anymore, but I will see if I can reproduce it and respond back if it happens again
owen (Clay)
·
·
Got it, appreciate you trying to recreate it though! If you continue to run into this let us know and we'll dive in deeper. :)