AsyncAPI channel · New Relic · New Relic Streaming and Event-Driven Surfaces

workflow/webhook

Webhook destination that receives Alerts Workflow notifications when an issue changes state. The HTTP request is a POST with a JSON body whose shape is fully controlled by the workflow's message template. The template uses Handlebars expressions over the documented set of notification variables. The schema below reflects the standard variables documented at docs.newrelic.com.

Open source AsyncAPI → All New Relic channels New Relic provider profile
Provider: New Relic AsyncAPI: v2.6.0 Spec: New Relic Streaming and Event-Driven Surfaces Operations: 1 Messages: 4

Channel address

workflow/webhook

Operations

publish
receiveWorkflowWebhook
Receive an Alerts Workflow webhook notification

Messages

issueActivated
Sent when a New Relic Alerts issue transitions to the ACTIVATED state.
Content-Type: application/json
issueAcknowledged
Sent when a New Relic Alerts issue is acknowledged by a user.
Content-Type: application/json
issueClosed
Sent when a New Relic Alerts issue transitions to the CLOSED state.
Content-Type: application/json
issueUpdated
Sent when a New Relic Alerts issue is updated (for example when a new correlated incident is added, priority changes, or muting state changes).
Content-Type: application/json

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.