Create Halo PSA Client: Halo P S A action

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
Name name	string	Required	Name

Sample request

{
  "name": "{{trigger.name}}"
}

Returns

{}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Create Halo PSA Client.

What does the Create Halo PSA Client action do in Halo P S A?

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.

What inputs does Create Halo PSA Client require?

Required: Name. 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 Create Halo PSA Client support batch operations?

Yes. Run Create Halo PSA Client 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