​
Authentication

This provider requires authentication.
  • signl4_integration_secret: SIGNL4 integration or team secret (required: True, sensitive: True)
Certain scopes may be required to perform specific actions or queries via the provider. Below is a summary of relevant scopes and their use cases:
  • signl4:create: Create SIGNL4 alerts (mandatory)

​
In workflows

This provider can be used in workflows. As “action” to make changes or update data, example: 
actions:
    - name: Query signl4
      provider: signl4
      config: "{{ provider.my_provider_name }}"
      with:
        title: {value}  # Alert title.
        message: {value}  # Alert message.
        user: {value}  # User name.
        s4_external_id: {value}  # External ID.
        s4_status: {value}  # Alert status.
        s4_service: {value}  # Service name.
        s4_location: {value}  # Location.
        s4_alerting_scenario: {value}  # Alerting scenario.
        s4_filtering: {value}  # Filtering.
        # Additional alert data.
Check the following workflow example:

​
Connecting with the Provider

To use the Signl4Provider, you’ll need to provide your signl4_integration_secret. You can find your integration or team secret in the SIGNL4 web portal under Teams or Integrations -> Distribution Rules. The signl4_integration_secret is used to post events to SIGNL4 using the webhook API.

​
Notes

The provider uses either the events API or the incidents API to create an alert or an incident. The choice of API to use is determined by the presence of either a routing_key or an api_key.