connector_get
Retrieve Zabbix event connectors to review endpoints, data formats, authentication, and event filtering for SIEM integrations, custom pipelines, and third-party alerting.
Instructions
Retrieve event connectors. Connectors stream Zabbix events to external systems in real time, enabling SIEM integration, custom event pipelines, and third-party alerting. Each connector defines a URL endpoint, data format, authentication, and filtering rules for which events to forward.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of results to return. | |
| filter | No | Return only results whose properties exactly match the given values (a single value or a list of values per key). Example: {"status": 0} or {"status": [0, 1]}. Keys: attempt_interval (7.0+), authtype, connectorid, data_type, http_proxy, item_value_type (7.0+), max_attempts, max_records, max_senders, name, password, protocol, ssl_cert_file, ssl_key_file, ssl_key_password, status, tags_evaltype, timeout, token, url, username, verify_host, verify_peer. Text properties cannot be filtered; use 'search' for them. | |
| output | No | Properties of the connector object to return. Pass 'extend' for all, 'count' for the number of matches only, or a comma-separated list of property names. Default when omitted: connectorid, name, status. Properties: attempt_interval (7.0+), authtype, connectorid, data_type, description, http_proxy, item_value_type (7.0+), max_attempts, max_records, max_senders, name, password, protocol, ssl_cert_file, ssl_key_file, ssl_key_password, status, tags_evaltype, timeout, token, url, username, verify_host, verify_peer. | |
| search | No | Return results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: attempt_interval (7.0+), description, http_proxy, name, password, ssl_cert_file, ssl_key_file, ssl_key_password, timeout, token, url, username. | |
| server | No | Target Zabbix server. Available: default. Defaults to 'default' if omitted. | |
| raw_json | No | Strips the security disclaimer preamble from the response so it is pure JSON. Default: false. Requires the bearer token to have 'allow_raw_json' explicitly enabled by an operator in the admin portal - tokens without that policy receive a PolicyError instead. WARNING: setting true bypasses the prompt-injection mitigation marker that wraps untrusted Zabbix data (host names, item descriptions, problem text). LLM clients (Claude, GPT, Cursor, ...) should leave this false; only programmatic non-LLM consumers (Python scripts, n8n workflows that json.loads the result) should set true. | |
| sortfield | No | Sort by one or more of: connectorid, name, data_type, status (comma-separated for several; pair with 'sortorder'). No other property is sortable. | |
| sortorder | No | Sort order: 'ASC' (ascending) or 'DESC' (descending). | |
| countOutput | No | Return the count of matching results instead of the actual data. | |
| searchByAny | No | If true, return results matching ANY search field (OR). Default is ALL fields (AND). | |
| connectorids | No | Return only connectors with the given IDs. | |
| extra_params | No | Other native connector.get parameters, merged into the request as-is. Sub-object selects (value 'extend', 'count' or a list of property names): selectTags. Any other key is refused here, because Zabbix would silently ignore it. For a parameter you are sure exists on your release but is not listed, use zabbix_raw_api_call. | |
| searchWildcardsEnabled | No | If true, enable * and ? wildcards in search patterns. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |