Trigger Automations With an Incoming Webhook
Give an automation its own private URL so other tools — forms, Zapier, your own scripts — can start it by sending an HTTP request.
An incoming webhook lets something outside Bluprint start an automation. Instead of waiting for a record to change or a schedule to tick, the automation gets its own private URL — and whenever another tool sends an HTTP request to that URL, the automation runs.
This is how you connect Bluprint to tools that aren't built-in integrations: a website contact form, a Zapier or Make scenario, a Google Form, or a script you wrote yourself. New to automations? Start with Automations Overview.
When to Use One
Reach for a webhook trigger when the thing that should start your automation happens somewhere Bluprint can't see:
- A brand submits your sponsorship form → create an in-app notification for the team.
- A new sale fires in your store → post it to Slack.
- Your own script finishes rendering a video → update an Idea.
If the trigger is something inside Bluprint (a record changed, a comment was posted, a date arrived), use one of the built-in triggers instead — you won't need a webhook.
Set It Up
- Choose the Incoming webhook trigger
In the builder, select the WHEN card and pick Incoming webhook. The config panel shows a unique URL and a secret token for this automation.
- Copy the URL and secret
Copy the webhook URL and its secret token. You'll paste both into whatever tool is going to call it.
- Add a sample payload (optional)
Paste an example of the JSON body the caller will send. Bluprint uses it so you can test the automation and so the payload's fields show up as
{{ row.* }}tokens in your actions. - Add your actions and enable it
Build the DO actions as usual, referencing the incoming data with
{{ row.field }}tokens, then flip the automation on.
Calling the Webhook
Send an HTTP POST to the URL and include the secret so Bluprint knows the call is genuine. The simplest way is to pass the token as a query parameter:
curl -X POST "https://<your-webhook-url>?token=<your-secret>" \
-H "Content-Type: application/json" \
-d '{ "title": "New sponsor inquiry", "email": "brand@example.com" }'
Every field in that JSON body becomes a token you can use in your actions — here, {{ row.title }} and {{ row.email }}.
Keep the Secret Safe
The secret token is what stops strangers from firing your automation. Treat it like a password:
- Only paste it into tools you trust.
- Don't commit it to a public repo or share it in a public channel.
- If it ever leaks, regenerate it from the builder. Regenerating immediately invalidates the old token, so update every caller afterward or they'll stop working.
Test Before You Rely On It
Use Run test in the builder to fire the automation against your sample payload without needing the external tool wired up yet. Then check Execution Logs to confirm the actions did what you expected.
Pair It With an Outgoing Request
A webhook trigger brings data in; the Send an HTTP Request From an Automation action sends data out. Together they let Bluprint sit in the middle of your stack — receive an event, then call another service in response.