Per-pair page

Gmail + Salesforce: every email logged as Activity.

Log Gmail messages as Salesforce Tasks/Events on Lead/Contact records, with sender lookup and AI categorization. Reps stop pasting emails into SFDC manually.

Connect Gmail and Salesforce See reverse direction

Trigger app

Gmail as the trigger

Workflows fire when something happens in Gmail.

New EmailWebhook

Action app

Salesforce as the action

Workflows do something in Salesforce, instantly.

See all 13 actions →

Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

Gmail → Salesforce

When something happens in Gmail, do it in Salesforce.

1 Gmail triggers wired to 13 Salesforce actions. Most-used pairing: New Email → Convert Lead.

New Email

Salesforce → Gmail

Or fire it the other way around.

0 Salesforce triggers wired to 27 Gmail actions downstream.

Use any trigger in the catalog as the upstream.

See Salesforce → Gmail →

How it works

Connect Gmail and Salesforce in five steps.

No code, no glue, no half-day setup. Each step is one click.

1
Connect
Authorize Gmail and Salesforce
Open Tiny Command, authorize Gmail and Salesforce once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Gmail trigger
Drop the Gmail → New Email trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/google-gmail.trigger-email-received
3
Transform
Add a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
4
Action
Add the Salesforce action
Drop the Salesforce → Convert Lead action below it. Map fields from the Gmail payload into the Salesforce inputs.
salesforce.convert-lead
5
Publish
Publish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Gmail + Salesforce.

Doesn't Salesforce have Gmail integration already?

Salesforce has Salesforce Inbox / Einstein Activity Capture. The Tiny Command pair adds value when you need custom routing (e.g., logging from a no-reply support address) or AI pre-classification before logging.

How do I log an inbound Gmail as a Salesforce Activity?

Gmail Email Received → Salesforce Find Lead/Contact by sender email → Salesforce Create Task with subject = email subject, description = body, related to the matched record.

Can I create Salesforce Leads from Gmail senders?

Yes. For unmatched external senders, Salesforce Create Lead with email, name (AI-extracted from signature), source = "Gmail-inbound". Tag with category for downstream segmentation.

How do I AI-categorize Gmail before logging to Salesforce?

Insert Claude/OpenAI step. Classify as outbound-followup, inbound-inquiry, contract-discussion, customer-question. Set Salesforce Task subject prefix accordingly. Easier to filter in SFDC.

Can I link Gmail attachments to Salesforce records?

Yes. Loop Gmail attachments. Upload each via Salesforce Upload File and attach to the related record. Files visible in Salesforce alongside the activity.

How do I avoid logging internal emails to Salesforce?

Filter Gmail triggers where the sender/recipient domain is external (not your company's). Internal team emails skip Salesforce. Reduces noise in activity timeline dramatically.