Opsgenie

Opsgenie + Konnectify

Opsgenie Integration with Konnectify

Automate alert and incident management workflows by connecting Opsgenie with your support, DevOps, and business systems through Konnectify.

Alerts Incidents Users Teams Schedules & On-Calls Heartbeats 5 Triggers 51 Actions

ON THIS PAGE

→ What is Opsgenie? → API & authentication → How to connect → Triggers (5) → Actions (51) → Popular automations → FAQ

What is Opsgenie?

Opsgenie is Atlassian’s alerting and incident response platform for routing critical alerts, coordinating responders, managing on-call schedules, and tracking incident activity. It helps DevOps, SRE, IT, and support teams respond quickly to service-impacting events.

With Konnectify, you can connect Opsgenie to the rest of your toolchain to automatically create incidents, update responders, sync users and teams, monitor heartbeats, and keep downstream systems informed when alerts or incidents change.

New to Opsgenie?

Explore Opsgenie for alerting, incident management, and on-call scheduling.

Visit Opsgenie →

New to Konnectify?

Build no-code automations across Opsgenie and your business apps.

What you can automate

• Detect new and updated alerts

• Create, resolve, close, or reopen incidents

• Add notes, responders, tags, and incident details

• Manage Opsgenie users and team records

• Query on-call schedules and timelines

• Create, update, enable, or disable heartbeats

API & Authentication

API Key authentication

The Opsgenie connector uses API Key authentication. In Konnectify, enter your Opsgenie GenieKey API key and select the correct region: US / Global or EU (Europe). Konnectify uses these credentials to securely call the Opsgenie API on behalf of your workflow.

Your API key should have permissions for the Opsgenie resources you want to automate, such as incidents, alerts, users, teams, schedules, and heartbeats.

API capabilities

Poll alerts, incidents, and users
Create and manage incidents
Manage users, teams, and schedules
Retrieve on-call participants and timelines
Create and administer heartbeats

Required connection fields

API Key: your Opsgenie GenieKey API key
Region: US / Global or EU (Europe)

Plan, permission, and rate limit note

Opsgenie API access, available endpoints, and request limits may vary by Atlassian/Opsgenie plan, region, and API key permissions. If a workflow receives permission or rate limit errors, review your Opsgenie API key settings and retry after the rate limit window resets.

Official API documentation: Opsgenie API Overview

How to Connect Opsgenie to Konnectify

Prerequisites

An active Opsgenie account with API access
A valid Opsgenie GenieKey API key with the required permissions
Your Opsgenie region: US / Global or EU (Europe)
A Konnectify account with permission to create or edit workflows

Add Opsgenie to a Workflow

Open Konnectify and create a new workflow, or edit an existing workflow.
Search for Opsgenie in the app selector.
Select an Opsgenie trigger or action based on your automation goal.

Authorize via API Key authentication

Choose Add new connection.
Paste your Opsgenie GenieKey API key into the API Key field.
Select your Opsgenie region: US / Global or EU (Europe).
Save the connection.

Configure the Trigger or Action

Map required fields from previous steps in your workflow.
For incident actions, provide the incident identifier and any required message, note, responder, tag, or priority values.
For schedule and heartbeat actions, confirm that names or IDs match records in the selected Opsgenie region.

Tip: Use IDs returned by previous Opsgenie steps wherever possible to avoid ambiguity when names are duplicated across teams, schedules, or incidents.

Test the Workflow

Run a test to verify that Konnectify can access Opsgenie.
Confirm that sample records and action responses contain the fields you need.
Review any Opsgenie request status responses for asynchronous incident operations.

Activate the Workflow

Turn on the workflow when the test completes successfully.
Monitor initial runs to ensure alerts, incidents, users, teams, schedules, and heartbeats are processed as expected.

Triggers 5

Opsgenie includes 5 polling triggers. Konnectify periodically checks Opsgenie for new or updated records and starts your workflow when matching data is found.

Alerts 2 triggers

New Alert

Polls for new alerts sorted by creation time.

Updated Alert

Polls for updated alerts sorted by update time.

Incidents 2 triggers

New Incident

Polls for new incidents sorted by creation time.

Updated Incident

Polls for updated incidents sorted by update time.

Users 1 trigger

New User

Polls for new users sorted by creation time.

Actions 51

Use Opsgenie actions to create, retrieve, update, and manage incident response resources directly from Konnectify workflows.

Incidents 21 actions

Get Request Status

Track the async processing status of a prior incident write request.

Create Incident

Create a new incident.

Delete Incident

Permanently delete an incident.

Get Incident

Retrieve a specific incident's details.

List Incidents

List/search incidents with filtering, sorting, pagination.

Get Associated Alerts

Retrieve alert IDs associated with the incident.

Get Responder Alerts

