Torq connector and actionedit

The Torq connector uses a Torq webhook to trigger workflows with Kibana actions.

Create connectors in Kibanaedit

You can create connectors in Stack Management > Connectors or as needed when you’re creating a rule. For example:

configured Torq connector
Connector configurationedit

Torq connectors have the following configuration properties:

The name of the connector. The name is used to identify a connector in the Stack Management UI connector listing, and in the connector list when configuring an action.
Torq endpoint URL
Endpoint URL (webhook) of the Elastic Security integration you created in Torq.
Torq authentication header secret
Secret of the webhook authentication header.

Create preconfigured connectorsedit

If you are running Kibana on-prem, you can define connectors by adding xpack.actions.preconfigured settings to your kibana.yml file. For example:

    name: preconfigured-torq-connector-type
    actionTypeId: .torq
      token: mytorqtoken

Config defines information for the connector type.

An address that corresponds to Torq endpoint URL.

Secrets defines sensitive information for the connector type.

A string that corresponds to Torq authentication header secret.

Test connectorsedit

You can test connectors with the run connector API or as you’re creating or editing the connector in Kibana. For example:

Torq connector test

Torq actions have the following configuration properties.

JSON payload to send to Torq.