Step 3 - Note down the webhook URL
You will use this URL to send your webhooks from the 3rd party app which you are setting up. This webhook supports all methods (GET, POST, PUT, DELETE…)
Step 4 - Create a new “STEP” in your workflow
This step will basically take your incoming webhook and forward it to your Bubble backend api workflow aka api endpoint.
Step 8 - Chose all the types of data you want to forward to your bubble workflow
To keep this guide simple, I will only choose to forward the “data” aka “body” of the incoming hook.
STEP 9- Chose the “+method” from “optional” and from the drop-down list chose the “POST” method. This method will be used to forward the webhook to Bubble.
Step 10 - Go ahead TURN OFF the “structured mode” and simply pass the data param which you received from the trigger step. Using the drop-down list and at the end press the “select path”
Important Note - Once you have successfully initialized the workflow in Bubble, Do not forget to go back in Pipedream and remove the/initialize from the URL and hitting DEPLOY again
Hey @shawnmi6, thanks! I’ve never used Pipedream but it looks great! (even has cron scheduler) I’ve done this with a couple of other services but they were a bit of a pain to setup. Look forward to giving this a try.
Great thread and solved a big problem for me! One issue I’m running into though is that it works in my /version-test/, but it’s not working in my Live application. I created duplicate workflows in Pipedream, other than updating the URL and have them both active. The one going to the development instance works, but the live version does not.
I tried setting Pipedream with /initialize first (point to Live URL), but I get an error code 404. As-is, without trying to redo the initialize I get an error code 400 (screenshot below):
Thanks @shawnmi6 . I was able to figure it out finally. It wasn’t anything wrong with Pipedream, it was a step in the Bubble workflow after what the webhook was doing. Tough to figure out from the error message!
