Chekhub

· #438 most-used

Keep every asset, ticket, and field team in one operational register

ProductivityProjectsHRDeveloperSchedulingFormsAutomation

Chekhub is an operations management platform that centralises assets, tickets, checklists, and field team coordination in a single system. Built for facilities management, field service, and multi-site operations, it tracks every physical asset, structures every maintenance task as a templated work order, and manages the full member roster across sites. Connect it to Actionist and your agents can create and monitor tickets from any external trigger, build and sync the asset register from procurement or ERP data, attach compliance documents to inspection tickets automatically, and extract operational cost data into finance systems — all without anyone logging into Chekhub to do it manually.

Try Chekhub with Actionist Visit Chekhub

Average time saved

9 hours

per person · per month

≈ 1 workdays back

Eliminates manual work. Agents eliminate the manual cycle of creating tickets from alerts, reconciling asset registers against external systems, extracting operational cost data for finance, and scheduling preventive maintenance intervals.

Schedule

What your Chekhub 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

Tue–Thu

Tue

Wed

Thu

10a

11a

12p

Multi-app workflows

Chekhub × every other app you use

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

6Workflows

6Apps spanned

~16 hrsSaved / week

5Personas served

For operations

Featured3 apps

New equipment registered in Chekhub on delivery

When a new equipment delivery is logged in the Google Sheets receiving register, the operations agent checks whether the asset already exists in Chekhub, creates it with the full metadata from the delivery row, and opens a commissioning inspection ticket. The asset is in the register and the first service ticket is live before the delivery team has finished unloading.

~3 hrs

Time saved for your team — every week, on autopilot

The flow

Trigger·When a new equipment delivery row is added to the receiving register in Google Sheets

Trigger

Step 1

Google Sheets

Detect new row in equipment delivery register

read

Step 2

Chekhub

List Assets to check whether asset already exists

write

Step 3

Chekhub

Create Asset with model, serial number, and delivery date

write

Step 4

Chekhub

Create a Ticket for first-use commissioning inspection

write

Step 5

Slack

Post asset registration and ticket details to #operations

Result

Create Asset with model, serial number, and delivery dateCreate a Ticket for first-use commissioning inspectionPost asset registration and ticket details to #operations

The win

Saved per run

25 min

Runs / week

~8×

Every delivered asset enters the register with a commissioning ticket the same day

Driven byOperations 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
25 min / week
Manual survey ticket prep
The sales coordinator manually creates a Chekhub ticket before each site survey, picking the right template, filling in prospect details, and assigning it to the field engineer — averaging 10 minutes per booking.
Sales Agent
0 min
Agent creates survey tickets with the right template instantly
When a prospect site survey is booked, the agent selects the appropriate Chekhub template for the industry and creates a structured ticket before the appointment is confirmed.
Marketing
20 min / week
Weekly content metrics pull
The marketing coordinator manually exports Chekhub ticket data, formats the resolution time stats, and shares the spreadsheet with the content team — 20 minutes every week.
Marketing Agent
0 min
Agent extracts ticket metrics for content weekly
Every Tuesday the agent pulls closed ticket data and delivers resolution time metrics to the content team's spreadsheet — no Chekhub exports, no manual formatting.
Customer Support
30 min / week
Manual SLA breach monitoring
Support leads manually review open Chekhub tickets twice a week, checking creation timestamps against SLA clocks and chasing technicians by message when a breach looks likely.
Customer Support Agent
0 min
Agent monitors SLA timers and comments on near-breach tickets
The support agent checks all open tickets against SLA resolution targets mid-week and posts a progress chase comment on any ticket approaching breach — catching it before it becomes a missed SLA.
Human Resources
15 min / week
Manual onboarding ticket creation
HR manually creates a Chekhub ticket for each new starter, picking the onboarding template, filling in the details, and notifying facilities by email — 15 minutes per hire, often done the morning of the start date.
Human Resources Agent
0 min
Agent creates onboarding tickets for every new starter automatically
When a new employee is added to the HRIS, the agent creates a structured Chekhub onboarding ticket with equipment requirements and access checklist pre-populated — facilities are briefed before day one.
Finance
30 min / week
Monthly maintenance cost extraction
Finance manually requests a Chekhub export of closed tickets, reformats the cost data in Excel, and enters the aggregated figures into the finance system — a process that takes 2-3 hours at every month end.
Finance Agent
0 min
Agent extracts ticket costs to finance systems at month end
At month close, the agent pulls all closed tickets and writes the aggregated cost breakdown to the finance spreadsheet — maintenance spend data is available for close without a manual export.
Operations
45 min / week
Manual asset register reconciliation
A senior facilities manager manually exports the Chekhub asset list and compares it against the procurement register in Excel, identifying mismatches row by row — half a day every month if done properly.
Operations Agent
0 min
Agent runs the asset register accuracy check in minutes
Every Monday the agent lists all Chekhub assets, compares them against the master manifest, and surfaces discrepancies before the operations standup — a register audit that would take a manager half a day to run manually.
Legal
40 min / week
Manual statutory inspection scheduling
The compliance officer manually monitors the inspection calendar, identifies affected assets, creates individual Chekhub tickets, and attaches the relevant documentation — often done the week before and rarely with full documentation.
Legal Agent
0 min
Agent schedules statutory inspection tickets 30 days in advance
When a statutory inspection date appears on the compliance calendar 30 days out, the agent identifies all relevant assets and creates a Chekhub ticket for each with the regulatory reference and certificate template attached.

