Run Connector

elastic_security.run_connector
ActionBusiness appsconnection required

Calls the Elastic Security API with the connection's credentials.

Run a Kibana connector with the parameters its type expects, for example to post a Slack message or open a ServiceNow incident.

Connection

Required
Yes — the node will not save without one
Auth type
API key
Providers
Elastic Security
Secret shape
the Kibana API key ("ApiKey <encoded>" or the bare encoded value), or {"api_key": "…"}
Config it needs
kibana_url, space_id, owner
Resolved by
config.connection_id, else node.connection_id

Configuration

2 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
connector_id
Identifier of the connector to run.
stringYes———
params
Parameters for this connector type, such as {"message": "..."}.
objectNo———

Output

One shape.

result

FieldTypeExample
connector_id
The connector that was run.
string—
status
Elastic's outcome for the run: ok or error.
string—
ok
True only when status is ok; branch on this.
boolean—
data
Whatever the connector type returned, when it succeeded.
any—
message
Elastic's error message when status is error.
string—
service_message
The third party's own error detail.
string—
retry
Whether Elastic considers the failure retryable.
any—
{
  "connector_id": "",
  "data": null,
  "message": "",
  "ok": false,
  "retry": null,
  "service_message": "",
  "status": ""
}

Notes

  • Kibana answers HTTP 200 even when the third-party call failed, reporting status "error" with a service_message. The node surfaces that outcome instead of raising, so a workflow can branch on `ok` and read the reason.

See Run Connector run in a workflow.

In a technical demo we add the Elastic Security connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.