Troubleshoot webhooks, Zapier, and Make

Fix a hidden webhook address, events that never arrive, error codes, time-outs, duplicate records, and Zaps or scenarios that do the wrong thing.

Use this page when events between Spacebrain and Zapier, Make, or another app don't arrive, arrive twice, or cause the wrong result. Start with what you see. This page is for admins and anyone who builds automations with webhooks.

A webhook is a private web address that one app calls to tell another app something happened. First work out the direction: is Spacebrain sending to another app, or is another app sending to Spacebrain? Then find the last place that has a record of the event.

I can't see my webhook address

You see: Your webhook URL is hidden. Reveal it when you need to copy it to your automation.

Why: Spacebrain hides webhook addresses after setup because anyone who has one could send events into your workspace.

Fix: an Admin or Owner selects Reveal webhook URL in the same panel. The address shows only while the panel is open.

You see: An administrator can reveal or manage this webhook URL. Your role can't reveal it. Ask an admin.

For a custom email account, an admin can reveal the inbound address from the account's Edit window. If you see Webhook URL is unavailable. Reopen the account settings and try again., close and reopen Edit.

No events arrive

Check the connection belongs to the right workspace and shows Connected.
Check the event actually happened after you set up the webhook.
In Spacebrain, check Events Received and Last Event in the Zapier or Make panel. In Zapier or Make, check the task or run history.
Check the Zap or scenario is turned on.
Check the address in Zapier or Make matches the one Spacebrain gave you. If you set up the webhook again, the address changed.
Send one labelled test event and wait for the result before trying again.

The other app shows an error code

Code	What it means	What to do
401 or 403	The other app rejected the sign-in or permission.	Check the key or secret wasn't changed, cancelled, or entered in the wrong account.
404	The address doesn't exist.	Copy the address again from its source. The hook may be deleted, or you may be using a test address in live.
405	The other app doesn't accept that kind of request.	Use the setup the app's instructions describe. Don't guess.
400 or 422	The event arrived but the data didn't match what's expected.	Compare field names, date formats, and empty values with the app's sample, then fix the mapping.
429	Too many requests.	Wait, then send less often.
500 to 599	The other app had a problem.	Check its status page. See time-outs below before retrying.

Only use the sign-in and signature details shown in both apps' setup screens. Don't invent a header or secret format. For a form's webhook, use form webhook verification.

The request timed out

Why: the other app took too long to answer. It may still have done the work.

Fix:

Before retrying, search the other app for the record the event should have created.
If it's there, don't send the event again.
If the other app is often slow, have it acknowledge quickly and do longer work afterwards, if it supports that.

Events arrive twice or create duplicates

Why: retries after a time-out, two Zaps or scenarios listening to the same event, or someone triggering the action twice.

Fix:

Compare the event IDs and times of the duplicates.
Turn off any second Zap or scenario that handles the same event.
In your automation, look up the record by a stable ID or email before creating a new one. Don't match on name alone.

Zapier or Make runs, but the result is wrong

Open that exact Zap run or scenario run and check each step's input and output.
Look for old sample data, the wrong connected account, empty optional fields, filters, or a test destination.
Fix one mapping at a time and test with one labelled record before turning it back on.

Test Connection says Test failed

Fix: send a test event from Zapier or Make first, then select Test Connection in Spacebrain again. If it still fails, check the Zap or scenario is on and uses the current address.

I think a webhook address leaked

In the Zapier or Make panel, select Disconnect.
Set it up again with Generate Webhook URL to get a new address.
Paste the new address into Zapier or Make.
Check old test events are no longer processed.

Contact support

Open Help & support, select Contact, or see contact support. Include:

Direction (Spacebrain to the other app, or the other way).
Workspace, integration name, and event name.
The time of a test event, with time zone.
The error code and a short part of the error message.
The domain of the address only (for example hooks.zapier.com), not the full address.
How many times it was tried and what happened afterwards.

Never include the full webhook address, keys, secrets, or customer data.

Next step

Review setup in webhooks, Zapier, Make, and API keys.