Automate Google Sheets + Salesforce
The database every team already has open. 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.
Report Assembler is a ready-made agent built around Google Sheets; point its last step at Salesforce to finish this hand-off.
Automations teams run
Unlike field-mapping automation, the step in the middle is an agent: it can summarise, classify, judge and draft, not merely copy values from Google Sheets into Salesforce.
When a row is added or edited in Google Sheets…
…an agent can update records and fields in Salesforce — after reading the context and deciding it should.
When a sheet crosses a threshold in Google Sheets…
…an agent can create tasks and notes in Salesforce — after reading the context and deciding it should.
When a schedule fires in Google Sheets…
…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 append and update rows in Google Sheets — with the reasoning recorded in the run’s receipt.
When a task is due in Salesforce…
…an agent can read ranges for reporting in Google Sheets — with the reasoning recorded in the run’s receipt.
When a report cycle begins in Salesforce…
…an agent can maintain a rolling dashboard tab in Google Sheets — with the reasoning recorded in the run’s receipt.
Copy this Google Sheets → Salesforce workflow
Concretely: the google-sheets-api node on one side, a custom-api call to {instance}.my.salesforce.com on the other, and an agent in between that can decline. Deciding not to write into Salesforce is a recorded outcome, not a silent one.
{
"id": "0bb786d4-e2e6-4788-a1f7-86d4e60c79a8",
"name": "Google Sheets → Salesforce",
"nodes": [
{
"id": "28f65c6e-ce54-4ecf-af37-5b4f4f77fb82",
"text": "Watch Google Sheets",
"x": 512,
"y": 144,
"isEditing": false,
"type": "google-sheets-new-row",
"icon": "connect",
"category": "trigger",
"isSelected": false,
"parameters": {},
"description": "Listen for new rows added to a specified Google Sheet and trigger the workflow when a new row is detected.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "bf468dc2-942b-4839-a641-288d3d4c1d76",
"text": "Read it and decide",
"x": 512,
"y": 336,
"isEditing": false,
"type": "agnt-agent",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"instructions": "Read the Google Sheets item. Decide whether it warrants action in Salesforce, and explain why."
},
"description": "Decides whether this Google Sheets item warrants anything in Salesforce.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "fc7d137d-2d7f-498b-a51e-fe3a8436fe86",
"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": "POST"
},
"description": "Writes into Salesforce over its API.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
}
],
"edges": [
{
"id": "03adad69-c748-4158-a339-737fbb5a5760",
"start": {
"id": "28f65c6e-ce54-4ecf-af37-5b4f4f77fb82",
"type": "output"
},
"end": {
"id": "bf468dc2-942b-4839-a641-288d3d4c1d76",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "62e6975d-cc0f-45a9-a10d-d292ab6af486",
"start": {
"id": "bf468dc2-942b-4839-a641-288d3d4c1d76",
"type": "output"
},
"end": {
"id": "fc7d137d-2d7f-498b-a51e-fe3a8436fe86",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Install Report Assembler
Report Assembler is a working agent built around Google Sheets. 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
What building this looks like
- Get AGNT Community Core. Free, local, no sign-up needed to run a workflow.
- Add both connections to the vault — Google Sheets takes one OAuth sign-in, Salesforce takes one OAuth sign-in.
- Build the three 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 Sheets and Salesforce — common questions
Can I connect Google Sheets to Salesforce without writing code?
Yes. Google Sheets connects with one OAuth sign-in and Salesforce with one OAuth sign-in, both from the local credential vault. You then describe the job in plain language — “when a row is added or edited, update records and fields” — and the agent handles the rest.
How is this different from a field-mapping Google Sheets 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 Sheets, classify it against criteria you wrote in prose, draft something new, and act only when it is warranted.
Does my Google Sheets 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 Sheets, Salesforce, and your chosen model provider — which can be a local one.
What does a Google Sheets and Salesforce run leave behind?
Every run is recorded end to end — the Google Sheets items examined, the decision and its reasoning, the resulting Salesforce write. That record is what makes it reasonable to let this run unattended, and what lets you widen its remit on evidence.
