Opsgenie
Opsgenie alert and on-call orchestration
Opsgenie (Atlassian's on-call alerting product) is the on-call rotation + alert routing tool that pages the right engineer when production breaks — direct competitor to PagerDuty, deeply integrated with Jira and the wider Atlassian stack. Tiny Command exposes four actions, no triggers (Opsgenie emits incident-state-change events via webhooks configured per-team in admin Settings → Integrations → Webhook; point at a Tiny Command webhook trigger): Create Alert (open an alert with message, alias for dedupe, responder routing, priority), List Alerts (filterable by status/priority/responder/team), Add Note to Alert (append context, visible to responders in the alert timeline), Close Alert (resolve the alert; stops paging). The connection uses an Opsgenie API key (account-wide from Settings → API key management) with the appropriate role permissions. The alias field on Create Alert is the dedupe key — repeated Create Alert with the same alias updates the existing alert rather than creating new ones.
Do anything Opsgenie can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Opsgenie Add Note | Appends a note to an alert's timeline. For "AI-summarised investigation findings → log on the alert for the responder" workflows. |
| Close Opsgenie Alert | Resolves an alert. The standard end-state when monitoring signals indicate the issue is fixed — repeated Create Alert with same alias re-opens. |
| Create Opsgenie Alert | Opens an alert with message, alias for dedupe, responder routing, priority. The standard hook for "monitoring source detected anomaly → page the on-call engineer" workflows. |
| List Opsgenie Alerts | Paginated alerts with filters by status, priority, responder. For "current open alerts" dashboards and weekly post-mortem rollups. |
Pre-built Opsgenie workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Opsgenie once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Opsgenie field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Opsgenie integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Opsgenie to Tiny Command?
What Opsgenie triggers does Tiny Command support?
What Opsgenie actions can I run from a workflow?
Is the Opsgenie integration real-time?
Do I need to write code to use Opsgenie with Tiny Command?
How much does the Opsgenie integration cost?
More other apps people connect.
Same category as Opsgenie, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Opsgenie.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
