Per-pair page

Connect Opsgenie to Slack in two minutes.

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

Connect Opsgenie to Slack — start free See reverse direction

Trigger app

Opsgenie as the trigger

Workflows fire when something happens in Opsgenie.

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

Action app

Slack as the action

Workflows do something in Slack, instantly.

See all 45 actions →

Both directions

Pick the way that fits your stack.

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

Opsgenie → Slack

When something happens in Opsgenie, do it in Slack.

0 Opsgenie triggers wired to 45 Slack actions.

Slack → Opsgenie

Or fire it the other way around.

13 Slack triggers wired to 4 Opsgenie actions downstream.

See Slack → Opsgenie →

How it works

Connect Opsgenie and Slack in five steps.

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

1
Connect
Authorize Opsgenie and Slack
Open TinyCommand, authorize Opsgenie and Slack once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Opsgenie trigger
Drop the Opsgenie → New event trigger onto the canvas. TinyCommand auto-registers the webhook.
POST /v1/webhooks/opsgenie.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 Slack action
Drop the Slack → Add Reaction action below it. Map fields from the Opsgenie payload into the Slack inputs.
slack.add-reaction
5
Publish
Publish and forget
Hit Publish. TinyCommand runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Opsgenie + Slack.

How long does it take to connect Opsgenie and Slack on TinyCommand?

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

Is the Opsgenie ↔ Slack integration real-time?

Yes. Both Opsgenie and Slack 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 Opsgenie and Slack?

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

What Opsgenie events can trigger a Slack workflow?

Use TinyCommand's universal Webhook trigger to receive Opsgenie events, then run any of the 45 Slack actions downstream.

Do I need a paid plan to use Opsgenie with Slack?

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

What if I want Slack → Opsgenie instead?

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