Service Tags

An integration might require the configuration of multiple connectors to support multiple services. For these integrations, subflows installed with the integration are designed to work with a specific service. Integration service tags are used to facilitate the configuration of connectors and allow auto-assigning subflow connectors when importing a runbook containing the integration.

Configuring connectors with service tags

Integrations in the Integrations Library page require the configuration of connectors. For some of these integrations, connectors have an additional setting to specify Service Tags. Setting Service Tags is optional, but recommended as it makes assigning a connector a more seamless operation, especially when importing runbooks containing this integration.

Service tags and assigning connectors in a runbook

When assigning the connector in an integration subflow in a runbook, only matching enabled connectors are displayed to the user in the input selection. A connector can be enabled/disabled in the Integrations Library page. A connector is considered a match when:

  • It contains the required Service Tag for the subflow. It might have additional service tags that are not required for the subflow.

  • It has not been assigned any tag, acting like a wildcard.

Service tags and importing runbooks using the User Interface

When a runbook containing integrations is imported using the Import button in one of the Runbook Pages, Service Tags are used to auto-select matching enabled connectors in the Runbook Import dialog. A connector is considered a match as described above.

Service tags and importing runbooks using the Import API

When a runbook containing integrations is imported using the import API, Service Tags are used to automatically auto-assign connectors in the imported runbook. A connector will only be auto-assigned when:

  • There is a single matching enabled integration connector.

  • There is no matching connector that is enabled, but there is a single matching connector that is disabled. In this case, the disabled matching connector will be auto-assigned.

In all other cases, the connector will not be auto-assigned. For example, if many connectors are matching for a subflow, no connector will be set in the imported runbook. The user will have to manually assign the connector in the imported runbook.

Configuring service tags on integration subflows

An integration subflow can be duplicated and edited in the Subflow Editor. If the subflow supports service tags, its Subflow Input node will show an Integration section where Connector Service Tags can be configured as shown below.

If a tag is configured on the subflow, then only matching enabled integration connectors will be displayed to the user when using the subflow in a runbook. As described above, an integration connector without tags (wildcard connector) is also considered a match.

If no tag is configured on the subflow, then all integration connectors will be displayed to the user when using the subflow in a runbook, including integration connectors with tags.