Automate Google Calendar + Salesforce
The shared clock your workflows can read and write. The enterprise system of record for revenue. Put an agent between them and the hand-off stops being manual: it reads, decides, acts, and shows its work.
Meeting Follow-Through is a ready-made agent built around Google Calendar; point its last step at Salesforce to finish this hand-off.
Automations teams run
Each of these runs with a reasoning step between the two tools, so what reaches Salesforce is a decision about the Google Calendar event rather than a transcription of it.
When an event starts or ends in Google Calendar…
…an agent can update records and fields in Salesforce — after reading the context and deciding it should.
When a meeting is created in Google Calendar…
…an agent can create tasks and notes in Salesforce — after reading the context and deciding it should.
When a day begins in Google Calendar…
…an agent can extract report data in Salesforce — after reading the context and deciding it should.
When a lead or opportunity changes in Salesforce…
…an agent can create or move events in Google Calendar — with the reasoning recorded in the run’s receipt.
When a task is due in Salesforce…
…an agent can add agendas to invites in Google Calendar — with the reasoning recorded in the run’s receipt.
When a report cycle begins in Salesforce…
…an agent can block focus time in Google Calendar — with the reasoning recorded in the run’s receipt.
The Google Calendar and Salesforce hand-off, setup template
Start with the google-calendar-api node and a custom-api call to {instance}.my.salesforce.com. Configure the Google Calendar source payload, the agent input, and the Salesforce operation. The sequential template does not implement conditional writes or approval by itself.
This is a schema-checked starting point, not an end-to-end tested automation. Replace every CONFIGURE_ value, choose the operations you intend, connect credentials and map source outputs into later inputs. An edge orders steps; it does not supply a condition, an approval gate or a field mapping. Add and test those controls explicitly before any write. Cloud APIs and model providers may receive data. Keep the workflow inactive until tested with fixtures.
{
"id": "5db17462-f8d9-4272-ad99-3280f635f0fc",
"name": "Google Calendar → Salesforce",
"nodes": [
{
"id": "9d39cea2-3d91-4ff5-a4fe-af4bd27eb252",
"text": "Watch Google Calendar",
"x": 512,
"y": 144,
"isEditing": false,
"type": "google-calendar-new-event",
"icon": "connect",
"category": "trigger",
"isSelected": false,
"parameters": {
"calendarId": "CONFIGURE_CALENDARID"
},
"description": "Setup template for Google Calendar New Event. Listen for events created or updated on a Google Calendar and trigger the workflow. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "219729e1-65e0-4c00-ad4f-d59997146430",
"text": "Review source and draft",
"x": 512,
"y": 336,
"isEditing": false,
"type": "agnt-agent",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"agentId": "CONFIGURE_AGENTID",
"message": "Read the Google Calendar item. Decide whether it warrants action in Salesforce, and explain why.\nSource input: CONFIGURE_SOURCE_INPUT. Produce a reviewable draft only; do not take external actions."
},
"description": "Setup template for Agent Chat. Chat with an AI agent from your agent library. Select an agent and send messages to interact with it within your workflow. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "b7b20769-77af-4aff-acfd-4a82d2ec7b9a",
"text": "Call Salesforce",
"x": 512,
"y": 528,
"isEditing": false,
"type": "custom-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"url": "https://{instance}.my.salesforce.com/services/data/v59.0/sobjects/Contact",
"method": "GET",
"authType": "None",
"query": "",
"headers": "{}"
},
"description": "Setup template for Custom API Request. This action node makes a custom API request to any endpoint with configurable method, headers, and authentication. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
}
],
"edges": [
{
"id": "b2d4c0c7-58fb-4524-ac86-7c35e26ba318",
"start": {
"id": "9d39cea2-3d91-4ff5-a4fe-af4bd27eb252",
"type": "output"
},
"end": {
"id": "219729e1-65e0-4c00-ad4f-d59997146430",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "29d98c18-bbbc-40c8-adcb-96a407acc210",
"start": {
"id": "219729e1-65e0-4c00-ad4f-d59997146430",
"type": "output"
},
"end": {
"id": "b7b20769-77af-4aff-acfd-4a82d2ec7b9a",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Configure Google Calendar New Event
Listen for events created or updated on a Google Calendar and trigger the workflow.
- calendarId — Calendar ID to monitor (defaults to 'primary') Current example:
CONFIGURE_CALENDARID.
Configure Custom API Request
This action node makes a custom API request to any endpoint with configurable method, headers, and authentication.
- url — The URL of the API endpoint Current example:
https://{instance}.my.salesforce.com/services/data/v59.0/sobjects/Contact. - method — The HTTP method for the request Current example:
GET. - authType — The type of authentication Current example:
None. - query — Query parameters for the request (e.g., 'key1=value1&key2=value2') Current example:
. - headers — Optional headers for the request. e.g., {"Content-Type": "application/json"} Current example:
{}.
Install Meeting Follow-Through
Meeting Follow-Through is a working agent built around Google Calendar. Install it, point its last step at Salesforce, and you have this hand-off without building it from an empty canvas.
Runs on your own machine · See what it does
Wiring Google Calendar to Salesforce
- Get AGNT Community Core. Free, local, no sign-up needed to run a workflow.
- Add both connections to the vault — Google Calendar takes one OAuth sign-in, Salesforce takes one OAuth sign-in.
- Configure the nodes above, or start from a marketplace workflow and edit it. The agent in the middle is the part worth spending time on.
- Run it once with an approval gate in place. The receipt tells you what it read, what it concluded, and what it changed in Salesforce.
Google Calendar and Salesforce — common questions
Can I connect Google Calendar to Salesforce without writing code?
No code is required. Add both connections in the vault (Google Calendar uses one OAuth sign-in, Salesforce uses one OAuth sign-in), then either install a marketplace workflow for this pair or drag the two nodes onto the canvas and put an agent between them.
How is this different from a field-mapping Google Calendar to Salesforce automation?
Mapping tools move data; this reasons about it. Rather than copying a field into Salesforce, the agent can weigh what arrived from Google Calendar, classify it against criteria you wrote in prose, draft something new, and act only when it is warranted.
Does my Google Calendar and Salesforce data leave my machine?
Your credentials stay in a vault on your own disk rather than in someone else’s cloud. The only calls made are the ones the workflow needs: Google Calendar, Salesforce, and your chosen model provider — which can be a local one.
What does a Google Calendar and Salesforce run leave behind?
You get an auditable trail rather than a success flag. It shows the Google Calendar context the agent worked from, the judgment it made about hygiene enforced across the pipeline, and the exact change applied in Salesforce, with approvals attached where you required them.
