ActionHalo P S AUpdated May 2026
How do I delete a HaloPSA user?
Short answer: Drop the "Halo P S A → Delete Halo PSA User" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
ID id | string | Required | ID |
Sample request
{"id": "{{trigger.id}}"}
Returns
{}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Delete Halo PSA User.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Delete Halo PSA User.
What does the Delete Halo PSA User action do in Halo P S A?
Removes a user from a client. For "client employee offboarded → revoke HaloPSA portal access" workflows.
What inputs does Delete Halo PSA User require?
Required: ID. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Halo P S A returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Delete Halo PSA User support batch operations?
Yes. Run Delete Halo PSA User inside a Loop node to process arrays. Tiny Command handles Halo P S A's rate limits automatically so you don't have to throttle manually.
More actions
Other Halo P S A actions.
Action
Create Halo PSA Client
Creates a new client (company-level record) in HaloPSA — the MSP-focused PSA/ITSM platform. Useful for "new MSP client onboarded → provision in HaloPSA" workflows.
ActionCreate Halo PSA Site
Creates a physical site/location under a client. For multi-location clients (warehouses, branch offices), each site is tracked separately for asset and ticket attribution.
ActionCreate Halo PSA Ticket
Files a new ticket with subject, description, client, site, priority. The standard hook for "monitoring alert → auto-file ticket" or "client submits via portal → file ticket" workflows.
ActionCreate Halo PSA User
Creates a user under a client (the contact who can file tickets and receive updates). For "new client employee onboarded → grant them HaloPSA access" workflows.
ActionDelete Halo PSA Client
Removes a client (typically with all associated sites, users, tickets). For "MSP relationship terminated → clean up client record" workflows.
ActionDelete Halo PSA Site
Removes a site under a client. For "client closed a location → remove from HaloPSA" cleanup workflows.
Send delete halo psa user from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.
