Receives data that was sent to Parabola in a Webhook, or via an API POST to Parabola.
The Receive from webhook step is in beta, and is not available to use by everyone at this time. If you are interested in using this step, and the overall webhook feature, contact us!
The Receive from webhook step is a unique source in Parabola. It works in tandem with the Webhook feature, which allows your flows to run when triggered by an event from another system. This Pull, will bring the data from that triggering event into your flow. Webhooks are a common feature in many of your favorite tools, so setting up this step will require working with another tool at the same time.
The unique part of this Pull is that it cannot Pull data whenever it wants, like all other Pulls can. It can only Pull data when data is sent to it.
Webhooks are how tools can let each other know that events have occurred. Let's say that you have an online store, every time that a purchase is made, you could send a webhook from your payment processor to your email tool to send an email confirmation of the purchase. That webhook would be sent with information such as the customer, the items purchased, and the amount charged.
Generally, it is expected that once a tool receives a webhook, it will then process the data included with the webhook as needed.
The Receive from webhook step is the way for you to pull data from a webhook that your flow received and work with it. Every time your flow receives a webhook, the flow will begin running, and if you are using this Receive from webhook step, then data will be pulled.
In our example about the online shop, the purchase order would send a webhook to your Parabola flow, which would now have information such as the customer, the amount spent, and the items.
If your flow is running while another webhook comes in, or many other webhooks come in, those hooks will be queued up to run one after another. Parabola flows do not run in parallel, so each incoming webhook will need to wait in line to be processed.
Our expectation is no webhooks are dropped and all are successfully queued and processed. If you send a very large amount of webhooks to a flow at the same time, you may hit some limits.
The current version of the Receive from webhook step does not have a way to get data from a webhook into your builder. This make it generally difficult to build with this step because you do not have any data to see how your transformations are actually changing your data.
There are two ways to get data into this step:
To mock out data, enter valid JSON into the mock data field in the Receive from webhook step and click Update Settings.
To catch a real webhook from your published version, do as follows:
A webhook is an API request to a URL. Each Parabola flow has a URL that can be sent an API request by another tool to start your flow with some pieces of data.
For example, a webhook may look like this:
When your flow is sent that request, it will start your flow. The Receive from webhook step will have one row of data, with three columns, called id, amount, and customer. The values of those columns would be 1234, 50.00, and Sara Johnston.
If the request has any query parameters added to that Parabola webhook URL, they will also be included in the table of data Pulled.
Every Receive from webhook step will catch every hook that comes into your flow URL. So it is very difficult to have multiple services sending webhook data to the same flow. One flow per webhook source is best.