Automate Google Drive + Salesforce
Where the documents live — and pile up. 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.
Document Extractor is a ready-made agent built around Google Drive; 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 Drive event rather than a transcription of it.
When a file lands in a folder in Google Drive…
…an agent can update records and fields in Salesforce — after reading the context and deciding it should.
When a doc is updated in Google Drive…
…an agent can create tasks and notes in Salesforce — after reading the context and deciding it should.
When a file is shared in Google Drive…
…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 read and summarise documents in Google Drive — with the reasoning recorded in the run’s receipt.
When a task is due in Salesforce…
…an agent can file outputs into folders in Google Drive — with the reasoning recorded in the run’s receipt.
When a report cycle begins in Salesforce…
…an agent can export and convert formats in Google Drive — with the reasoning recorded in the run’s receipt.
Google Drive to Salesforce, in three nodes
Concretely: the google-drive-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": "2a2a4c91-c0af-49f1-a7e1-87144308c2d6",
"name": "Google Drive → Salesforce",
"nodes": [
{
"id": "d54053e4-e1de-4d05-ae59-24531c0160d2",
"text": "Watch Google Drive",
"x": 512,
"y": 144,
"isEditing": false,
"type": "google-drive-api",
"icon": "connect",
"category": "trigger",
"isSelected": false,
"parameters": {},
"description": "Interact with Google Drive to perform various operations on files and folders.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "6e563350-baa0-4490-a03e-bd9afece2a70",
"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 Drive item. Decide whether it warrants action in Salesforce, and explain why."
},
"description": "Decides whether this Google Drive item warrants anything in Salesforce.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "f8e716e2-69c2-4649-a75e-0dbbb4fdc556",
"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": "83c00539-877c-4fd2-a920-2bb9a970f558",
"start": {
"id": "d54053e4-e1de-4d05-ae59-24531c0160d2",
"type": "output"
},
"end": {
"id": "6e563350-baa0-4490-a03e-bd9afece2a70",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "fb092b3e-10d2-45dd-a45a-de6dcbcd16ae",
"start": {
"id": "6e563350-baa0-4490-a03e-bd9afece2a70",
"type": "output"
},
"end": {
"id": "f8e716e2-69c2-4649-a75e-0dbbb4fdc556",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Install Document Extractor
Document Extractor is a working agent built around Google Drive. 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
Build it in AGNT
- Install AGNT — it runs on your own machine and needs no account to start.
- Authorise Salesforce (one OAuth sign-in) and Google Drive (one OAuth sign-in). Nothing is stored anywhere but your disk.
- Describe the job in plain language, or paste the definition above; google-drive-api does the reading and custom-api the writing.
- Gate anything you would not want done unattended, then let it run and read the first receipt end to end.
Google Drive and Salesforce — common questions
Can I connect Google Drive to Salesforce without writing code?
Yes. Google Drive 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 file lands in a folder, update records and fields” — and the agent handles the rest.
How is this different from a field-mapping Google Drive 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 Drive, classify it against criteria you wrote in prose, draft something new, and act only when it is warranted.
Does my Google Drive and Salesforce data leave my machine?
Not to us. AGNT runs locally and both sets of credentials are encrypted on your own disk. Outbound traffic goes only to Google Drive, Salesforce and whichever model you chose — and pointing that at Ollama or LM Studio keeps everything on your hardware.
What does a Google Drive and Salesforce run leave behind?
Every run is recorded end to end — the Google Drive 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.
