--- title: "Zabbix MCP server for AI agents - actionlake" description: "Give Claude 224 Zabbix actions through one MCP server: administration, data collection. Your agent never holds the credential. 100,000 calls a month free." canonical: https://actionlake.com/connectors/zabbix updated: 2026-10-23 --- Connectors · MSP & PSA # Zabbix MCP server for AI agents. actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Zabbix and the rest of your systems. It gives your agent 224 Zabbix actions (64 reads, 110 writes and 50 that wait for a confirmation) and holds the Zabbix credential itself, so the agent never does. It paces Zabbix's limits and records every call. [Connect Zabbix free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) 100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you. `claude mcp add --transport http actionlake https://connect.actionlake.com/mcp` the first call ``` do { action: "zabbix.user.get", intent: "check which Zabbix account is connected" } # Retrieve users · read · 1 upstream call ``` - 224 actions in one signed file - 64 read look, never change - 110 write create and update - 50 wait for a yes destructive, confirmed first Set up ## Connect Zabbix in three steps. 1. 01 ### Add actionlake to Claude. Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us. `https://connect.actionlake.com/mcp` 2. 02 ### Connect Zabbix. Bearer token. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key. - `api_token` Zabbix API token: in the Zabbix frontend open Users > API tokens (or User settings > API tokens for your own user),… - `host` Where your Zabbix lives: your host ``` account { op: "connections.requirements", service: "zabbix" } # free: exactly what to paste, and what is found for you ``` 3. 03 ### Make the first call. Check before a write. Ask in plain words; Claude picks the action. Before anything changes, `check` validates the call and prices it, for free. ``` do { action: "zabbix.user.get" } # retrieve users · read · 1 upstream call check { action: "zabbix.user.create", input: { … } } # free: inputs, permissions, cost and confirmations, nothing sent ``` Zabbix at a glance **Sign-in** Bearer token. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. **You provide** `api_token` **Setup fields** `host` **Limits we pace to** 20 calls a second, per connection **API covered** Zabbix API 7.4 (JSON-RPC 2.0 at /api_jsonrpc.php), at your Zabbix instance's API base URL, which you enter when connecting **Built from** Zabbix's documentation, read 23 October 2026[zabbix.com](https://www.zabbix.com/documentation/current/en/manual/api/reference) [zabbix.com](https://www.zabbix.com/documentation/current/en/manual/api) **Service file** Version 1.0.0, signed (Ed25519) **Cached reads** 61 of 64 reads, for up to 5 minutes; a write clears what it affects **Shared entities** 7, so ask can line Zabbix up with your other systems **Data** Processed and stored in Sydney, Australia. No US region yet Capabilities ## What an AI agent can do in Zabbix. 224 actions in 14 areas. Every one carries its effect, so a key can allow the reads and hold the rest. - **64** read look, never change - **110** write create and update - **50** destructive wait for a confirmation 1. ### Administration 44 15 read · 21 write · 8 destructive Retrieve audit log records · Create new connector objects · Retrieve connector objects · Retrieve a list of High availability cluster nodes 2. ### Data collection 32 8 read · 16 write · 8 destructive Create new LLD rules · Retrieve LLD rules · Create new LLD rule prototypes · Retrieve LLD rule prototypes 3. ### Hosts 26 4 read · 15 write · 7 destructive Retrieve hosts · Create new hosts · Update existing hosts · Delete hosts 4. ### Users 25 6 read · 14 write · 5 destructive Retrieve users · Retrieve user groups · Retrieve roles · Create new users 5. ### Dashboards 21 6 read · 10 write · 5 destructive Retrieve dashboards · Create new dashboards · Update existing dashboards · Delete dashboards 6. ### Templates 19 3 read · 11 write · 5 destructive Create new templates · Retrieve templates · Create new template dashboards · Retrieve template dashboards 7. ### Alerts 16 6 read · 6 write · 4 destructive Create new actions · Retrieve actions · Retrieve alerts · Create new media types 8. ### Services 9 3 read · 4 write · 2 destructive Retrieve services · Retrieve SLA objects · Create new services · Update existing services **6 more areas · 32 actions** - Discovery **7** - Events **7** - Macros **7** - Maintenance **4** - Monitoring data **4** - Configuration **3** Top actions ## The Zabbix API, shaped for agents. The ids your agent types, what each does, and the one name it shares with other systems. 37 of Zabbix's 37 action names are shared with at least one other connector, so an agent learns them once. | Action | What it does | Effect | Same name in | | --- | --- | --- | --- | | `zabbix.user.get` Retrieve users | The method allows you to retrieve users according to the given parameters. | read | `identity.user.list` 474 connectors | | `zabbix.usergroup.get` Retrieve user groups | The method allows you to retrieve user groups according to the given parameters. | read | `identity.group.list` 262 connectors | | `zabbix.role.get` Retrieve roles | The method allows you to retrieve roles according to the given parameters. | read | `identity.role.list` 184 connectors | | `zabbix.user.create` Create new users | This method allows you to create new users. | write | `identity.user.create` 262 connectors | | `zabbix.usergroup.create` Create new user groups | This method allows you to create new user groups. | write | `identity.group.create` 205 connectors | | `zabbix.role.create` Create new roles | This method allows you to create new roles. | write | `identity.role.create` 105 connectors | | `zabbix.problem.get` Retrieve problems | The method allows you to retrieve problems according to the given parameters. | read | `monitoring.alert.list` 51 connectors | | `zabbix.user.delete` Delete users | This method allows you to delete users. | destructive | `identity.user.delete` 253 connectors | | `zabbix.host.get` Retrieve hosts | The method allows you to retrieve hosts according to the given parameters. | read | `device.endpoint.list` 65 connectors | | `zabbix.service.get` Retrieve services | The method allows you to retrieve services according to the given parameters. | read | `monitoring.service.list` 12 connectors | | `zabbix.token.create` Create new tokens | This method allows you to create new tokens. | write | `identity.api_key.create` 100 connectors | | `zabbix.token.get` Retrieve tokens | The method allows you to retrieve tokens according to the given parameters. | read | `identity.api_key.list` 96 connectors | Try it ## Prompts to paste into Claude. Each one names the Zabbix actions it will call, so you know what it reads and what it changes before you send it. 1. Read read Which Zabbix alerts are open right now? Group them by service. calls `zabbix.problem.get` 2. Write write Create new users in Zabbix. Show me exactly what you will send before you save it. calls `zabbix.user.create` Governance for Zabbix ## Destructive actions wait for a yes. 50 Zabbix actions are destructive. The first 10: - Delete users `zabbix.user.delete` - Delete user groups `zabbix.usergroup.delete` - Delete roles `zabbix.role.delete` - Delete tokens `zabbix.token.delete` - Delete services `zabbix.service.delete` - Delete hosts `zabbix.host.delete` - Delete SLA entries `zabbix.sla.delete` - Delete dashboards `zabbix.dashboard.delete` - Delete maps `zabbix.map.delete` - Delete MFA methods `zabbix.mfa.delete` A destructive action runs only with `confirm: true`. Under the `human` policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after. do zabbix.user.delete confirm_policy: **human** Delete users? **intent:** the user asked me to delete users run suspended · waiting for a named person · key _zabbix-agent_ cannot confirm itself In the console, or from an emailed signed link. a key for this connector ``` account { op: "keys.create", name: "zabbix-agent", allowed_actions: ["zabbix.*"], cap_calls: 2000, confirm_policy: "human_for_writes", approval_rules: [ { match: "zabbix.user.delete", approver: "lead@example.com" }, { match: "zabbix.usergroup.delete", approver: "lead@example.com" }, { match: "zabbix.role.delete", approver: "lead@example.com" } ] } ``` Illustrative. Scoped to Zabbix only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person. Cost ## What Zabbix costs on actionlake. Every Zabbix action is one upstream call, the only thing actionlake bills. Searching, `check`, `cost`, `account` and any call Zabbix refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000. - 1 upstream call per action all 224 Zabbix actions - 224 actions page each page of a long list is one call - 61 reads can be cached a cache hit costs nothing - 100,000 calls a month, free paid plans from US$49 a month for 250,000 [See pricing](https://actionlake.com/pricing) Action index ## Every Zabbix action. 224 actions by area: the id your agent calls, what it does, and its effect. **Administration 44** - `zabbix.auditlog.get` Retrieve audit log records read - `zabbix.authentication.get` Retrieve authentication object read - `zabbix.authentication.update` Update existing authentication settings write - `zabbix.autoregistration.get` Retrieve autoregistration object read - `zabbix.autoregistration.update` Update existing autoregistration write - `zabbix.connector.create` Create new connector objects write - `zabbix.connector.delete` Delete connector entries destructive - `zabbix.connector.get` Retrieve connector objects read - `zabbix.connector.update` Update existing connectors write - `zabbix.hanode.get` Retrieve a list of High availability cluster nodes read - `zabbix.housekeeping.get` Retrieve housekeeping object read - `zabbix.housekeeping.update` Update existing housekeeping settings write - `zabbix.iconmap.create` Create new icon maps write - `zabbix.iconmap.delete` Delete icon maps destructive - `zabbix.iconmap.get` Retrieve icon maps read - `zabbix.iconmap.update` Update existing icon maps write - `zabbix.image.create` Create new images write - `zabbix.image.delete` Delete images destructive - `zabbix.image.get` Retrieve images read - `zabbix.image.update` Update existing images write - `zabbix.mfa.create` Create new MFA methods write - `zabbix.mfa.delete` Delete MFA methods destructive - `zabbix.mfa.get` Retrieve MFA methods read - `zabbix.mfa.update` Update existing MFA methods write - `zabbix.module.create` Install new frontend modules write - `zabbix.module.delete` Uninstall modules destructive - `zabbix.module.get` Retrieve modules read - `zabbix.module.update` Update existing modules write - `zabbix.proxy.create` Create new proxies write - `zabbix.proxy.delete` Delete proxies destructive - `zabbix.proxy.get` Retrieve proxies read - `zabbix.proxy.update` Update existing proxies write - `zabbix.proxygroup.create` Create new proxy groups write - `zabbix.proxygroup.delete` Delete proxy groups destructive - `zabbix.proxygroup.get` Retrieve proxy groups read - `zabbix.proxygroup.update` Update existing proxy groups write - `zabbix.regexp.create` Create new global regular expressions write - `zabbix.regexp.delete` Delete global regular expressions destructive - `zabbix.regexp.get` Retrieve global regular expressions read - `zabbix.regexp.update` Update existing global regular expressions write - `zabbix.settings.get` Retrieve settings object read - `zabbix.settings.update` Update existing common settings write - `zabbix.task.create` Create tasks write - `zabbix.task.get` Retrieve tasks read **Data collection 32** - `zabbix.discoveryrule.create` Create new LLD rules write - `zabbix.discoveryrule.delete` Delete LLD rules destructive - `zabbix.discoveryrule.get` Retrieve LLD rules read - `zabbix.discoveryrule.update` Update existing LLD rules write - `zabbix.discoveryruleprototype.create` Create new LLD rule prototypes write - `zabbix.discoveryruleprototype.delete` Delete LLD rule prototypes destructive - `zabbix.discoveryruleprototype.get` Retrieve LLD rule prototypes read - `zabbix.discoveryruleprototype.update` Update existing LLD rule prototypes write - `zabbix.httptest.create` Create new web scenarios write - `zabbix.httptest.delete` Delete web scenarios destructive - `zabbix.httptest.get` Retrieve web scenarios read - `zabbix.httptest.update` Update existing web scenarios write - `zabbix.item.create` Create new items write - `zabbix.item.delete` Delete items destructive - `zabbix.item.get` Retrieve items read - `zabbix.item.update` Update existing items write - `zabbix.itemprototype.create` Create new item prototypes write - `zabbix.itemprototype.delete` Delete item prototypes destructive - `zabbix.itemprototype.get` Retrieve item prototypes read - `zabbix.itemprototype.update` Update existing item prototypes write - `zabbix.trigger.create` Create new triggers write - `zabbix.trigger.delete` Delete triggers destructive - `zabbix.trigger.get` Retrieve triggers read - `zabbix.trigger.update` Update existing triggers write - `zabbix.triggerprototype.create` Create new trigger prototypes write - `zabbix.triggerprototype.delete` Delete trigger prototypes destructive - `zabbix.triggerprototype.get` Retrieve trigger prototypes read - `zabbix.triggerprototype.update` Update existing trigger prototypes write - `zabbix.valuemap.create` Create new value maps write - `zabbix.valuemap.delete` Delete value maps destructive - `zabbix.valuemap.get` Retrieve value maps read - `zabbix.valuemap.update` Update existing value maps write **Hosts 26** - `zabbix.host.create` Create new hosts write - `zabbix.host.delete` Delete hosts destructive - `zabbix.host.get` Retrieve hosts read - `zabbix.host.massadd` Simultaneously add multiple related objects to all the given hosts write - `zabbix.host.massremove` Remove related objects from multiple hosts destructive - `zabbix.host.massupdate` host.massupdate write - `zabbix.host.update` Update existing hosts write - `zabbix.hostgroup.create` Create new host groups write - `zabbix.hostgroup.delete` Delete host groups destructive - `zabbix.hostgroup.get` Retrieve host groups read - `zabbix.hostgroup.massadd` hostgroup.massadd write - `zabbix.hostgroup.massremove` Remove related objects from multiple host groups destructive - `zabbix.hostgroup.massupdate` hostgroup.massupdate write - `zabbix.hostgroup.propagate` Apply permissions and tag filters to all subgroups of a host group write - `zabbix.hostgroup.update` Update existing hosts groups write - `zabbix.hostinterface.create` Create new host interfaces write - `zabbix.hostinterface.delete` Delete host interfaces destructive - `zabbix.hostinterface.get` Retrieve host interfaces read - `zabbix.hostinterface.massadd` Simultaneously add host interfaces to multiple hosts write - `zabbix.hostinterface.massremove` Remove host interfaces from the given hosts destructive - `zabbix.hostinterface.replacehostinterfaces` Replace all host interfaces on a given host write - `zabbix.hostinterface.update` Update existing host interfaces write - `zabbix.hostprototype.create` Create new host prototypes write - `zabbix.hostprototype.delete` Delete host prototypes destructive - `zabbix.hostprototype.get` Retrieve host prototypes read - `zabbix.hostprototype.update` Update existing host prototypes write **Users 25** - `zabbix.role.create` Create new roles write - `zabbix.role.delete` Delete roles destructive - `zabbix.role.get` Retrieve roles read - `zabbix.role.update` Update existing roles write - `zabbix.token.create` Create new tokens write - `zabbix.token.delete` Delete tokens destructive - `zabbix.token.generate` Generate tokens write - `zabbix.token.get` Retrieve tokens read - `zabbix.token.update` Update existing tokens write - `zabbix.user.create` Create new users write - `zabbix.user.delete` Delete users destructive - `zabbix.user.get` Retrieve users read - `zabbix.user.provision` Provision LDAP users write - `zabbix.user.resettotp` Reset user TOTP secrets write - `zabbix.user.unblock` Unblock users write - `zabbix.user.update` Update existing users write - `zabbix.userdirectory.create` Create new user directories write - `zabbix.userdirectory.delete` Delete user directories destructive - `zabbix.userdirectory.get` Retrieve user directories read - `zabbix.userdirectory.test` Test user directory connection settings read - `zabbix.userdirectory.update` Update existing user directories write - `zabbix.usergroup.create` Create new user groups write - `zabbix.usergroup.delete` Delete user groups destructive - `zabbix.usergroup.get` Retrieve user groups read - `zabbix.usergroup.update` Update existing user groups write **Dashboards 21** - `zabbix.dashboard.create` Create new dashboards write - `zabbix.dashboard.delete` Delete dashboards destructive - `zabbix.dashboard.get` Retrieve dashboards read - `zabbix.dashboard.update` Update existing dashboards write - `zabbix.graph.create` Create new graphs write - `zabbix.graph.delete` Delete graphs destructive - `zabbix.graph.get` Retrieve graphs read - `zabbix.graph.update` Update existing graphs write - `zabbix.graphitem.get` Retrieve graph items read - `zabbix.graphprototype.create` Create new graph prototypes write - `zabbix.graphprototype.delete` Delete graph prototypes destructive - `zabbix.graphprototype.get` Retrieve graph prototypes read - `zabbix.graphprototype.update` Update existing graph prototypes write - `zabbix.map.create` Create new maps write - `zabbix.map.delete` Delete maps destructive - `zabbix.map.get` Retrieve maps read - `zabbix.map.update` Update existing maps write - `zabbix.report.create` Create new scheduled reports write - `zabbix.report.delete` Delete scheduled reports destructive - `zabbix.report.get` Retrieve scheduled reports read - `zabbix.report.update` Update existing scheduled reports write **Templates 19** - `zabbix.template.create` Create new templates write - `zabbix.template.delete` Delete templates destructive - `zabbix.template.get` Retrieve templates read - `zabbix.template.massadd` Simultaneously add multiple related objects to the given templates write - `zabbix.template.massremove` Remove related objects from multiple templates destructive - `zabbix.template.massupdate` template.massupdate write - `zabbix.template.update` Update existing templates write - `zabbix.templatedashboard.create` Create new template dashboards write - `zabbix.templatedashboard.delete` Delete template dashboards destructive - `zabbix.templatedashboard.get` Retrieve template dashboards read - `zabbix.templatedashboard.update` Update existing template dashboards write - `zabbix.templategroup.create` Create new template groups write - `zabbix.templategroup.delete` Delete template groups destructive - `zabbix.templategroup.get` Retrieve template groups read - `zabbix.templategroup.massadd` templategroup.massadd write - `zabbix.templategroup.massremove` Remove related objects from multiple template groups destructive - `zabbix.templategroup.massupdate` Replace templates with the specified ones in multiple template groups write - `zabbix.templategroup.propagate` Apply permissions to all template groups' subgroups write - `zabbix.templategroup.update` Update existing template groups write **Alerts 16** - `zabbix.action.create` Create new actions write - `zabbix.action.delete` Delete actions destructive - `zabbix.action.get` Retrieve actions read - `zabbix.action.update` Update existing actions write - `zabbix.alert.get` Retrieve alerts read - `zabbix.mediatype.create` Create new media types write - `zabbix.mediatype.delete` Delete media types destructive - `zabbix.mediatype.get` Retrieve media types read - `zabbix.mediatype.update` Update existing media types write - `zabbix.script.create` Create new scripts write - `zabbix.script.delete` Delete scripts destructive - `zabbix.script.execute` Run a script on a host or event destructive - `zabbix.script.get` Retrieve scripts read - `zabbix.script.getscriptsbyevents` script.getscriptsbyevents read - `zabbix.script.getscriptsbyhosts` script.getscriptsbyhosts read - `zabbix.script.update` Update existing scripts write **Services 9** - `zabbix.service.create` Create new services write - `zabbix.service.delete` Delete services destructive - `zabbix.service.get` Retrieve services read - `zabbix.service.update` Update existing services write - `zabbix.sla.create` Create new SLA objects write - `zabbix.sla.delete` Delete SLA entries destructive - `zabbix.sla.get` Retrieve SLA objects read - `zabbix.sla.getsli` Calculate the Service Level Indicator read - `zabbix.sla.update` Update existing SLA entries write **Discovery 7** - `zabbix.dcheck.get` Retrieve discovery checks read - `zabbix.dhost.get` Retrieve discovered hosts read - `zabbix.drule.create` Create new discovery rules write - `zabbix.drule.delete` Delete discovery rules destructive - `zabbix.drule.get` Retrieve discovery rules read - `zabbix.drule.update` Update existing discovery rules write - `zabbix.dservice.get` Retrieve discovered services read **Events 7** - `zabbix.correlation.create` Create new correlations write - `zabbix.correlation.delete` Delete correlations destructive - `zabbix.correlation.get` Retrieve correlations read - `zabbix.correlation.update` Update existing correlations write - `zabbix.event.acknowledge` Update events write - `zabbix.event.get` Retrieve events read - `zabbix.problem.get` Retrieve problems read **Macros 7** - `zabbix.usermacro.create` Create new host macros write - `zabbix.usermacro.createglobal` Create new global macros write - `zabbix.usermacro.delete` Delete host macros destructive - `zabbix.usermacro.deleteglobal` Delete global macros destructive - `zabbix.usermacro.get` Retrieve host and global macros read - `zabbix.usermacro.update` Update existing host macros write - `zabbix.usermacro.updateglobal` Update existing global macros write **Maintenance 4** - `zabbix.maintenance.create` Create new maintenances write - `zabbix.maintenance.delete` Delete maintenance periods destructive - `zabbix.maintenance.get` Retrieve maintenances read - `zabbix.maintenance.update` Update existing maintenances write **Monitoring data 4** - `zabbix.history.clear` Clear item history destructive - `zabbix.history.get` Retrieve history data read - `zabbix.history.push` Sending item history data to Zabbix server write - `zabbix.trend.get` Retrieve trend data read **Configuration 3** - `zabbix.configuration.export` Export configuration data as a serialized string read - `zabbix.configuration.import` Import configuration data from a serialized string write - `zabbix.configuration.importcompare` configuration.importcompare read Questions ## The Zabbix MCP server, answered. **Is there a Zabbix MCP server for Claude?** Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 224 Zabbix actions across administration, data collection, hosts and users, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Zabbix. **What do I need to connect Zabbix?** Zabbix API token: in the Zabbix frontend open Users > API tokens (or User settings > API tokens for your own user),…. Plus your host. The free call account { op: "connections.requirements", service: "zabbix" } lists exactly what to paste. **Can an AI agent delete or change things in Zabbix?** Only if its key allows it, and only with an explicit confirmation. 50 Zabbix actions are destructive, including delete users, delete user groups and delete roles. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it. **Will an AI agent use up my Zabbix API limit?** actionlake paces every call to the limits in the Zabbix service file: 20 calls a second per connection. Repeated reads are answered from cache (61 Zabbix actions can be), which never reaches Zabbix. **What does a Zabbix action cost?** One upstream call, the only unit actionlake bills. A list that pages bills one call per page (224 Zabbix actions page). Cache hits, searches, dry runs and calls Zabbix refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000. **Which Zabbix API does it cover?** The Zabbix API 7.4 (JSON-RPC 2.0 at /api_jsonrpc.php) at your Zabbix instance's API base URL, which you enter when connecting. It is built from Zabbix's documentation as read on 23 October 2026. 224 actions in 14 areas, each one in the signed service file (version 1.0.0). **Does actionlake keep my Zabbix data, and where?** actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Zabbix credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models. **Which AI clients can use it?** Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names. ## More connectors like Zabbix Shares the most action names with - [TeamViewer 18](https://actionlake.com/connectors/teamviewer) - [Tactical RMM 15](https://actionlake.com/connectors/tactical-rmm) - [Commvault Cloud 13](https://actionlake.com/connectors/commvault-cloud) - [Site24x7 12](https://actionlake.com/connectors/site24x7) - [Action1 11](https://actionlake.com/connectors/action1) - [Cato Networks SASE 10](https://actionlake.com/connectors/cato-networks-sase) Joins with, on shared entities - [Palo Alto Networks Cortex XDR 5](https://actionlake.com/connectors/palo-alto-networks-cortex-xdr) - [Microsoft 365 Users 4](https://actionlake.com/connectors/microsoft-365-users) - [Okta 4](https://actionlake.com/connectors/okta) - [Rootly 4](https://actionlake.com/connectors/rootly) - [JumpCloud 4](https://actionlake.com/connectors/jumpcloud) - [FireHydrant 4](https://actionlake.com/connectors/firehydrant) Browse - [All MSP & PSA connectors](https://actionlake.com/connectors/category/msp-and-psa) - [All connectors](https://actionlake.com/connectors) - [How actionlake compares](https://actionlake.com/compare) actionlake is independent. It is not made or endorsed by Zabbix; the name is the vendor's own. Counts are from the Zabbix service file, version 1.0.0. ## Give your agent Zabbix today. [Connect Zabbix free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free. --- Source: https://actionlake.com/connectors/zabbix More: https://actionlake.com/llms.txt