+ 100s of other Chekhub automations

Average time saved

21 hrs / person / month

Calculator

Calculate what your team saves

Team size

5 people

Hourly rate

$75 / hr

Hours saved / week

Hours saved / year

550

Annual ROI

$41,250

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

Connect

How to plug Chekhub into Actionist

Pick the connection method that suits your environment.

Connect Chekhub to Actionist using an API key generated from your Chekhub account settings. The key authorises the agent to read and write tickets, assets, elements, and members according to the scopes you assign.

Generate your Chekhub API Key

Log in to Chekhub and navigate to Settings. Under the Accounts or API section, click Create API Key to generate a new credential.

Set permissions and copy the key

Select the required permission scopes — read access for list and get operations, write access for create and update operations. Copy the generated key and store it securely.

Paste into Actionist

Paste the key into Actionist's Chekhub credential field and click Test connection. Actionist runs a read-only call to confirm the handshake.

Credentials you'll need

API Key*

Chekhub → Settings → Create API Key. Select the permissions your agent needs and copy the generated token.

Actions

19 actions your agent can call

Read and write operations available to your Actionist agent.

Triggers

0 events your agent can react to

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

This app has no triggers yet.

FAQs

Questions about Chekhub + Actionist

How does Actionist connect to Chekhub?

Go to the Apps tab, find Chekhub, and click Connect. Enter your Chekhub API key — generate one by logging into Chekhub, navigating to Settings, and creating a new API key under the Accounts section. Paste it into the API key field, click Test connection, and Actionist runs a read-only call to confirm the handshake. The agent gains access to your tickets, assets, elements, and member directory immediately.

What permissions does the agent need on my Chekhub account?

Actionist needs an API key scoped to your Chekhub organisation. The key is generated from within your Chekhub account under Settings. For read actions — listing assets, pulling tickets, fetching members — the key needs read access. For write actions — creating tickets, creating assets, adding attachments, posting comments — it needs write access as well. Generate the key while logged in as an admin so it inherits the right permissions, and store it securely in Actionist's credential vault.

Can I connect Chekhub to other apps in the same workflow?

Yes. Chekhub works best when connected to the other systems your operations team already uses. Common combinations: create a Chekhub ticket whenever a maintenance alert fires in your monitoring tool; pull asset data from Chekhub and write it to a Google Sheets register; update element records when a field technician closes out work in another system; sync member lists between Chekhub and your HRIS. Any of Actionist's 200+ connected apps can send or receive data alongside Chekhub in the same agent task.

What are the most common things agents do with Chekhub?

The four patterns that come up most in operations teams: (1) automated ticket creation — whenever a condition is detected elsewhere (a sensor reading, a support request, an asset threshold), the agent opens a Chekhub ticket without a human typing it; (2) asset audits — pulling all assets or elements on a schedule, cross-referencing against an expected list, and flagging gaps; (3) comment and attachment workflows — when a ticket is resolved in another system, the agent logs a comment and attaches the resolution document in Chekhub; (4) member roster syncs — keeping the Chekhub member list in step with the HR or identity system so no ex-employee retains access.

How does API key authentication work for Chekhub in Actionist?

The Chekhub API uses API key authentication via a bearer token in the Authorization header. Actionist stores and rotates your credential securely — you paste it once and the agent handles the header on every call. If the key is ever regenerated in Chekhub, update it in Actionist's credential settings and all your agent tasks pick up the new key automatically without any workflow edits.

What is the difference between Assets, Elements, and Locations in Chekhub?

Chekhub supports multiple asset types — physical assets, locations, and generic elements — each with a distinct API endpoint. When creating assets in bulk, use the Create Multiple Assets action, which accepts a batch payload and returns all created records in one call. For location hierarchies, use Create Location to establish the parent-child site structure before assigning assets to it. Elements are the most flexible entity type in Chekhub and can model anything not covered by the typed Asset or Ticket resources.

Does Chekhub support real-time triggers or webhooks in Actionist?

Chekhub does not currently expose a webhook-based outbound trigger in its API surface available to Actionist. Actionist monitors Chekhub on a polling cadence — checking for new or updated tickets, assets, and elements within about a minute of each check cycle. For time-sensitive workflows, configure a short polling interval on the relevant scheduled agent task. If your Chekhub account emits webhooks in future, Actionist will be able to consume them as event triggers directly.

Can agents attach documents and photos to Chekhub tickets?

Yes. Chekhub's Create a Ticket action accepts an optional attachment field pointing to an uploaded file. Use Add Attachment from Upload to attach files stored in your Actionist-connected storage (Google Drive, Dropbox, or any direct URL). For files already in your Chekhub media library, use Add Attachment from Library instead, which references the asset by its library ID. Attaching inspection reports, photos, or compliance documents to tickets from other systems is a common automation pattern for field service and facilities teams.