Webhooks, Zapier, Make, and API keys

Many apps in Integrations → Browse apps connect with an API key or a webhook address instead of a sign-in window. This guide shows you how to connect them, how to link Spacebrain to Zapier or Make, and how to keep webhook addresses private. It's for workspace admins who set up automations with other tools.

Before you begin

• Role: Admin or Owner. Other roles see Admin access required, and in a webhook setup they see An administrator can reveal or manage this webhook URL.
• For an API key: create a key in the other app, ideally one used only by Spacebrain, with only the permissions it needs.
• For Zapier or Make: an account where you can create a Zap or scenario.
• A test record: use test data for your first run.

How each app connects

Open an app in Browse apps. Its Authentication section shows one of these:

Apps marked Beta are still being tested. If a Connect button is missing or disabled, that app isn't available to you right now.

Connect an app with an API key

1. Go to Integrations → Browse apps and select the app.
2. Read what it does and select How to get API Key or Documentation if you need help finding the key.
3. Select Connect.
4. In Display Name, enter a name that says which account this is, for example "Calendly – sales team".
5. Paste the key. Use Show API key to check it, then Hide API key.
6. Select Connect.
7. Test the task you need, for example a booking or a data sync.

What you should see: Successfully connected to the app, and a Connected status with a Connected since date.

Spacebrain hides the key after saving. If you lose it, create a new one in the other app. If the key fails, check it's from the right account and region, hasn't expired, and has the permissions needed. Don't retry many times in a row. Some apps lock or cancel keys after repeated failures.

Connect Zapier or Make

Zapier and Make receive events from Spacebrain through a private webhook address.

1. Get your webhook address

1. Go to Integrations → Browse apps and select Zapier or Make.
2. Select Connect. The Webhook Integration panel opens.
3. Under Step 1: Generate Webhook URL, select Generate Webhook URL.
4. Under Step 2: Copy Webhook URL, select Copy to clipboard.
5. Check Supported Event Types to see which events Spacebrain can send. The list comes from your workspace, so use what's shown there.
6. Keep the panel open while you set up the other app.

2a. Set up Zapier

The panel's Setup Instructions walk you through it:

1. Log in to Zapier and create a new Zap.
2. Choose Webhooks by Zapier as the trigger.
3. Select Catch Hook as the trigger event.
4. Paste the webhook address where Zapier and the panel tell you to.
5. Send a test request.
6. Add the actions you want.
7. Turn the Zap on only after the test shows up in both Zapier and Spacebrain.

2b. Set up Make

1. Log in to Make and create a new scenario.
2. Add a Webhooks module as the first step.
3. Select Custom webhook.
4. Create a new webhook and paste the address.
5. Select Run once and send a test event.
6. Add the modules you want.
7. Turn on the scenario after you check the test data and mappings.

Zapier and Make change their screens from time to time. If their labels differ, follow their current screens and the instructions in the panel.

3. Test the connection

1. Send a test event from Zapier or Make.
2. Under Step 3: Configure Your Automation, select Test Connection.
3. Check Connection Details: Status, Events Received, Last Event, and Connected Since.

What you should see: Connection test succeeded. Then run one full test from start to finish and check:

• The event came from the right workspace.
• It updated the right contact or record.
• One event caused exactly one result, with no duplicates.
• Blank or missing fields don't break the automation.

Webhook addresses are hidden

A webhook address works like a password: anyone who has it could send events into your workspace. So Spacebrain hides it after setup.

• When you reopen the panel, you'll see Your webhook URL is hidden. Reveal it when you need to copy it to your automation.
• Only an Admin or Owner can select Reveal webhook URL. The address stays visible only while the panel is open.
• The same applies to the inbound webhook address for a custom email account. See Gmail, SMTP, and inbound email.

Keep the address safe:

• Don't put it in chats, tickets, screenshots, shared documents, or public pages.
• Use separate addresses for test and live workspaces.
• Limit who can edit your Zaps and scenarios.
• If it may have leaked, select Disconnect, then set it up again to get a new address, and update Zapier or Make.

Each webhook belongs to one feature

Spacebrain also uses webhook addresses for custom inbound email, Meta messages and leads, webinar attendance, payments, and form submissions. Each is created by its own feature. Don't paste a Zapier or Make address into Stripe, Zoom, or your email provider, or the other way round. For form webhooks, see form webhook verification.

Reconnect or disconnect

Use Reconnect when a key expires or you switch to a new key. Then test again.

Before you select Disconnect, turn off the Zaps, scenarios, and automations that use it. In Disconnect Integration, Spacebrain warns that the connection and any webhooks it created are removed. Afterwards, send a test event to check it's no longer processed. Turning off a Zap and disconnecting in Spacebrain are separate steps.

If something goes wrong

See also troubleshoot webhooks, Zapier, and Make.

FAQ

Why can't I see my webhook address anymore?

Spacebrain hides it after setup. An admin can reveal it again from the same panel.

Can I use one webhook address for two Zaps?

Each workspace connection has one address. Sending the same event to two Zaps can create duplicates, so plan which Zap handles what.

Next step

Build the automation that uses these events: automation workflows.