Per-pair page

Connect Gmail to Azure DevOps in two minutes.

Real-time triggers from Gmail, ready-made actions in Azure DevOps. Filter, transform, and route without writing a line of code.

Connect Gmail and Azure DevOps See reverse direction

Trigger app

Gmail as the trigger

Workflows fire when something happens in Gmail.

New EmailWebhook

Action app

Azure DevOps as the action

Workflows do something in Azure DevOps, instantly.

Both directions

Pick the way that fits your stack.

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

Gmail → Azure DevOps

When something happens in Gmail, do it in Azure DevOps.

1 Gmail triggers wired to 5 Azure DevOps actions. Most-used pairing: New Email → Add Comment to Work Item.

New Email

Azure DevOps → Gmail

Or fire it the other way around.

0 Azure DevOps triggers wired to 27 Gmail actions downstream.

Use any trigger in the catalog as the upstream.

See Azure DevOps → Gmail →

How it works

Connect Gmail and Azure DevOps in five steps.

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

1
Connect
Authorize Gmail and Azure DevOps
Open Tiny Command, authorize Gmail and Azure DevOps 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 Azure DevOps action
Drop the Azure DevOps → Add Comment to Work Item action below it. Map fields from the Gmail payload into the Azure DevOps inputs.
azure-devops.add-comment
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 + Azure DevOps.

How long does it take to connect Gmail and Azure DevOps on Tiny Command?

Under two minutes. Authorize Gmail and Azure DevOps once each, drop the Gmail trigger and Azure DevOps action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.

Is the Gmail ↔ Azure DevOps integration real-time?

Yes. Both Gmail and Azure DevOps expose webhooks, so events from one fire workflows in the other within seconds rather than on a polling interval.

Can I filter or transform data between Gmail and Azure DevOps?

Yes. Add a Filter node to only pass through matching events, a Switch node to branch by value, or an AI / Code node to transform payloads before they hit Azure DevOps.

What Gmail events can trigger a Azure DevOps workflow?

Any of the 1 Gmail triggers, including "New Email". Each fires in real time when the matching event happens in Gmail.

Do I need a paid plan to use Gmail with Azure DevOps?

No. There's a free tier that covers most Gmail+Azure DevOps use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.

What if I want Azure DevOps → Gmail instead?

Build it the same way, in reverse. There's a dedicated /integrations/azure-devops/with/google-gmail page with the reverse-direction triggers and actions.