About this agent
Ships in the FieldCamp agent marketplace — because techs live in their phone calendars, and a schedule nobody looks at is a rumor.
Every shop has the two-calendars problem: the official schedule in the system, and the calendar the tech actually checks at breakfast. When they drift — a reschedule that didn't propagate, a new visit that never synced — the truck goes to the wrong place at the right time.
This agent makes drift impossible. Every scheduled or rescheduled visit writes through to the assigned tech's Google Calendar within moments — not as a bare block, but with a description worth reading: client, service, address, gate notes, and a travel buffer in front so back-to-backs stop being lies. Change the schedule in FieldCamp, and breakfast knows.
What it actually does
Trigger: Visit scheduled / rescheduled
- 1
Catches the change
visit_scheduledNew visits, reschedules, reassignments — anything that moves the truth.
- 2
Writes a description worth reading
compose_eventClient, service, address, access notes — the briefing, not just a time block.
- 3
Pads for the drive
add_travel_bufferTravel time in front of the visit, so the calendar reflects the day's physics.
- 4
Writes to the tech's calendar
sync_google_calendarThe assigned technician's Google Calendar, updated within moments of the change.
What you get
One calendar truth — what's in FieldCamp is what's on every tech's phone, buffers included.
A run, as you’d see it
Agent runs land on a timeline — what fired, what the agent found, and the action waiting for a human. This is that screen.
Visit rescheduled
#V-4501 → Thu 9 AM · Priya
Details
Synced to
Priya's Google Calendar
Summary
Moved Thursday's water heater install to 9 AM and rewrote the calendar event: client, address, 'gate code 4482' note, and a 35-minute travel buffer from her prior stop. Old slot cleared.
Syncs unattended — it writes calendars, never customers. Removing it leaves your calendars intact, just manual again.
By trade
Same agent, configured to how your vertical actually works.
Permit and inspection windows ride along in the event description.
Part numbers from the job land in the event, so the truck loads right.
Questions, answered
What shows up in the calendar event?
Client name, service, address, access notes, and a link back to the FieldCamp visit — plus a travel buffer ahead of the start. Configurable if you want leaner events.
Does it sync both directions?
FieldCamp → Google, deliberately. The schedule of record stays FieldCamp; the phone calendar is the always-true mirror. Two-way sync is how two calendars both become rumors.
What about techs who use Apple or Outlook calendars?
Google is the template default; other calendar targets connect through the same custom-connection mechanism during setup.