Webhooks

A webhook is a URL that bildflow calls the moment something happens in your workspace. Go to Settings › API & integrations › Webhooks. Webhooks need the Growth plan or above, and only owners and admins can manage them. A workspace can have up to 10 endpoints.

If your workspace moves below Growth, events that happen meanwhile aren't sent, and deliveries still waiting are cancelled. Upgrading again doesn't send them later. You can still switch endpoints off, delete them and read their delivery log.

Add an endpoint

1. Select Add endpoint and paste the URL. It must start with https://. Private, local and internal addresses aren't allowed.
2. Choose the events, or tick All events.
3. Select Add endpoint, then Copy the signing secret. It starts with whsec_ and is shown only once.

Use the secret to check that each request really comes from bildflow. See Webhook payloads and signatures.

Events

• lead.created: a new lead from any source, with name, email, phone, source, project, preferences, who it was assigned to and UTM attribution. Internal notes are never sent.
• unit.status_changed: a unit becomes available, reserved, sold or delivered, with the old and new status and its price.
• reservation.signed: a buyer signs a reservation, with the unit, buyer, price and deposit.
• payment.recorded: a buyer payment is marked paid, with amount, currency, label, buyer and unit.
• booking.created: a viewing is booked, with the project, start and end time and the visitor's contact details. In the rare case that no lead could be created for the booking, lead.id, lead.name, lead.email and lead.phone are all null and no contact details are sent.

Each event includes only the personal data it needs. You're responsible for where you send it.

Test, log and resend

• Send test event sends a ping straight away and shows the result, for example "Delivered (200)" or "Failed: timeout". A failed test isn't retried, and test events never count toward switching an endpoint off.
• Delivery log lists the last 50 deliveries with the event, time, attempts, status code and duration. Deliveries are kept for 30 days.
• Resend sends a failed delivery again, with a fresh set of retries.
• Rotate secret replaces the secret at once, so update your receiver straight away.

Retries and switching off

Any 2xx answer within 10 seconds counts as delivered. Anything else, including a redirect, is a failed attempt. bildflow tries again after 1 minute, 5 minutes, 30 minutes, 2 hours, 6 hours and 24 hours (7 attempts in all), then marks the delivery failed.

After 20 consecutive failed attempts spanning at least 24 hours, the endpoint is switched off and owners and admins get a notification. Every retry counts as an attempt. Fix the receiver, then select Switch on.

Zapier, Make and n8n

Each of these tools gives you a URL to paste in as the endpoint:

• Zapier: create a Zap with the Webhooks by Zapier trigger and choose Catch Hook.
• Make: start a scenario with the Webhooks module and choose Custom webhook.
• n8n: add a Webhook node, set the method to POST and use its production URL.

Paste the URL into Add endpoint and select Send test event to check the connection. Then make one real event, for example a test lead, so the tool can see its fields. An event sends the same keys every time, and a value that's missing is null.