Automation
Make
Start Make scenarios from portal events, and let scenarios create tasks and post messages in BravaSpace.
Free for 14 days. No credit card needed.
What it does
Connect Make to your client work.
- Portal events start scenarios
New clients and tasks, status changes and completed tasks, invoices sent and paid, client messages and files, as signed JSON to a Custom webhook.
Apps > API & webhooks, Webhooks - Scenario actions in BravaSpace
The HTTP module with an API key creates tasks, moves their status or posts a message to a client.
The client's plan and messages - Only what the key allows
Each API key has its own permissions, can expire, and reaches only your workspace; revoke it any time.
Apps > API & webhooks, API keys - Or the quick connect
Connect sends task, approval and message updates for the clients you switch on, through the Webhooks app.
The Webhooks Connection tab
How it works
Connect once. It keeps itself current.
- 1Custom webhook for triggers
In Make, add Webhooks, Custom webhook, and add its address as a webhook endpoint with the events you want.
- 2Send a test event
Make reads the example and learns its fields; filter on test = false.
- 3HTTP module for actions
Make a request to the BravaSpace API with an API key in the Authorization header. The setup guide has every field.
Before you start
What you need.
- A Make account (Custom webhooks and HTTP work on every plan).
- The owner or an admin of the workspace, to make the API key and the endpoint.
Setting it up
Where to find it.
- In Make, create a scenario and add the Webhooks module, Custom webhook.
- Add a webhook and copy the address it shows.
Make connects through Webhooks: in the app, Apps, API & webhooks has a step-by-step setup guide for it.
Data and privacy
What BravaSpace keeps, and what it can touch.
What is stored
The endpoint address and its signing secret (encrypted), 30 days of events and deliveries, and for each API key only a SHA-256 of it and its last four characters.
Access
Events are sent to your Custom webhook; a scenario reads and writes only what its API key allows, in this workspace only.
Disconnecting
Delete the endpoint and revoke the key under Apps > API & webhooks (or disconnect Webhooks for the quick connect); they stop at once. Turn the scenario off in Make too.
Questions
Make questions.
Portal events start scenarios; scenario actions in BravaSpace; only what the key allows; or the quick connect. Events are sent to your Custom webhook; a scenario reads and writes only what its API key allows, in this workspace only.
Make connects through Webhooks: in BravaSpace, Apps, API & webhooks has a step-by-step guide for it. In Make, create a scenario and add the Webhooks module, Custom webhook. Add a webhook and copy the address it shows.
The endpoint address and its signing secret (encrypted), 30 days of events and deliveries, and for each API key only a SHA-256 of it and its last four characters.
Delete the endpoint and revoke the key under Apps > API & webhooks (or disconnect Webhooks for the quick connect); they stop at once. Turn the scenario off in Make too.
Brava reads the error and suggests the fix. The common ones: Paste the full Custom webhook address, starting with https://hook.
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.