Close Opsgenie Alert: Opsgenie action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Alert ID or Alias identifier	string	Required	—
Identifier Type identifierType	options	Optional	—
Close note note	string	Optional	—

Sample request

{
  "identifier": "{{trigger.identifier}}",
  "identifierType": "{{trigger.identifierType}}",
  "note": "{{trigger.note}}"
}

Returns

{
  "result": "Request will be processed",
  "requestId": "req_abc"
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Close Opsgenie Alert.

What does the Close Opsgenie Alert action do in Opsgenie?

Resolves an alert. The standard end-state when monitoring signals indicate the issue is fixed — repeated Create Alert with same alias re-opens.

What inputs does Close Opsgenie Alert require?

Required: Alert ID or Alias. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Opsgenie returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Close Opsgenie Alert support batch operations?

Yes. Run Close Opsgenie Alert inside a Loop node to process arrays. Tiny Command handles Opsgenie's rate limits automatically so you don't have to throttle manually.

More actions