Skip to content

Alerts

Alerts tell you when something changes, so you don't have to open the Bridge to notice. Trimtab can send them by email, to a Microsoft Teams or Slack channel, to any webhook, or straight into your PSA as tickets.

Owners and Admins with access to all clients manage alerts from Settings > Alerts.

What counts as an alert

Alert When
New failure A check that passed on the previous scan now fails or warns
Fix A check that failed or warned on the previous scan now passes
Device stopped reporting A Windows device hasn't sent results for 3 days
Device back A device that stopped reporting sends results again

Each scan is compared with the one before it and judged by the client's standards, the same way the device page judges it. A device's first scan never alerts, and neither does a check that has been failing all along. Use the Fleet and Checks pages for those.

Turn alerts on

Settings > Alerts has a switch for each way Trimtab can reach you: Email, Microsoft Teams, Slack, Webhook, and PSA tickets.

  1. Turn on the switch. Its settings open below it.
  2. Fill in the settings (see below). For PSA tickets, first choose which PSA; its settings appear once you do.
  3. Choose what to send: new failures, fixes, devices that stop reporting, or any mix.
  4. Choose a severity. High only is the quietest; All severities sends everything. Offline devices always count.
  5. Choose All clients or Selected clients.
  6. Select Turn on, then Send a test (for a PSA, Open and close a test ticket).

Turning a switch off later pauses that channel and keeps its settings, so turning it back on picks up where you left off. Remove deletes the settings. Each channel has one set of settings, and PSA tickets go to one PSA at a time; to switch PSAs, remove the current one first.

Secrets you enter (keys, passwords, webhook URLs) are encrypted when they're saved and never shown again. To change one, type the new value; leave it blank to keep the saved one. If you change where a destination sends (a PSA's URL or site, the Autotask API username, or a webhook URL), enter its secrets again: Trimtab never sends a saved secret to a new address.

Email

Enter up to 10 addresses. Choose As it happens for one email per scan with changes, or Once a day for a single summary at the time and time zone you pick. A daily summary is skipped when nothing changed.

Microsoft Teams

In the Teams channel, open Workflows and add the template Post to a channel when a webhook request is received. Copy the URL it gives you into Trimtab. Alerts arrive as a card with a link to each device.

Slack

Create an incoming webhook for the channel and paste its URL.

Webhook

Trimtab sends a JSON POST for each batch of alerts:

{
  "source": "trimtab",
  "test": false,
  "events": [
    {
      "id": 412,
      "type": "fail",
      "at": "2026-10-24T14:05:11+00:00",
      "summary": "CD-FRONT-01: BitLocker protects all fixed drives (now fails)",
      "client": {"id": 3, "name": "Contoso Dental"},
      "device": {"id": "8f0c...", "name": "CD-FRONT-01", "kind": "windows"},
      "check": {"id": "ENC-001", "title": "BitLocker protects all fixed drives", "severity": "High", "status": "Fail", "previous": "Pass"},
      "message": "BitLocker is off on C:.",
      "url": "https://app.trimtabsec.com/devices/8f0c..."
    }
  ]
}

type is fail, fixed, offline, or online. For offline and online, check is null.

If you set a signing secret, each request carries X-Trimtab-Signature: sha256=<hex>, the HMAC-SHA256 of the raw body with your secret. Compute the same value and compare before you trust a request.

PSA tickets

With ConnectWise PSA, Autotask, or HaloPSA, each new failure becomes one ticket, with what Trimtab found, the steps to fix it, and the requirements it affects. When the check passes again, Trimtab adds a note and closes the ticket. A device that stops reporting gets a ticket that closes when it reports again.

Trimtab doesn't open a second ticket for a check that already has an open one. Tickets you close yourself stay closed; if the check is still failing, Trimtab doesn't reopen them.

Tell Trimtab where each client's tickets go: choose or enter the PSA's company (or client) for each Trimtab client, or a default for all of them. A client with neither isn't ticketed, and the Alerts page lists it.

Open and close a test ticket checks the credentials, the company, and the closed status in one step.

ConnectWise PSA

  1. In ConnectWise, go to System > Members > API Members, create an API member with permission to add and edit service tickets, and generate an API key pair.
  2. In Trimtab, enter your site (for example api-na.myconnectwise.net), the company ID you sign in with, and the public and private keys.
  3. Optionally choose a service board and the closed status for that board (default Closed (resolved)).
  4. For each client, enter the ConnectWise company identifier (the short ID on the company record).

Autotask

  1. Create an API user (Admin > Resources (Users), security level API User (system)), and choose a custom internal integration as its API tracking identifier.
  2. In Trimtab, enter the API user's username, secret, and tracking identifier. Trimtab finds your Autotask zone on its own.
  3. Select Connect to Autotask. Trimtab reads your queues, issue types, priorities, statuses, and active companies from Autotask, and picks your default queue.
  4. Choose where tickets go:
    • Queue, and optionally an issue type and sub-issue type (the sub-issue list follows the issue type).
    • The priority for High, Medium, and Low checks. These start as Autotask's High, Medium, and Low.
    • The status when the check passes. It starts as Complete.
  5. For each client, choose its Autotask company. Start typing to search. Trimtab suggests a company for each client whose name matches (it ignores endings like LLC and Inc.) and highlights the suggestion. Check each one before you save; you can also type a company ID.

New tickets are opened with the status New, and the due date is 3 days out. To pick up a new company or queue later, select Reload lists; you don't have to retype the secret.

HaloPSA

  1. In Halo, go to Configuration > Integrations > HaloPSA API and add an application that uses Client ID and Secret (Services), logs in as an agent, and has the edit:tickets and read:customers permissions.
  2. In Trimtab, enter your Halo URL (for example https://yourcompany.halopsa.com), the client ID and secret, and the tenant if your API page shows one.
  3. Optionally enter a ticket type ID and the closed status ID (Halo's built-in Closed status is 9).
  4. For each client, enter the Halo client ID.

Different settings for one client

Settings > Alerts applies to every client. To handle one client differently, open Clients and select Alerts on that client. A client with changes shows Custom on the button, and each channel on Settings > Alerts lists the clients that differ from it.

  • Channels. For each channel that's set up, choose Organization setting (the default), On for this client, or Off for this client. On sends the client's alerts even when the channel covers selected clients only. A channel that's off for the whole organization stays off.
  • Severity. Choose which failing checks count for this client on every channel, for example High only for a noisy client. Leave it on Each channel's own setting to follow the channels.
  • Client contacts. Email addresses at the client, such as an office manager. They get alerts about that client only, never about your other clients, as they happen or as a daily summary. Send a test to the client contacts sends a test that names the client. Clear the addresses to stop sending to them.

For PSA tickets, the client still needs a company in the PSA's settings; the dialog warns when it doesn't have one. Fixes still close tickets that are already open, even if the client's PSA tickets are turned off afterward.

Delivery and history

Recent alerts on the Alerts page shows the latest 50 alerts and what happened to each at every destination: sent, the ticket opened or closed, waiting, retrying, or skipped (with the reason).

If a destination can't be reached, Trimtab retries with growing gaps for about a day, and the channel shows Not delivering with the last error. Turning a channel off drops alerts that were waiting for it. Alerts are kept for 90 days.