Incident.io

This connector captures data from Incident.io into Estuary collections.

It is available for use in the Estuary web application. For local development or open-source workflows, ghcr.io/estuary/source-incident-io:dev provides the latest version of the connector as a Docker image. You can also follow the link in your browser to see past image versions.

Supported data resources

The following data resources are supported through the Incident.io API:

• catalog entries
• catalog resources
• catalog types
• custom fields
• incident attachments
• incident roles
• incident statuses
• incident timestamps
• incident types
• incidents
• severities
• users

By default, each resource is mapped to an Estuary collection through a separate binding.

Prerequisites

• An Incident.io account.
• An Incident.io API key

Configuration

You configure connectors either in the Estuary web app, or by directly editing the catalog specification files. See connectors to learn more about using connectors. The values and specification sample below provide configuration details specific to the Incident.io source connector.

Properties

Endpoint

Property	Title	Description	Type	Required/Default
/credentials/credentials_title	Authentication Method	Set to Private App Credentials.	string	Required
/credentials/access_token	API Key	Your Incident.io API key.	string	Required

Bindings

Property	Title	Description	Type	Required/Default
/name	Data resource	Resource in Incident.io from which collections are captured.	string	Required
/interval	Interval	Interval between data syncs	string	PT5M

Sample

captures:
  ${PREFIX}/${CAPTURE_NAME}:
    endpoint:
      connector:
        image: ghcr.io/estuary/source-incident-io:dev
        config:
          credentials:
            access_token: <secret>
            credentials_title: Private App Credentials
    bindings:
      - resource:
          name: incidents
        target: ${PREFIX}/incidents