> ## Documentation Index
> Fetch the complete documentation index at: https://docs.keephq.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# SIGNL4 Provider

> SIGNL4 offers critical alerting, incident response and service dispatching for operating critical infrastructure. It alerts you persistently via app push, SMS text and voice calls including tracking, escalation, collaboration and duty planning. Find out more at [signl4.com](https://www.signl4.com/)

## 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:

```yaml theme={null}
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:

* [signl4-alerting-workflow.yaml](https://github.com/keephq/keep/blob/main/examples/workflows/signl4-alerting-workflow.yaml)

## 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.

## Useful Links

* SIGNL4: [https://signl4.com/](https://signl4.com/)
* SIGNL4 knowledge base: [https://support.signl4.com/](https://support.signl4.com/)
* SIGNL4 getting-started videos: [https://www.youtube.com/watch?v=bwYSYOjMJZ8\&list=PL9FRxukdQyk9QRZPOEH3jhRX9WQCovCc6](https://www.youtube.com/watch?v=bwYSYOjMJZ8\&list=PL9FRxukdQyk9QRZPOEH3jhRX9WQCovCc6)
* SIGNL4 videos: [https://vimeo.com/showcase/signl4](https://vimeo.com/showcase/signl4)