Actions290
- Action Actions
- Agent Actions
- Appointment Actions
- Approval Process Actions
- Approval Process Rule Actions
- Asset Actions
- Attachment Actions
- Automation Actions
- Canned Text Actions
- Category Actions
- Client Actions
- Contract Actions
- Contract Rule Actions
- Contract Schedule Actions
- Contract Schedule Plan Actions
- Custom API Call Actions
- Feed Actions
- Field Info Actions
- Holiday Actions
- Invoice Actions
- Invoice Payment Actions
- Item Actions
- Knowledge Base Actions
- Lookup Actions
- Notification Actions
- Opportunity Actions
- Outcome Actions
- Product Branch Actions
- Product Component Actions
- Project Actions
- Purchase Order Actions
- Quotation Actions
- Raynet Actions
- Raynet Detail Actions
- Recurring Invoice Actions
- Release Actions
- Release Note Group Actions
- Reporting Actions
- Sales Order Actions
- Secure Secret Link Actions
- Security Check Actions
- Site Actions
- Supplier Actions
- Survey Actions
- Tag Actions
- Team Actions
- Ticket Actions
- Ticket Approval Actions
- Ticket Status Actions
- Ticket To-Do Actions
- Ticket Type Actions
- Timesheet Actions
- Timesheet Event Actions
- Top Level Actions
- Transcription Actions
- User Actions
- Webhook Actions
- Webhook Event Actions
Custom API Call → Request
AI-generatedSummary
Send a GET, POST, PUT, or DELETE request to a HaloPSA API path and return the response as n8n items. Use this operation for HaloPSA endpoints that are not covered by the node’s dedicated operations.
Inputs
- Method (required) — HTTP method: GET (default), POST, PUT, or DELETE.
- Endpoint (required) — API path relative to /api, such as /Ticket or /ClientContract/5. A leading /api/ prefix is stripped automatically.
- Query Parameters — JSON object of query string parameters; supports expressions.
- Body — JSON object or array sent as the request body for POST, PUT, or DELETE. HaloPSA endpoints may expect an array, for example [{"summary":"Example"}].
Output shape
One or more n8n items containing the API response data.
The response is converted into items; the exact item count and fields depend on the endpoint response.