For quick tests or command-line integrations, you can use cURL to trigger a Lutra Playbook via the webhook.
Example cURL Command
bashCopycurl -X POST 'https://lutra.ai/api/webhooks/<WEBHOOK_ID>/runs' \
-H "X-Lutra-Webhook-Token: <YOUR_TOKEN>" \
-H "Content-Type: application/json" \
-d '{"condition":"heart attack","destination_sheet":{"id":"1234567890abcdef","mime_type":"application/vnd.google-apps.spreadsheet","name":"Heart Attack Clinical Trials"}}' \
-i
Explanation of the Options
-X POST: Sends a POST request.
URL: Replace
<WEBHOOK_ID>with the ID Lutra generated for you.X-Lutra-Webhook-Token: Your unique token from the webhook dialog.
Content-Type: application/json: Tells Lutra to expect JSON.
-d: Specifies the JSON payload for your Playbook’s inputs.
-i: Prints response headers so you can see the
Locationfor polling or check for errors.
Handling the Response
A
201 Createdindicates Lutra received your request successfully.The response body includes fields like
run_idandresult. Initially,resultmight benulluntil the run completes.Use the
Locationheader to check the run’s status, or view results in your Lutra Chat/logs.
Additional Tips and Best Practices
Security
Keep your
X-Lutra-Webhook-Tokensecret to prevent unauthorized triggers of your Playbook.Consider rotating or regenerating webhook tokens periodically for sensitive tasks.
Testing on Small Data
If your Playbook processes large data sets, test your webhook with minimal input first to confirm it works as intended.
Error Handling
If Lutra returns a non-
200or non-201status, you can parse the error message to debug.You can also check Lutra’s Chat or Playbook logs for more detailed error context.
Modifying Inputs
Some complex inputs (e.g., nested objects) may require the same structure you see in the webhook dialog’s example. If needed, you can revise your Playbook to accept simpler data types.
Image References
If you have a screenshot of the Webhook button on the Playbooks page, include it in each relevant page to guide new users.