Actions524
- AI Helper Actions
- Tool Actions
- API Threshold Actions
- Appointment Actions
- Billing Code Actions
- Billing Items Actions
- Change Request Link Actions
- Checklist Library Actions
- Checklist Library Item Actions
- Classification Icon Actions
- Company Actions
- Company Alert Actions
- Company Location Actions
- Company Note Actions
- Company Webhook Actions
- Company Site Configuration Actions
- Configuration Item Actions
- Configuration Item Billing Product Association Actions
- Configuration Item Category Actions
- Configuration Item Category UDF Association Actions
- Configuration Item DNS Record Actions
- Configuration Item Note Actions
- Configuration Item Related Item Actions
- Configuration Item SSL Subject Alternative Name Actions
- Configuration Item Type Actions
- Configuration Item Webhook Actions
- Contact Actions
- Contact Webhook Actions
- Contact Groups Actions
- Contact Group Contacts Actions
- Contract Actions
- Contract Block Actions
- Contract Block Hour Factor Actions
- Contract Billing Rule Actions
- Contract Charge Actions
- Contract Exclusion Billing Code Actions
- Contract Exclusion Role Actions
- Contract Exclusion Sets Actions
- Contract Exclusion Set Excluded Role Actions
- Contract Exclusion Set Excluded Work Type Actions
- Contract Milestone Actions
- Contract Note Actions
- Contract Rate Actions
- Contract Role Costs Actions
- Contract Retainer Actions
- Contract Service Actions
- Contract Service Adjustment Actions
- Contract Service Bundle Adjustment Actions
- Contract Service Bundle Actions
- Contract Service Bundle Unit Actions
- Contract Ticket Purchase Actions
- Department Actions
- Project Phase Actions
- Quote Item Actions
- Quote Location Actions
- Quote Template Actions
- Resource Actions
- Resource Role Actions
- Resource Role Queue Actions
- Search Filter Actions
- Service Actions
- Service Call Actions
- Subscription Actions
- Subscription Period Actions
- Ticket Category Actions
- Ticket Category Field Default Actions
- Ticket History Actions
- Ticket Note Actions
Appointment → Get Many (Advanced)
AI-generatedOverview
This node operation retrieves multiple appointment records from the Autotask PSA system using advanced filtering criteria. It allows users to specify detailed JSON-based filters to query appointments, control the number of records returned, and customize the output fields. This operation is useful for scenarios where users need to extract specific appointment data based on complex conditions, such as date ranges, statuses, or other appointment attributes.
Use Case Examples
- Retrieve all appointments scheduled within a specific date range using a JSON filter.
- Fetch up to 100 appointments with a particular status or assigned resource.
- Use advanced filters to get appointments that meet multiple criteria, such as location and type.
Properties
| Name | Meaning |
|---|---|
| Get All | Whether to return all results or only up to a given limit (maxRecords). |
| Max Records | Maximum number of appointment records to return when 'Get All' is false. Range is 1 to 500. |
| Advanced Filter | A JSON string containing a 'filter' array with Autotask API query criteria to filter the appointments returned. |
| Add Picklist Labels | Whether to automatically add '_label' fields for picklist fields with human-readable values in the output. |
| Add Reference Labels | Whether to automatically add '_label' fields for reference fields with human-readable values in the output. |
| Select Columns Names or IDs | Choose which appointment fields to include in the response. If no fields are selected, all fields are returned. The ID field is always included. |
| Flatten User-Defined Fields | Whether to bring user-defined fields up to the top level of each appointment object instead of nested in the userDefinedFields array. |
Output
JSON
id- Unique identifier of the appointment record.fieldName_label- Human-readable labels for picklist or reference fields if enabled.
userDefinedFieldsfieldName- User-defined fields nested or flattened based on the flattenUdfs option.
Dependencies
- Autotask PSA API with appropriate API key credentials
Troubleshooting
- Ensure the advancedFilter JSON is correctly formatted and contains a valid 'filter' array as per Autotask API documentation.
- If no records are returned, verify the filter criteria match existing appointment data.
- Check API credentials and permissions to access appointment data.
- If the node throws errors related to rate limits, consider API usage limits and retry strategies.
Links
- Autotask API Basic Query Calls - Official Autotask API documentation for constructing filter queries.