Integrations & Automation

Halo ITSM

Runbooks, JSON examples, and patterns you can lift straight into your own Halo instance. Includes scheduled automation, ticket updates, and safer custom-table handling.

← Back to Halo SQL & Reporting →

Runbooks JSON Scheduling Iteration

Runbooks

Full runbook exports (JSON) you can import and adapt.

RUNBOOK Set closed date/time via runbook Allows “close-like” statuses to set clear time RUNBOOK Clear import placeholder asset tags Removes OTB “ABC…” tags ready for next import RUNBOOK Sync site contact roles (scheduled) Adds Site Manager role for site contacts RUNBOOK Link draft article to ticket Associates draft KB/article content to a ticket RUNBOOK Update custom-table row (preserve other rows) Safer linked-table updates when multiple rows exist

JSON examples

Drop-in stages/snippets for custom tables and safer updates.

JSON Add a new row to a custom table Create a new linked-table entry

Adds a new record to a custom table. If your custom table is linked to a request/ticket, include "key": <<ticket^id>> at the top level before "id".

JSON

{
  "id": 1004,
  "_isimport": true,
  "_importtype": "runbook",
  "customfields": [
    {
      "id": 211,
      "type": 7,
      "usage": 1004,
      "value": [
        {
          "customfields": [
            {
              "name": "CFParameters",
              "value": "TEST for 1"
            }
          ]
        }
      ]
    }
  ]
}

JSON Edit one custom-table row without losing others Important behaviour note for linked tables

This updates a field in a linked custom table row. Halo can remove other rows when multiple values exist if you only send one row back. For “edit one + keep the rest”, first capture existing rows then loop and re-add.

JSON

{
  "id": 1004,
  "edit_customfields": [
    {
      "id": 208,
      "value": [
        {
          "id": 8,
          "customfields": [
            {
              "id": "211",
              "value": "Test 12345"
            }
          ]
        }
      ]
    }
  ]
}