checkmk-square

Checkmk

· #437 most-used

Your infrastructure, monitored and acted on automatically

ProductivityAnalyticsDeveloperSecurityAutomation

Checkmk is an open-source IT infrastructure monitoring platform that tracks hosts, services, metrics, and alerts across servers, containers, Kubernetes clusters, and cloud environments. Connect it to Actionist and your agents can list hosts, acknowledge problems, schedule downtimes, discover services, pull metric history, and update notification rules — all in plain English, all without opening the Checkmk UI. Turn monitoring data into automated incident response.

Average time saved
11 hours
per person · per month
≈ 1 workdays back

Eliminates manual work. Agents eliminate the manual steps between a Checkmk alert firing and the right action being taken — acknowledging problems, scheduling downtimes, creating tickets, and updating status pages without human relay.

Schedule

What your Checkmk agent runs on autopilot

A week of scheduled jobs your Actionist agent will execute on your behalf.

28Scheduled jobs
7Agents at work
24/7Always on
Agents
WedFri
Wed
Thu
Fri
7a
8a
9a
10a
11a
12p
1p
2p
3p
4p
5p
6p
Multi-app workflows

Checkmk × every other app you use

End-to-end automations that span multiple apps — each one a real business outcome.

6Workflows
9Apps spanned
~17 hrsSaved / week
6Personas served
For customer success
Featured4 apps

SLA breach alert to customer in 60 seconds

When a critical service email arrives flagging a monitored host, your agent reads the sender's account record, pulls the current Checkmk service state and metric history for their infrastructure, schedules a downtime window to prevent alert noise during investigation, and fires a personalised status email to the customer — all before the first support engineer has opened their laptop. SLA breach notifications that previously took 15 minutes of manual coordination now land on the customer's screen in under a minute.

~6 hrs

Time saved for your team — every week, on autopilot

The flow
Trigger·When a customer-reported incident email arrives in the support inbox
Result
Schedule downtime to suppress repeat alertsNotify customer-success team with service detailsBook emergency review call with customer
The win
Saved per run
45 min
Runs / week
~8×
Customers hear from you before they chase you
Driven byCustomer Support Agent
ROI

Savings

What your team gets back — two angles: what you stop doing manually, and what that's worth.

Without Actionist

What you do manually today

With Actionist

What your agent runs for you

  • Sales
    19 min / week
    Manual demo prep

    A sales engineer spends 20 minutes before each prospect demo manually pulling host counts, service states, and uptime figures from Checkmk to populate the demo health sheet.

    Sales Agent
    0 min
    Agent generates the demo sheet

    When a demo-prep request lands in Slack, the agent queries Checkmk, writes the health summary to the sheet, and books the prep call — before the engineer has clicked anything.

  • Marketing
    14 min / week
    Delayed status updates

    When infrastructure issues affect customer-facing services, marketing waits 15+ minutes for engineering to confirm the scope before updating the public status page.

    Marketing Agent
    0 min
    Agent posts to status page in 2 minutes

    The agent queries Checkmk for service state on report and commits a status-page incident update to GitHub Pages before the first customer follow-up email arrives.

  • Customer Support
    19 min / week
    Alert-to-customer lag

    Support engineers manually cross-reference Checkmk alerts with customer accounts before sending incident notifications, adding 10–20 minutes to every customer-facing outage response.

    Customer Support Agent
    0 min
    Agent notifies customer in 60 seconds

    The agent reads the service state, schedules a downtime, and sends a personalised customer email automatically when a support-flagged incident arrives in the inbox.

  • Human Resources
    8 min / week
    Manual on-call load audit

    HR relies on engineering managers to self-report on-call burden; there is no systematic way to check whether the notification load is distributed fairly across team members.

    Human Resources Agent
    0 min
    Agent reports notification distribution

    The agent lists Checkmk notifications per engineer each week and flags anyone receiving disproportionately high page volume, feeding directly into the wellbeing review.

  • Finance
    14 min / week
    SLA data gathering

    Finance spends two hours at month-end manually extracting downtime records, matching them to approved maintenance windows, and calculating uptime percentages for customer SLA reports.

    Finance Agent
    0 min
    Agent assembles SLA report on day one

    When the monthly SLA Notion page is created, the agent pulls metric history and notification logs from Checkmk and populates the report automatically, including flagging any breach requiring a credit.

  • Operations
    30 min / week
    Manual host registration

    Every new server requires an ops engineer to manually create the host in Checkmk, trigger service discovery, and activate changes — a 15-minute process that is easy to forget during busy provisioning runs.

    Operations Agent
    0 min
    Agent monitors every server from minute one

    When a new row appears in the inventory sheet, the agent creates the host, runs discovery, activates changes, and logs the result to Notion — fully automated, zero clicks.

  • Legal
    6 min / week
    Compliance evidence export

    Legal manually requests notification logs from the ops team for each audit cycle, then waits days for someone to extract and format the data from Checkmk into a presentable CSV.

    Legal Agent
    0 min
    Agent exports audit evidence on request

    The agent lists Checkmk notifications for the audit period, filters for critical-host events, and exports a timestamped CSV proving every CRIT triggered an alert — delivered in minutes, not days.

