Automation
Webhooks
Signed JSON for tasks, approvals and messages, sent to your own https address.
Free for 14 days. No credit card needed.
What it does
Connect Webhooks to your client work.
- Portal events as signed JSON
New tasks, status changes, client approvals and comments, and new messages.
Your endpoint - Verifiable
Every request carries X-Brava-Signature, an HMAC-SHA256 with a signing secret shown once.
Your server - You choose the clients
Only the clients switched on send events.
This app's Connection tab
How it works
Connect once. It keeps itself current.
- 1Connect an https endpoint
A ping event is sent to check it; copy the signing secret shown once.
- 2Switch clients on
Pick which clients send events.
- 3Delivered in order
Events go out on the scheduled run, oldest first, a failing one retried up to five times.
Before you start
What you need.
- An https address on the public internet that answers with a 2xx status.
Setting it up
Where to find it.
- Use the https address of the server, Zapier Catch Hook or Make Custom webhook that should receive events.
In the app, Connect Webhooks opens a guided setup with Brava: it asks for each thing in turn, tests the connection and tells you it is working.
Data and privacy
What BravaSpace keeps, and what it can touch.
What is stored
The endpoint URL and signing secret, encrypted in a table no browser can read, and a week of queued events (text cut to 500 characters).
Access
Sends only: events go to that address; nothing is read back.
Disconnecting
Disconnect on this page: the URL, the signing secret and the client switches are deleted.
Questions
Webhooks questions.
Portal events as signed JSON; verifiable; you choose the clients. Sends only: events go to that address; nothing is read back.
Open Connect Webhooks in BravaSpace and paste the endpoint URL; Brava tests the connection before saving it. Use the https address of the server, Zapier Catch Hook or Make Custom webhook that should receive events. Then match each client to their clients that send.
The endpoint URL and signing secret, encrypted in a table no browser can read, and a week of queued events (text cut to 500 characters).
Disconnect on the Webhooks app page in BravaSpace: the URL, the signing secret and the client switches are deleted.
Brava reads the error and suggests the fix. The common ones: Use an https address on the public internet (not localhost or a private network). The endpoint did not answer with a 2xx status. Check it accepts POST requests.
Try it with one client.
Add some work. Share a file. Ask for feedback. See what your client sees, with your name on it. Free for 14 days. No credit card needed.