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
Contract Schedule → Create
AI-generatedSummary
Create a new contract schedule in HaloPSA by sending a JSON object with the desired fields.
Inputs
- Additional Fields — A JSON object or array containing the fields and their values to include in the POST request body for creating a contract schedule.
Output shape
a single record representing the newly created contract schedule, including its details as returned by the HaloPSA API
The output contains the API response data for the created contract schedule. The shape aligns with the API's POST /ContractSchedule response. Any included optional fields in Additional Fields are reflected in the created record. Errors may be returned if required data is missing or invalid.