Push the three events that matter into anything
BuildersBridge fires an event when a lead arrives, an invoice is paid and an estimate is approved. Point those at Zapier's Catch Hook and you can land them in a spreadsheet, a Slack channel, a mailing list or anywhere else Zapier reaches.
- Direction
- One-way, BuildersBridge to Zapier
- Triggers
- lead.created, invoice.paid, estimate.approved
- Actions into BuildersBridge
- None — outbound events only
- Mechanism
- Zapier's Catch Hook (Webhooks by Zapier)
- Plans
- Every plan, no extra charge
- Setup
- Dashboard → Settings → Integrations
The three triggers
These are the moments where something outside BuildersBridge usually needs to happen: someone should be called, a number should be recorded, a document should be filed.
- lead.created — a new lead lands in the CRM
- invoice.paid — an invoice is marked paid
- estimate.approved — a client approves an estimate
Things people actually build with it
The pattern that comes up most is getting a number out of the product and into somewhere the owner already looks. A row appended to a Google Sheet, a message into the channel the office watches, a task created in whatever the team uses for follow-up.
The second pattern is speed to lead. A new lead firing into a phone notification or an SMS tool is the difference between calling back in five minutes and calling back tomorrow, and in residential work that gap decides who gets the job.
- New lead into Slack, SMS or a phone notification
- Paid invoice appended to a revenue spreadsheet
- Approved estimate creating a task in your project tool
- Any event into a mailing list or CRM you already run
Setting it up
In Zapier, create a Zap with Webhooks by Zapier as the trigger and choose Catch Hook. Zapier gives you a URL. Paste that URL into Dashboard → Settings → Integrations in BuildersBridge, and set a signing secret while you are there.
Trigger the event once — create a test lead — so Zapier can see the payload shape and let you map fields. After that the Zap runs on its own. No code, and no Zapier app to install, because this uses Zapier's generic webhook catcher rather than a published BuildersBridge app.
What it does not do
There are no Zapier actions into BuildersBridge. You cannot create a lead or raise an invoice from a Zap, because this is an outbound event stream rather than a two-way app integration. If your workflow needs to write into BuildersBridge, this is not the mechanism for it.
There is also no published BuildersBridge app in the Zapier directory, so you will not find it by searching Zapier for the name. You are building on Catch Hook, which is why setup involves pasting a URL rather than clicking Connect.
Questions
- Is there a BuildersBridge app in the Zapier directory?
- No. The integration uses Zapier's Webhooks by Zapier trigger with Catch Hook, so you paste a URL rather than connecting an account. That is why it works on any Zapier plan that includes webhooks.
- Can Zapier create records in BuildersBridge?
- No. Events flow out of BuildersBridge only. There are no inbound actions, so a Zap cannot create a lead, an estimate or an invoice.
- Which events are available?
- Three: lead.created, invoice.paid and estimate.approved. They fire regardless of your email notification settings, so turning off a notification email does not turn off the event.
- Is the payload signed?
- Yes, when you set a signing secret. Each request carries an x-buildersbridge-signature header containing an HMAC-SHA256 hex digest of the body. Zapier will accept the request either way, so the signature matters most when you are sending to your own endpoint.
- Does it cost extra?
- Not from us — it is on every plan. Zapier's own pricing depends on how many tasks your Zaps run.
Connect it on any plan
Calendar feeds, Zapier and webhooks are included on every plan — no add-on, no integration fee.