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 Salesforce and Gmail See reverse direction

Trigger app

Salesforce as the trigger

Workflows fire when something happens in Salesforce.

Salesforce has no triggers yet. Use the catalog's universal Webhook trigger as the upstream.

Action app

Gmail as the action

Workflows do something in Gmail, instantly.

See all 27 actions →

Both directions

Pick the way that fits your stack.

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

Salesforce → Gmail

When something happens in Salesforce, do it in Gmail.

0 Salesforce triggers wired to 27 Gmail actions.

Gmail → Salesforce

Or fire it the other way around.

1 Gmail triggers wired to 13 Salesforce actions downstream.

New Email

See Gmail → Salesforce →

How it works

Connect Salesforce and Gmail in five steps.

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

1
Connect
Authorize Salesforce and Gmail
Open Tiny Command, authorize Salesforce and Gmail once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Salesforce trigger
Drop the Salesforce → New event trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/salesforce.event
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 Gmail action
Drop the Gmail → Add Labels to Message action below it. Map fields from the Salesforce payload into the Gmail inputs.
google-gmail.add-labels
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 Salesforce + Gmail.

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.