The job schedule, in the calendar you already check
BuildersBridge publishes your schedule as a private calendar feed. Subscribe to it once in Google Calendar and jobs, inspections, deliveries and task due dates sit alongside everything else in your week, updating on their own.
- Direction
- One-way, BuildersBridge to Google
- What appears
- Scheduled work, inspections, deliveries, task due dates
- Window
- 30 days back, 180 days forward
- Refresh
- Automatic; the feed caches for 5 minutes
- Plans
- Every plan, no extra charge
- Setup
- Dashboard → Settings → Integrations
What shows up
Scheduled work from your projects, carrying the event title, its type and the project it belongs to, so a calendar entry tells you which job it is without opening anything. All-day items stay all-day; timed items keep their times.
Task due dates come through as well, which is the part people do not expect and then rely on. A task with a date on it is a commitment, and it belongs in the same place as the rest of your week.
- Scheduled jobs and site visits
- Inspections
- Deliveries
- Task due dates
How to connect it
Open Dashboard → Settings → Integrations and turn the calendar feed on. BuildersBridge mints a private address for your organisation. Copy it, then in Google Calendar choose Other calendars → From URL and paste it in.
Google then polls that address on its own schedule. There is nothing to install, no Google account to connect to BuildersBridge, and no permissions to grant — the feed is a read-only address, which is why it works the same way on Apple Calendar and Outlook.
It is read-only, and that is deliberate
Changes made in BuildersBridge appear in Google Calendar. Changes made in Google Calendar do not come back. Dragging an event in Google moves it in Google only, and the next refresh will put it back where the schedule says it should be.
That is the honest trade for a feed with no account connection and no permissions. If two systems can both write, one of them has to win a conflict, and the one that should win is the schedule your crew is working from.
The address is the credential
The feed URL contains a 256-bit token, and that token is the whole credential — anyone holding the address can read the schedule. This is the same model Google itself uses for secret calendar addresses, and it is what makes subscribing possible without an OAuth connection.
The practical consequence: treat the address like a password. Do not post it in a shared document or a group chat. If it does get out, rotating or disabling the token in Settings kills the old address immediately, and subscribers simply stop receiving updates.
Questions
- How often does Google Calendar update?
- Google decides how often it polls a subscribed feed, and it is typically a few hours rather than instantly. The feed itself caches for five minutes, so the delay you see is almost always Google's polling interval, not ours.
- Can I edit BuildersBridge events from Google Calendar?
- No. The feed is read-only. Edit the schedule in BuildersBridge and the change flows out; an edit made in Google affects only your own copy until the next refresh overwrites it.
- How far ahead does the feed go?
- Thirty days back and one hundred and eighty days forward, capped at 500 events. That covers a jobsite calendar comfortably without dragging years of history into your personal calendar.
- Does every crew member need their own feed?
- The feed is per organisation, not per person, so everyone subscribing sees the same schedule. Because the address is the credential, share it the way you would share a password rather than posting it somewhere open.
- Is it included in my plan?
- Yes. Calendar feeds, Zapier and CSV export are on every plan at no additional charge.
Connect it on any plan
Calendar feeds, Zapier and webhooks are included on every plan — no add-on, no integration fee.