Skip to main content

incident.io Destination

The incident.io destination connector enables you to send data from Nexla into your incident.io organization—such as creating incidents, posting alert events to trigger automated incident workflows, or updating incident records from external systems. Follow the instructions below to create a new data flow that delivers data to an incident.io destination in Nexla.
incident_io_api.png

incident.io

Create a New Data Flow​

  1. To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Then, select the desired flow type from the list, and click the Create button.

  2. Select the incident.io connector tile from the list of available connectors on the destination configuration screen. Then, select the credential that will be used to connect to incident.io, and click Next; or, create a new incident.io credential for use in this flow.

  3. Configure the destination by specifying the API endpoint, HTTP method, data format, and any additional settings as described in the sections below.

API Method​

  1. Select the API method that will be used for calls to the incident.io API from the Method pulldown menu. The most common methods for writing data to incident.io are:

    • POST: For creating new incidents, posting alert events, or triggering actions in incident.io.

    • PUT: For replacing an existing incident record with updated data.

    • PATCH: For partially updating an existing incident or resource (modifying specific fields without replacing the entire record).

Data Format​

  1. Select the format in which data will be sent to the incident.io API from the Data Format pulldown menu. incident.io accepts data in JSON format for all API write operations. Select JSON to ensure that Nexla formats outbound records correctly.

The incident.io API requires that the Content-Type: application/json header be included with all write requests. Nexla sets this header automatically when JSON is selected as the data format.

API Endpoint URL​

  1. Enter the URL of the incident.io API endpoint to which this destination will send data in the Set API URL field. This should be the complete endpoint URL including the protocol. Common incident.io destination endpoints include:

    • https://api.incident.io/v2/incidents — create a new incident (POST)

    • https://api.incident.io/v2/alert_events/http/{'{alert_source_config_id}'} — post an alert event to trigger automated incident creation (POST); replace {'{alert_source_config_id}'} with the ID of the alert source you configured in your incident.io dashboard

    • https://api.incident.io/v2/incidents/{'{id}'} — update an existing incident by ID (PATCH or PUT); replace {'{id}'} with the incident's unique identifier

For the alert events endpoint, you must first configure an HTTP alert source in your incident.io dashboard (Settings > Alert sources) before you can post alert events to it. Each alert source has a unique alert_source_config_id that is used in the endpoint URL. The alert events endpoint has a rate limit of 120 events per minute per alert source. For additional details, refer to the incident.io Alert Events API documentation.

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this destination, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2).

    You do not need to include the Authorization header or Content-Type header here, as both are handled automatically by Nexla from your saved credential and the selected data format. Only include headers that are required beyond these defaults.

Exclude Attributes​

Optional
  • If there are fields in the Nexla data set that should not be sent to incident.io, enter the field names as a comma-separated list in the Exclude Attributes field. This is useful for filtering out internal Nexla metadata or fields that are not accepted by the incident.io API endpoint.

Record Batching​

Optional

  • Configure the Record Batching settings to control how Nexla groups records into individual API calls when sending data to incident.io. By default, Nexla sends one record per API call.

    For most incident.io write endpoints (such as creating incidents or posting alert events), each API call creates a single record in incident.io. Record batching is typically not applicable for these endpoints, as each incident or alert event should be sent as a separate API request. However, if the target endpoint supports batch ingestion, you can adjust batching settings accordingly.

Response Webhook​

Optional

  • If you want Nexla to capture and process the response from incident.io after each API call, configure the Response Webhook settings. This allows Nexla to log API responses, track success or failure of each record sent to incident.io, and optionally route response data to other downstream systems.

    Enabling response capture is recommended when posting alert events to incident.io, as the API response includes confirmation of the event receipt and any validation errors. Tracking responses can help you identify and troubleshoot issues with records that fail to be accepted by incident.io.

Save & Activate the Destination​

  1. Once all of the relevant steps in the above sections have been completed, click the Create button in the upper right corner of the screen to save and activate the new incident.io destination. Nexla will now begin delivering data to the configured incident.io endpoint according to the flow schedule.