Webhooks, Zapier, Make, and authentication

Spacebrain's general Integrations catalog is delivered by the active environment. Each catalog entry defines its category, authentication type, documentation link, beta state, and whether it is active. Consequently, two workspaces or deployments can show different providers even when the frontend recognizes the same integration family.

Use the signed-in catalog as the source of truth. A missing entry, inactive Connect button, Beta badge, Admin access required label, or disabled module means the provider is unavailable to that user or workspace at that time.

Authentication types

Only workspace managers or administrators can create a general catalog connection in the current interface. Existing connections can report Pending, Connected, Disconnected, Error, Expired, or Revoked. A green connection state proves stored authorization or setup state; it does not prove that the provider action required by your workflow succeeds.

Connect an API-key integration

1. Open Integrations and select a visible, active provider.
2. Review its description, category, beta state, requested credential label, and linked provider documentation.
3. Create a provider credential dedicated to the Spacebrain workspace when the provider supports that model.
4. Choose Connect.
5. Enter a meaningful display name that identifies the provider account or resource.
6. Paste the requested API key and complete the connection.
7. Perform a read and write test in the module that will consume it.

Use the narrowest provider permissions that still support the intended action. Store the source key in an approved secrets manager. Spacebrain's masked field is not a recovery mechanism; if the key is lost, use the provider's rotation process. Never reuse a production credential in a demo workspace.

If validation fails, confirm that the key belongs to the expected region, tenant, project, or account, has not expired, and includes the required provider scopes. Avoid repeated blind retries because some providers lock, rate-limit, or revoke credentials after abnormal use.

OAuth connections

For a provider whose current screen exposes a working OAuth authorization:

1. Verify the intended provider identity and organization before choosing Connect.
2. Review every requested permission at the provider.
3. Complete the provider redirect and return to Spacebrain.
4. Confirm the resource or account selected by the connection.
5. Test the exact provider operation in its owning module.

Dedicated flows such as Gmail, WhatsApp and Meta, and Zoom or Google Meet have provider-specific screens and should use those guides. Do not paste an OAuth authorization code, access token, refresh token, browser cookie, or callback URL into a generic API-key field or support ticket.

Set up Zapier or Make

Zapier and Make use the dedicated Webhook authentication path when their active catalog entries are configured as webhook-secret integrations.

Generate the Spacebrain URL

1. Open Integrations and select Zapier or Make.
2. Choose Connect to open the webhook setup drawer.
3. Choose Generate Webhook URL.
4. Copy the URL shown for the active workspace.
5. Keep the drawer open while configuring the provider.

The setup response can display Supported Event Types. Use the event names shown in your workspace rather than copying an event list from another workspace or this guide; the backend controls the current set.

Configure Zapier

The current Spacebrain drawer directs you to:

1. Sign in to Zapier and create a Zap.
2. Choose Webhooks by Zapier as the trigger.
3. Select Catch Hook.
4. Paste the Spacebrain-generated webhook URL into the workflow configuration as directed by the current Zapier and Spacebrain screens.
5. Send a test request.
6. Add the required Zap actions.
7. Publish only after the test event is visible in both systems.

Zapier's editor and field labels can change. If its current UI requests a provider-generated hook instead of accepting the Spacebrain URL in the displayed place, stop and compare the live instructions rather than moving secrets between fields experimentally.

Configure Make

The current Spacebrain drawer directs you to:

1. Sign in to Make and create a scenario.
2. Add a Webhooks module as the first step.
3. Select Custom webhook.
4. Create the webhook and paste the Spacebrain-generated URL as directed by the current Make and Spacebrain screens.
5. Choose Run once and send a test event.
6. Add the downstream modules.
7. Enable the scenario only after inspecting the captured sample and mappings.

Make's editor can also evolve independently. Treat the provider's current interface and the setup drawer returned for your workspace as authoritative.

Test and monitor the webhook

After sending a provider test event, choose Test Connection in Spacebrain. The drawer can show connection status, total events received, the last event time, and connection date. A successful test should be followed by an end-to-end workflow test that confirms:

1. The correct workspace received the event.
2. The payload maps to the intended contact, record, or action.
3. Required and optional fields behave correctly.
4. One provider event produces one intended outcome.
5. Retries or duplicate event identifiers do not create duplicate customer actions.
6. Invalid signatures or malformed requests fail safely.
7. Provider history and Spacebrain audit data provide enough information to reconcile a failure.

Protect webhook URLs and secrets

A webhook URL containing a workspace-specific secret is a capability credential. Anyone who has it may be able to submit events.

• Do not place it in public docs, source control, analytics properties, screenshots, issue trackers, or customer-visible pages.
• Send only over HTTPS and only to the provider field intended for the integration.
• Keep production and test workspace URLs separate.
• Restrict provider editor access and audit who can view the workflow.
• Disconnect and replace the setup when exposure is suspected.
• Avoid logging full URLs or payloads containing customer data.

Webhook systems are asynchronous. A timeout does not prove failure, and a retry can duplicate work. Inspect provider delivery history, Spacebrain event counts, the target record, and downstream actions before replaying an event.

Different webhook surfaces are not interchangeable

Spacebrain also uses provider callbacks for custom inbound email, Meta messaging and leads, webinar attendance, and payment-state synchronization. Those endpoints are generated and managed by their owning module. Do not copy a Zapier or Make URL into an email provider, Stripe, Commas, Meta, Zoom, or Google screen, and do not substitute one module's secret for another.

Reconnect or disconnect

Use Reconnect when a catalog connection is expired, revoked, or moved to a new provider credential. Reconfirm the selected account and repeat the end-to-end test.

Before Disconnect, inventory active Zaps, Make scenarios, workflows, forms, campaigns, and scheduled actions. Disable or repoint the provider workflow, then disconnect in Spacebrain and verify that new test events are rejected or no longer processed. Provider-side workflow disablement and Spacebrain disconnection are separate actions.