URL structure for actions
Not sure if i'm being stupid or if i'm taking the wrong approach entirely here.
I'm trying to build a webhook handler for Pipedrive's CRM.
I've created a model called pipedriveDeal, added the fields, and have created a custom action for the model to take in pipedrive's generated webhook and process it into a record to be created/updated as needed.
I'm now at the testing stage and am trying to test it by firing off webhooks from pipedrive, but am getting nothing but 404's I have temporarily set the action to allow unauthorized calls.
I've tried a few variations and am currently firing off the webhooks to https://<my app>--development.gadget.app/api/models/pipedriveDeal/actions/webhook/
Is this an incorrect url structure? Can model actions not be called externally? Am i just an idiot to be taking this approach in the first place?
8 Replies
Unknown User•14mo ago
Message Not Public
Sign In & Join Server To View
That makes a ton of sense, thank you
Still getting 404's oddly.
Route POST:/api/integrations/pipedrive/webhooks/ not found
Just to check here, does a file at api/routes/integrations/pipedrive/webhooks/POST.js
become accessible to a POST api call at
https://<my app>--development.gadget.app/api/integrations/pipedrive/webhooks/Unknown User•14mo ago
Message Not Public
Sign In & Join Server To View
i'll try a manual test from postman, as pipedrive wants all webhook urls to end in /, = or ?
for some bizarre reason
i added a GET endpoint in the same folder for testing and noticed this shows up to give me the routes
however that isnt present in the POST
yes it looks as though it is the trailing /
as i can now hit it albeit with errors i need to fix, thank you
Any suggestions for which of these characters i could end the url with without messing up the routing?
The joys of Pipedrive's bizarre arbitrary requirements 🙄
? seems to work