Per-pair page

Connect Azure DevOps to Notion in two minutes.

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

Connect Azure DevOps and Notion See reverse direction

Trigger app

Azure DevOps as the trigger

Workflows fire when something happens in Azure DevOps.

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

Action app

Notion as the action

Workflows do something in Notion, instantly.

See all 12 actions →

Both directions

Pick the way that fits your stack.

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

Azure DevOps → Notion

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

0 Azure DevOps triggers wired to 12 Notion actions.

Notion → Azure DevOps

Or fire it the other way around.

3 Notion triggers wired to 5 Azure DevOps actions downstream.

See Notion → Azure DevOps →

How it works

Connect Azure DevOps and Notion in five steps.

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

1
Connect
Authorize Azure DevOps and Notion
Open Tiny Command, authorize Azure DevOps and Notion once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Azure DevOps trigger
Drop the Azure DevOps → New event trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/azure-devops.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 Notion action
Drop the Notion → Append Content action below it. Map fields from the Azure DevOps payload into the Notion inputs.
notion.append-blocks
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 Azure DevOps + Notion.

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

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

Is the Azure DevOps ↔ Notion integration real-time?

Yes. Both Azure DevOps and Notion 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 Azure DevOps and Notion?

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 Notion.

What Azure DevOps events can trigger a Notion workflow?

Use Tiny Command's universal Webhook trigger to receive Azure DevOps events, then run any of the 12 Notion actions downstream.

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

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

What if I want Notion → Azure DevOps instead?

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