- Integrations
- /
- Outreach
- /
- with Gmail
Connect Outreach to Gmail in two minutes.
Real-time triggers from Outreach, ready-made actions in Gmail. Filter, transform, and route without writing a line of code.
Workflows fire when something happens in Outreach.
- Outreach Prospect RepliedWebhook
- Outreach Sequence Step FinishedWebhook
Workflows do something in Gmail, instantly.
- Add Labels to MessageAPI
- Create DraftAPI
- Create LabelAPI
- Delete DraftAPI
- Delete LabelAPI
- Delete MessageAPI
Pick the way that fits your stack.
Pair pages are mirrored. Each direction gets its own dedicated page.
When something happens in Outreach, do it in Gmail.
2 Outreach triggers wired to 27 Gmail actions. Most-used pairing: Outreach Prospect Replied → Add Labels to Message.
Or fire it the other way around.
1 Gmail triggers wired to 5 Outreach actions downstream.
See Gmail → Outreach →Common Outreach → Gmail workflows.
Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.
Fires when a prospect responds to a sequenced email — the moment that pulls them out of automation. For "remove from competing sequences, notify the AE, log to CRM" hand-off workflows.
Fires when a prospect responds to a sequenced email — the moment that pulls them out of automation. For "remove from competing sequences, notify the AE, log to CRM" hand-off workflows.
Fires when a prospect responds to a sequenced email — the moment that pulls them out of automation. For "remove from competing sequences, notify the AE, log to CRM" hand-off workflows.
Fires when a prospect responds to a sequenced email — the moment that pulls them out of automation. For "remove from competing sequences, notify the AE, log to CRM" hand-off workflows.
Fires per-step as sequences progress. For granular activity-tracking workflows that need to log each touch separately.
Fires per-step as sequences progress. For granular activity-tracking workflows that need to log each touch separately.
Fires per-step as sequences progress. For granular activity-tracking workflows that need to log each touch separately.
Fires per-step as sequences progress. For granular activity-tracking workflows that need to log each touch separately.
Connect Outreach and Gmail in five steps.
No code, no glue, no half-day setup. Each step is one click.
- 1ConnectAuthorize Outreach and Gmail
Open Tiny Command, authorize Outreach and Gmail once each. Both connections are available to every workflow on your account.
- 2TriggerPick a Outreach trigger
Drop the Outreach → Outreach Prospect Replied trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/outreach.trigger-prospect-replied - 3TransformAdd a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
- 4ActionAdd the Gmail action
Drop the Gmail → Add Labels to Message action below it. Map fields from the Outreach payload into the Gmail inputs.
google-gmail.add-labels - 5PublishPublish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.
Questions about Outreach + Gmail.
How long does it take to connect Outreach and Gmail on Tiny Command?
Is the Outreach ↔ Gmail integration real-time?
Can I filter or transform data between Outreach and Gmail?
What Outreach events can trigger a Gmail workflow?
Do I need a paid plan to use Outreach with Gmail?
What if I want Gmail → Outreach instead?
Other apps that pair well with Outreach.
Wire Outreach to Gmail in 2 minutes.
Free tier available. No credit card. No onboarding call.