Forum Discussion
AustinK
5 years agoQrew Commander
Without seeing your webhook and how you set it up and exactly how you are triggering it it is tough to say. If you can provide screenshots of those things it may help. If you are getting a 404 error I would look at your end point URL for sure.
There shouldn't be anything different really. Make sure your user token is set up for the right app. IF you have app tokens enabled on your app(by default they are I think) then you may need to provide the app token as well. Sometimes the user token can be substituted but not in every case so it is worth checking.
There shouldn't be anything different really. Make sure your user token is set up for the right app. IF you have app tokens enabled on your app(by default they are I think) then you may need to provide the app token as well. Sometimes the user token can be substituted but not in every case so it is worth checking.
- EvanMartinez5 years agoQuickbase StaffHi John,
I would agree with Austin that usually when the issue is a User Token you get an authentication error back. The most common reason to get an issue with a 404 error on a Webhook usually has to do with the endpoint. You would want to make sure that the account URL is set to the correct realm (for example it might need to be mycompanyname.quickbase.com instead of university.quickbase.com and that you have updated to DBID to the correct application and table (sometimes a character can get cut off or if the DBID isn't updated to the right target table you can run into these issues. The DBID would be the portion after the example.quickbase.com/db/, it is usually in a combination of letters and numbers and would need to point to the right destination table in the account url you are referencing. I hope those suggestions are helpful.
------------------------------
Evan Martinez
Community Marketing Manager
Quick Base
------------------------------
Related Content
- 6 months ago
- 4 days ago
- 4 months ago
- 7 months ago