Create Connector
elastic_security.create_connector
ActionBusiness appsconnection required
Calls the Elastic Security API with the connection's credentials.
Create a Kibana connector so cases and rules can reach another system.
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
5 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
name Display name for the connector. | string | Yes | — | — | — |
connector_type_id Connector type such as .jira, .servicenow, .slack or .cases-webhook. | string | Yes | — | — | .jira |
connector_config Non-secret settings for this connector type, such as its API URL. | object | No | — | — | — |
connector_secrets Credentials for the target system. Kibana stores them and never returns them, so they are absent from this node's output. | object | No | — | — | — |
connector_id Identifier to give the connector, 1 to 36 characters. Left blank Kibana generates one. | string | No | — | ≤ 36 characters | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"connector_type_id": ".jira"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
id Identifier of the Kibana connector. | string | — |
name Display name of the connector. | string | — |
connector_type_id Connector type, such as .jira or .servicenow. | string | — |
config Non-secret configuration of the connector. | object | — |
is_preconfigured True when the connector comes from kibana.yml. | boolean | — |
is_deprecated True when the connector is deprecated. | boolean | — |
is_missing_secrets True when the connector has no usable secrets. | boolean | — |
is_system_action True when the connector backs a system action. | boolean | — |
{
"config": {},
"connector_type_id": "",
"id": "",
"is_deprecated": false,
"is_missing_secrets": false,
"is_preconfigured": false,
"is_system_action": false,
"name": ""
}See Create 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.