Talking to any system: REST and webhooks
Beezr can reach out to other systems, and other systems can reach in. Three tools cover both directions. This page helps you pick one.
Which one should I use?
Section titled “Which one should I use?”| You want to | Use | Where it lives |
|---|---|---|
| Call an app from the Integration hub, such as Slack or QuickBooks Online | The Integration step | A workflow step |
| Call any web service by its address | The REST API step | A workflow step |
| Let another system start a workflow | The From a webhook trigger | The workflow’s settings |
- Another system
- Webhook URL
- Workflow starts
- REST step calls back
The Integration step
Section titled “The Integration step”Use it first when your app is in the Integration hub. You choose a connection and an action, and the hub handles sign-in. See Connect an app and use it in a workflow.
The REST API step
Section titled “The REST API step”Use it for any other service. In the step you set the method (GET, POST, PUT, PATCH or DELETE), the address, and how to sign in: None, Username + password, API key or Bearer token. You can add headers and query parameters, and list the fields you want back under What comes back. Name the result under Result so later steps can use it.
The webhook trigger
Section titled “The webhook trigger”A webhook lets another system start a workflow by calling a URL.
- Create a workflow and, under When should it run?, choose From a webhook.
- Save it, then open its menu in the workflow list and choose Copy webhook URL.
- Paste the URL into the other system.
- Turn on Require an API key if callers must send one in the
api-keyheader. Create the key under API keys. - Turn on Send the result back if Beezr should post the outcome to your own URL. Add the Callback URL and choose when to send it: When the run fails, When the run succeeds or Always.
Inside the workflow, a JSON parser step can read the data the webhook sent.
Check yourself
What's next
Last checked