webhook implementation difficulties

[Akram_Boukhers]

Hey folks!

Hope y’all are doing good. So, here’s the thing - I’ve been geeking out and setting up this webhook workflow. You know, the usual fun stuff.

I’ve got this super basic form with just one field, the SIRET. Once that’s filled in, I hit up the Papers API with a GET request to grab the data tied to that SIRET. Testing it out, it’s been smooth sailing, and you can check out what I mean from the attached.

BUT… (yup, there’s always a “but”, right?) when I go full throttle and submit the real deal form, I’m met with this pesky 404 error. And the wild part? Everything’s peachy when I test through the Papers interface.

Anyone out there encountered something similar or got any cool tips to drop? Would be awesome to get some insights.

Catch you later and thanks in advance!
Akram

[coldrickjack]

Hi @Akram_Boukhers,

If I understand correctly everything works fine when you test the webhook in the workflow or when you use the Pappers UI to check the company information. The issue is when you actually convert on the live form that it returns an error?

I’ve very limited insight as I don’t have a Pappers account with API access and I can’t obtain one without a french professional email address but if a 404 is being returned we can assume that the SIRET supplied on the form is not being included as a parameter in the GET request.

One way of testing this is to setup an endpoint using a service like Pipedream and then checking to see what information is being received by the endpoint. This will at least confirm if the SIRET is being captured and passed successfully.

I’ve recorded a short video showing how I would approach this and hope it’s in some way helpful.

Pappers?

[Akram_Boukhers]

Thanks you for your post, this is really kind.
The problem was it’s impossible to connect my workflow to my localhost OF COURSE …
So I just use Ngrok for my appli…
Thank you again…
Good continuation

Akram