HaloPSA
Raise and manage HaloPSA tickets and look up clients, sites, agents and assets.
OCNORA ships 9 typed HaloPSA operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect HaloPSA
- Authentication
- OAuth 2.0
- Credential
- {"client_id": "…", "client_secret": "…"} or {"client_id": "…", "refresh_token": "…"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with HaloPSA
Operations, grouped by what they do to your data.
Create and send 1
Read and search 6
Update 1
Delete and cancel 1
A sample HaloPSA workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no HaloPSA trigger is needed.
- 2Get Tickethalopsa.get_ticketRead one ticket by its Halo id.
- 3Create Tickethalopsa.create_ticketRaise a new ticket on the service desk.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 9
- Create TicketRaise a new ticket on the service desk.halopsa.create_ticket
- Delete TicketDelete a ticket and the objects related to it.halopsa.delete_ticket
- Get TicketRead one ticket by its Halo id.halopsa.get_ticket
- List AgentsList the agents on the Halo instance.halopsa.list_agents
- List AssetsList assets, optionally narrowed to a client, site or asset type.halopsa.list_assets
- List ClientsList the clients on the Halo instance.halopsa.list_clients
- List SitesList sites, optionally only those belonging to one client.halopsa.list_sites
- List TicketsList tickets, with the filters Halo's ticket listing accepts.halopsa.list_tickets
- Update TicketChange one or more properties of an existing ticket.halopsa.update_ticket
HaloPSA questions
- How does OCNORA authenticate with HaloPSA?
- With a stored OAuth 2.0 credential, shaped {"client_id": "…", "client_secret": "…"} or {"client_id": "…", "refresh_token": "…"}. A connection test can check it when you add it.
- What can I automate with HaloPSA?
- 9 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the HaloPSA operation I need is not listed?
- Where HaloPSA has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use HaloPSA?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are HaloPSA calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
More in Business apps
See your first HaloPSA workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.