Sync activities two-way between BROSH AI CRM and Google Calendar

by Ben Ford · 3 views · created 2026-08-22 · CRM

What this workflow does

This workflow has 26 nodes and runs on Google Calendar events (event created) (plus 3 other triggers). Along the way it connects Google Calendar. It also calls mcp.brosh.io over HTTP.

How it runs

Trigger: On Google Calendar events (event created) (plus 3 other triggers).

1. Normalize Created Event (Code): runs custom JavaScript code
2. Normalize Updated Event (Code): runs custom JavaScript code
3. Normalize Cancelled Event (Code): runs custom JavaScript code
4. Prepare Poll Window (Code): runs custom JavaScript code
5. BROSH MCP - Search Activity by Google ID (HTTP Request): calls mcp.brosh.io (POST)
6. BROSH MCP - Search Changed Activities (HTTP Request): calls mcp.brosh.io (POST)
7. Parse BROSH Activity Search (Code): runs custom JavaScript code
8. Expand Changed Activities (Code): runs custom JavaScript code
9. BROSH Activity Found? (If): checks a condition and branches into true / false
10. Should Sync to Google? (If): checks a condition and branches into true / false

…plus 9 more steps. See the full node list below.

Services it uses

Google Calendar

HTTP calls to: mcp.brosh.io

Before you upgrade to n8n 3.0

Nodes used (7)

• Google Calendar Triggern8n-nodes-base.googleCalendarTrigger
• Coden8n-nodes-base.code
• HTTP Requestn8n-nodes-base.httpRequest
• Ifn8n-nodes-base.if
• No Operation, do nothingn8n-nodes-base.noOp
• Google Calendarn8n-nodes-base.googleCalendar
• Schedule Triggern8n-nodes-base.scheduleTrigger

From the author

Quick overview This workflow keeps Google Calendar events and BROSH AI CRM Activity records in sync in both directions, creating or updating BROSH Activities when events change in Google Calendar and polling BROSH for recently modified Activities to create or…

View the original on n8n.io → Check your own copy