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
Recurring Invoice → Create
AI-generatedSummary
Create a HaloPSA recurring invoice for a client, using the client ID and optional invoice header fields supplied as JSON.
Inputs
- Client ID (required) — Numeric ID of the client for the recurring invoice; the UI default is 0.
- Additional Fields — JSON object of RecurringInvoiceHeader fields, such as summary, status, and lines. Defaults to an empty object.
Output shape
A single recurring invoice record returned by HaloPSA.
The source pack shows the operation entry point but omits its implementation body, so the precise response handling is not visible.
Examples
Example 1: Set the client ID to the HaloPSA client and provide any desired recurring invoice header fields in Additional Fields.
Client ID and RecurringInvoiceHeader JSON.