Two-Way Google Calendar ↔ BROSH AI CRM Sync (n8n Workflow)

Keep Google Calendar and BROSH AI CRM in perfect sync—both ways

This n8n workflow automatically mirrors updates between Google Calendar and BROSH AI CRM Activity records in both directions. When events change in Google Calendar, matching BROSH Activities are created or updated; when Activities change in BROSH, the corresponding Google Calendar events are created or updated—without creating update loops.

What this workflow does

• Listens for Google Calendar changes (create, update, cancel) on your selected calendar and triggers every minute.
• Normalizes event details including title, time range, location, description, and attendees, and builds sync metadata.
• Finds the linked BROSH Activity by searching BROSH via the BROSH MCP API using the stored Google event ID.
• Creates or updates BROSH Activities based on whether a linked Activity already exists.
• Polls BROSH for recent changes on a schedule to process Activities modified in the last 10 minutes.
• Prevents sync loops by skipping BROSH Activities that were just synced from Google Calendar.
• Creates or updates Google Calendar events depending on whether the BROSH Activity already contains a stored Google event ID.
• Writes back sync metadata, including the googleCalendarEventId field, to the BROSH Activity via the BROSH MCP API.

Use cases

• Ensure meetings and appointments automatically appear as BROSH AI CRM Activities with accurate timing and attendee context.
• When sales or support users update BROSH Activities, keep calendar events aligned without manual rework.
• Maintain clean bi-directional scheduling for SaaS operators managing customer meetings in one shared system.

Technical details

• n8n nodes / components: Google Calendar, HTTP Request, if, code, no op, sticky note.
• Google authentication: OAuth2 credentials for Google Calendar nodes (calendar defaults to primary).
• BROSH integration: BROSH MCP via HTTP Request using https://mcp.brosh.io/api/mcp and BROSH MCP OAuth2 credentials.
• Required BROSH fields: create Activity fields such as googleCalendarEventId (plus the workflow’s additional sync metadata field as defined in setup).