+ 100s of other Checkmk automations
Average monthly
11 hrs / person / month
Average monthly
11 hrs / person / month
Calculator

Calculate what your team saves

Team size
10 person
Hourly rate
$20 / hr
Hours saved / week
28
Hours saved / year
1,400
Annual ROI
$28,000

Based on Checkmk's typical team usage — the visible tasks plus a few other automations the agent runs: ~2.8 hrs / person / week of admin work automated.

Connect

How to plug Checkmk into Actionist

Pick the connection method that suits your environment.

The fastest path to full Checkmk automation. Install the Checkmk MCP server and the agent connects to your site through a permissioned handshake — list hosts, acknowledge problems, and schedule downtimes without managing API tokens or site URLs manually.

1
Open the Apps tab

Find Checkmk in the Apps library and click Connect. MCP is selected by default.

2
Authorise in Checkmk

Enter your Checkmk site URL (e.g. https://monitoring.yourcompany.com/mysite) and grant the Actionist MCP server read and write access to the REST API. A dedicated automation user with the least required permissions is recommended.

3
Test the connection

Actionist runs a read-only call to list hosts and verify the handshake. You're ready when the host count appears.

Actions

16 actions your agent can call

Read and write operations available to your Actionist agent.

Triggers

8 event your agent can react to

Events your agent watches for, and the actions it kicks off in response.

Skills

Skills that pair with Checkmk

Reusable agent skills that work well alongside this app.

No paired skills curated yet. Add this app to your agent to discover what fits.
MCP servers

MCP servers that work with Checkmk

Connect Actionist to MCP servers built for or around this app.

No MCP servers indexed for this app yet.
FAQs

Questions about Checkmk + Actionist

How does the agent connect to my Checkmk site?
The recommended path is the Checkmk MCP server, which handles authentication through a permissioned handshake. Alternatively you can connect with an automation user's API secret — create a dedicated Checkmk user under Setup → Users, generate an Automation secret, and paste it into Actionist. The agent then communicates with your site's REST API over HTTPS.
What permissions does the automation user need?
For read-only operations (listing hosts, querying service states, fetching metrics) a user with the built-in 'Guest' role is sufficient. To write — acknowledge problems, schedule downtimes, create hosts, activate changes — the user needs the 'Normal monitoring user' role or a custom role with the relevant permissions enabled. Principle of least privilege: only grant what the workflows actually need.
Will the agent accidentally activate changes I didn't intend?
The Activate Changes action only runs when explicitly included in a workflow step or when you ask the agent to activate changes. It does not fire automatically after every write operation. If you want a human review gate before activation, structure your workflow to pause after creating or updating hosts and only activate on explicit approval.
Can the agent monitor multiple Checkmk sites?
Yes. Connect each site as a separate Checkmk app instance in Actionist, each with its own site URL and automation credentials. Workflows can then reference a specific site connection, or you can build multi-site workflows that query several connections in sequence.
How does downtime scheduling work — can the agent schedule a downtime that's already past?
The Checkmk REST API requires that downtime start times be in the future. If the agent tries to schedule a downtime with a start time in the past, the API will return an error. Build your workflows to calculate the start time dynamically (e.g. 'now') rather than using hardcoded timestamps.
Does the agent support Checkmk Raw Edition as well as Cloud or Enterprise?
The Checkmk REST API is available in all editions — Raw, Cloud, and Enterprise. The actions in Actionist use the standard REST API endpoints that are present across all editions. Some advanced features (distributed monitoring, business intelligence) may only be available in Enterprise; those capabilities are outside the scope of the current action set.
How does the agent handle Checkmk's two-phase configuration model?
Checkmk separates configuration changes (creating hosts, updating rules) from activating them. The agent's Create Host, Update Host, and Delete Host actions write to the pending configuration. The Activate Changes action then applies the pending changes live. Workflows that create hosts should include an Activate Changes step at the end, or your monitoring will not start until someone activates manually.
Can the agent disconnect from Checkmk without losing my workflows?
Disconnecting removes the active credential but does not delete your workflow definitions. Workflows that include a Checkmk action step will fail at runtime if the connection is inactive. Reconnecting with valid credentials restores full functionality. No Checkmk data is stored in Actionist beyond the authentication token.