Operator
← All integrations
Google Drive logo+Salesforce logo

Connect Google Drive to Salesforce

Automate Google Drive and Salesforce with AI

Salesforce records should point at the Drive folder where contracts and decks actually live. On Operator.io, an OpenClaw agent connects Drive and Salesforce so opportunity stage changes can require the latest Drive file, Salesforce uploads can land in the mapped Drive path, and reps can ask for files on an account without searching manually. Hand it an opportunity ID and it returns Salesforce fields with Drive links beside them.

It reaches both apps directly or through connectors like Composio MCP and Pipedream MCP, which handle the sign in and token refresh, so there is no Zap to build and no API keys to paste.

What your agent can do with Google Drive and Salesforce

What your agent does in Google Drive

  • Insert File Parent (v2)

    Tool to add a parent folder for a file using Google Drive API v2. Use when you need to add a file to an additional folder.

  • Insert Property (v2 API)

    Tool to add a property to a file, or update it if it already exists (v2 API). Use when you need to attach custom key-value metadata to a Google Drive file.

  • Copy file with advanced options

    Creates a copy of a file and applies any requested updates with patch semantics. Use when you need to duplicate a file with advanced options like label inclusion, visibility settings, or custom metadata.

  • Create Comment

    Tool to create a comment on a file in Google Drive. Returns a nested `data` object; extract `data.id` for the resulting comment identifier. Omit `anchor` and `quoted_file_content_*` for general file-level comments.

  • Create Shared Drive

    Tool to create a new shared drive. Use when you need to programmatically create a new shared drive for collaboration or storage.

  • Create File or Folder

    Creates a new file or folder in Google Drive. Supports both metadata-only creation (for folders and empty documents) and file upload with content. When file_to_upload is provided, uploads the actual file bytes; otherwise creates an empty...

All 76 Google Drive actions →

What your agent does in Salesforce

  • Add contact to campaign

    Adds a contact to a campaign by creating a CampaignMember record to track campaign engagement. Fails if the contact is already a member of the campaign; pre-check membership via SOQL before calling.

  • Add lead to campaign

    Adds a lead to a campaign by creating a CampaignMember record, allowing you to track campaign engagement. Both `campaign_id` and `lead_id` must be valid Salesforce IDs of active, existing records — names or emails cannot be substituted,...

  • Add product to opportunity

    Adds a product (line item) to an opportunity. The product must exist in a pricebook entry that's associated with the opportunity's pricebook.

  • Apply lead assignment rules

    Applies configured lead assignment rules to a specific lead, automatically routing it to the appropriate owner based on your organization's rules. Allow a brief propagation delay before querying updated ownership or field values after ru...

  • Associate contact to account

    Associates a contact with an account by updating the contact's AccountId field. Overwrites any existing AccountId on the contact. For broader contact field updates alongside the account association, use SALESFORCE_UPDATE_CONTACT instead.

  • Clone opportunity with products

    Clones an opportunity and optionally its products (line items). Creates a new opportunity with the same field values and products as the original.

All 179 Salesforce actions →

How it works

Tell the agent what you want to happen between Google Drive and Salesforce, for example to watch one and act in the other, or to keep the two in step. It reads what it needs from Google Drive, works out what to do, and runs the matching action in Salesforce without you mapping a single field.

You can have it run once, on a schedule, or whenever something changes. Ask it for a status any time and it reads the latest from both apps back to you in the same chat.

Common questions about Google Drive and Salesforce

How do I connect Google Drive and Salesforce to Operator?
You authorize Google Drive and Salesforce once each from your Operator dashboard. Operator holds both connections and refreshes the access tokens for you, so your agent keeps working across them without you signing in again.
What can my agent do across Google Drive and Salesforce?
You describe the outcome in plain language and your agent works between the two, reading from one and acting in the other. It picks the right Google Drive and Salesforce actions on its own, so you do not map fields or pick triggers.
Can my agent keep Google Drive and Salesforce in sync?
Yes. It can watch Google Drive and act in Salesforce, or keep both in step, reading from one and running the matching update in the other. This runs on demand when you ask or on a schedule you set.
Do I need to build a workflow or write code?
No. There is no workflow to build, no fields to map, and no API keys to paste. Operator manages both connections, and you give the agent instructions in plain language.

Google Drive and Salesforce integrations

Put your agent on Google Drive and Salesforce

Sign in, connect both apps, and hand your agent the work. The same setup reaches every app in the catalog. Your first week is free.

Try for free