Skip to content

HaloPSA Documentation

Instances

  • https://prod.crm.titantelecoms.au/ - Production
  • https://staging.crm.titantelecoms.au/ - Staging / UAT

Ticket Alerting

Currently Titan Telecoms alerts on inbound tickets, and responses using HaloPSA Custom Integrations and Runbooks poking Pushover's API;

You can read more about the HaloPSA Custom Integrations / Runbooks flows below;

  • https://halopsa.com/guides/article/?kbid=1630 - Custom Integrations/Runbooks
  • https://halopsa.com/guides/article/?kbid=1853 - Iterative Runbooks
  • https://halopsa.com/guides/article/?kbid=2356 - Workflow Runbook Automations

You can read more about the Pushover AI below;

  • https://pushover.net/api - Custom Integrations/Runbooks

You can find the production Pushover 2.0 Custom Integrations / Runbooks flows below;

  • https://prod.crm.titantelecoms.au/config/integrations/customintegrations/runbooks?id=8e4736c9-943c-4bee-afdc-1d89e634cd0f - Custom Integrations/Runbooks

Currently logic is as below;

Step Condition Value
Start Ticket Type Includes Incident, Network Operations, Engineering
Is New? Ticket Status Is equal to New
Is With User? Ticket Status Is equal to With User

Todo

  • Update Is New, Is With User logic to Includes rather than expicits
  • wavePortal UAT / alignment