Webhooks let your other software tell BuilderComs about a change the moment it happens. When a job closes in your CRM, a task is finished in another app or a status changes on your scheduling board, that tool can send the update straight into BuilderComs, so your crew and clients see it without anyone retyping it.
Webhooks are live in the BuilderComs web app. The technical reference is at web.buildercoms.com/api-docs.
Webhook vs. API, in plain terms
The BuilderComs REST API is like calling the office to ask a question or make a change. A webhook is the other tool calling you as soon as something happens. Both use the same permissions, so a webhook cannot do anything the owner has not allowed.
The seven updates BuilderComs accepts
BuilderComs accepts seven kinds of incoming updates:
| Update | What it does |
|---|---|
| Job created | Starts a new job with its name, address and client |
| Job updated | Replaces a job's details, such as a new address |
| Job status changed | Marks a job active or completed |
| Task created | Adds a task, with an optional due date |
| Task updated | Changes a task's title or due date |
| Task completion changed | Marks a task done or reopens it |
| Message sent | Posts to the exact Team or Client conversation, including replies |
Each update is saved immediately. When BuilderComs answers "succeeded," the change is already on the job.
Built so updates don't double up
Jobsite connections drop and software retries. Every webhook carries its own ID, so if the same update arrives twice, BuilderComs saves it once. That means no duplicate client messages and no task appearing three times because a tool resent it.
The usual protections still apply. Updates are tied to your company, the owner has to approve the connection with read and write access, and access can be revoked at any time. A webhook cannot post as someone else or reach another company's jobs.
Where contractors use webhooks
- Sales to production: a won deal in your CRM creates the BuilderComs job automatically.
- Inspections: a passed inspection in another system marks the matching task done and posts a note to the Team thread.
- Closeout: finishing the final invoice marks the job completed in BuilderComs.
What you need
Your other tool has to be able to send a secure, signed-in update. Some tools do this out of the box, and others need a small connector built by your vendor or an automation service. Share the webhook reference with them; it includes a sample for each of the seven updates.
Want the big picture first? Read how BuilderComs integrations work, or see our integrations page.
Webhooks are included in BuilderComs, with no extra fee. See pricing or start a 7-day free trial.

