However, when it comes time to detect data and start building workflows off the webhook payloads. . . bubble appends “/initialize” to the workflow URL and instagram is trying to send the data to the URL it validated when it sent the get request (without “/initialize” appended).
So. . . the question - how do we get bubble to use the SAME URL for the get request needed to validate with meta/instagram AND the webhook post payload when detecting data to build out workflows.
Being able to manually define the data within JSON arrays could potentially fix the issue, but. . . from what I gather that’s a sensitive topic.
If I understand correctly, you’re saying have instagram send the get request to the URL with /initialize and somehow intercept that with postman to send the required validation response?
I’ve run into the exact same issue in the past, it’s really frustrating and I’m unsure why the initialize string is appended to it in the first place (makes the whole process quite clunky, but maybe there’s a good reason).
Thinking on my feet, would you be able to initialize the endpoint with instagram’s payload, then run through the same flow again on instagram but with the active endpoint instead? If insta is delivering the same JSON structure both times, hopefully that’d work.
I don’t think I could, instagram asks for a callback URL and sends the verification payload (a get request) to that URL, then instagram saves that url. If you try and edit it (i.e. add /initialize to the end.), you have to verify again and since a get request to the /initialize URL doesn’t trigger the workflow since it’s triggering on post request. . . you’re up a creek.
So the initialize step on bubble is effectively just a means of bubble understanding the JSON structure that you’ll be feeding to that endpoint. Once initialised (gonna start spelling that the English way now because it’s driving me mad), you should be able to just start the entire instagram flow fresh, using the endpoint w/o initialise, since it’s already active and understands what to expect.
