Integration Runbooks

A Break down of the Automated Statement of Work Generation & AI Project task Creation

Automated Statement of Work Generation

Backend Services Monitoring

This article provides a comprehensive guide on Backend Services Monitoring using Halo. It explains how to monitor backend services such as automations, integration syncs, emails, and webhooks. The guide includes instructions to navigate the monitoring area, set log levels, manage background services, and conduct maintenance. It details various logs like task scheduler, incoming/outgoing emails, and events to troubleshoot issues. Additionally, it covers integration errors and monitoring events to help identify and resolve issues efficiently.

Creating Report Data Within a Runbook (Matching and Merging to Existing Alert Tickets)

This article provides a guide on creating report data within a runbook and matching email alerts to existing alert tickets. It explains how to configure runbooks to pull data from a Halo database using SQL queries, and how to manage alert tickets by merging them based on a shared Alert Ticket ID. The article details the steps for creating and using runbook-level variables, setting up email rules to capture alert IDs, and configuring runbooks to update or merge tickets as new alerts arrive.

Custom Integrations

This guide explains how to set up custom integrations in Halo, which are used for authenticating and executing requests to external APIs, allowing integration with other tools. It covers the process of creating custom integrations, choosing authorization methods, and setting up integration methods. Custom integration methods define the requests and endpoints for data exchange with other applications. The guide also explains using runbooks to execute these integration methods, detailing steps configuration, execution flow, and linking methods with multiple Halo instances for consistent functionality.

Custom Integrations/Runbooks

This article provides a comprehensive guide to creating and managing custom integrations and runbooks in the Halo platform. It covers the basic building blocks of runbooks, runbook statistics, various trigger options, and how to use output variables in subsequent steps. The guide also includes methods for integrating with external APIs, using Halo API actions, and securing sensitive data through encryption. Practical examples are given to illustrate the steps required to configure and use runbooks effectively, including triggering actions based on ticket workflows and custom buttons.

Example of how to implement Request Signing for Integration Runbook Authentication

Execute Automation Runbooks from the Chatbot

Handling Attachments/Files in Runbooks

Iterative Runbooks

Log Retention

Runbook Level Variables

Runbook: Append a Recurring Invoice from Sales Order lines

Runbook: Update Status of Child Tickets

Runbook: Update the Estimated Time Based on the Category Chosen

Runbooks - Authorising API Access into Your Own Halo Instance

Triggering Automation Policies in RMM via Halo

Webhook and Integration Runbook Access Control

This guide explains how to implement access control for webhooks and integration runbooks, allowing specific agents to configure selected webhooks and runbooks without full admin privileges. Agents with access can view and edit existing runbooks and webhooks but cannot create new ones; only administrators have creation rights. Access control is granted by the creator of a webhook/runbook and is managed through an 'Access Control' button. Access is assigned by roles or departments with varying levels, such as read and modify or owner. Each new runbook/webhook requires access settings.

Webhook To Trigger a Runbook

This article provides a detailed guide on setting up a webhook to trigger a runbook in Halo's Runbooks module. The process involves creating a new runbook, obtaining its URL for use as a webhook payload URL, and defining an event trigger, such as 'Invoice Created'. The guide explains how to configure settings, view logs, and utilize runbook-level variables, using the example of an Invoice ID. The runbook URL allows external triggers to initiate predefined sequences through POST requests.