Retrieve alert IDs tied to the incident's responders.

Close Incident

Close the incident once response is complete.

Resolve Incident

Mark the incident resolved while preserving history.

Reopen Incident

Reopen a resolved/closed incident.

Add Note

Add an investigation note to an incident.

Add Responder

Add a team/user responder to an incident.

Add Tags

Add tags to an incident.

Remove Tags

Remove tags from an incident.

Add Details

Add custom key/value properties to an incident.

Remove Details

Remove custom key/value properties from an incident.

Update Priority

Change incident priority (P1–P5).

Update Message

Update the incident's title/message.

Update Description

Update the incident's description.

List Incident Logs

Retrieve the incident's audit log/activity history.

List Incident Notes

Retrieve all notes added to the incident.

Users 9 actions

Create User

Create a new Opsgenie user.

Get User

Retrieve a specific user's details.

Update User

Partially update a user.

Delete User

Delete a user from Opsgenie.

List Users

List/search users with filtering, sorting, pagination.

List User Escalations

List escalation policies a user participates in.

List User Teams

List teams the user belongs to.

List Forwarding Rules

List a user's alert forwarding rules.

List User Schedules

List schedules the user participates in.

Teams 6 actions

Create Team

Create a new team.

Get Team

Retrieve a specific team's details.

Update Team

Partially update a team (name, description, members).

Delete Team

Delete a team.

List Teams

Retrieve all teams (no pagination).

List Team Logs

Retrieve a team's audit log.

Schedules & On-Calls 8 actions

Get On-Calls

Retrieve current on-call participants for a schedule.

Get Next On-Calls

Retrieve upcoming on-call participants for a schedule.

Create Schedule

Create a new on-call schedule with rotations.

Get Schedule

Retrieve a specific schedule's details.

Update Schedule

Partially update a schedule.

Delete Schedule

Delete a schedule.

List Schedules

List all schedules.

Get Schedule Timeline

Retrieve the computed on-call timeline for a schedule.

Heartbeats 7 actions

Create Heartbeat

Create (add) a new heartbeat.

Get Heartbeat

Retrieve a specific heartbeat's configuration/status.

List Heartbeats

List all heartbeats.

Update Heartbeat

Partially update a heartbeat's configuration.

Delete Heartbeat

Delete a heartbeat.

Enable Heartbeat

Enable a disabled heartbeat.

Disable Heartbeat

Disable a heartbeat without deleting it.

Popular Automations

Here are common Opsgenie workflows you can build with Konnectify.

Auto-enrich new incidents

When a new incident is detected, add investigation context, routing tags, and an initial responder.

New Incident → Add Details → Add Responder

Escalate updated high-priority incidents

React to incident updates by changing priority, adding notes, and tracking responders.

Updated Incident → Update Priority → Add Note

Keep user and team data current

When a new Opsgenie user appears, retrieve their team and schedule participation for downstream provisioning or reporting.

New User → List User Teams → List User Schedules

Route alert activity to on-call context

Use new alert activity to look up current and upcoming on-call participants before notifying other systems.

New Alert → Get On-Calls → Get Next On-Calls

FAQ

How does Opsgenie authentication work in Konnectify?

Opsgenie uses API Key authentication. Add your GenieKey API key in Konnectify and choose the matching Opsgenie region, either US / Global or EU.

Which Opsgenie plans are supported?

Any Opsgenie plan that allows API access and provides the required endpoint permissions can be connected. Some capabilities may depend on your Atlassian/Opsgenie subscription, role, API key permissions, and region.

How do Opsgenie triggers work?

The available Opsgenie triggers are polling triggers. Konnectify checks Opsgenie on a schedule for new or updated alerts, incidents, and users, then starts the workflow when matching records are found.

How can I prevent duplicate incidents or repeated updates?

This connector does not include a dedicated upsert action. To avoid duplicates, design workflows around stable Opsgenie IDs or aliases, search existing incidents with List Incidents, and add conditional logic before creating a new incident or applying updates.

How are Opsgenie rate limits handled?

Opsgenie may throttle requests when API rate limits are exceeded. If a workflow receives a rate limit response, reduce workflow frequency or volume where possible and retry after the limit window resets.

Can I connect multiple Opsgenie accounts or regions?

Yes. Create separate Opsgenie connections in Konnectify for each account or region. Name each connection clearly, such as “Opsgenie US Production” or “Opsgenie EU Staging,” so workflow builders select the correct environment.

Why do some incident write actions return a request status instead of final incident data?

Some Opsgenie incident operations are processed asynchronously. Use the Get Request Status action to track the processing result of a prior incident write request before continuing with dependent steps.

Ready to automate your Opsgenie workflows?

Connect Opsgenie to Konnectify and automate alert, incident, on-call, and heartbeat operations across your stack.

Get started free →