Instead of manually starting a Playbook, you can configure another application (like Zapier, a custom script, or an HTTP service) to call Lutra whenever new data is available, thereby automating your workflows.
How to Access Webhooks in Lutra
Open a Playbook: Navigate to the Playbook you want to trigger externally.
Click the “Webhook” Button: On the Playbook’s page, you’ll see a “Webhook” button. (See the screenshot you have showing where this button is located.)
Copy the Instructions: A dialog box with the Webhook URL, a unique token, and usage instructions will appear. Note: Once you close this dialog, you must add a new webhook to see these instructions again.
Set Up Your External Tool: Use the URL, token, and instructions to configure your external system (e.g., Zapier, a custom script, or cURL).
Tip: If you plan to connect multiple apps via webhooks, you can generate different webhook URLs (one per Playbook or scenario) for better tracking and security.
Core Concepts
URL & Token
Every Lutra webhook has a unique URL and an
X-Lutra-Webhook-Token.Keep these confidential—anyone with the token can trigger your Playbook.
Triggering the Run
Send a
POSTrequest to the webhook URL with your token in the header:X-Lutra-Webhook-Token: <YOUR_TOKEN_HERE>
Include a JSON body (if needed) to supply inputs to the Playbook.
Checking Status
The response to creating a run contains a
Locationheader.GETthat location (with the same token header) to see if the run is finished and fetch the result.
Result & Logs
Once the run is complete, Lutra returns
resultdata that you can retrieve.Check your Lutra Chat or Logs (if available) for detailed operation history.