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
Subscription → Get Many
AI-generatedOverview
This node operation retrieves multiple subscription records from the Autotask PSA system. It supports fetching all records or limiting the number of records returned, making it useful for scenarios where you need to list or process multiple subscriptions, such as generating reports, syncing subscription data, or monitoring subscription statuses.
Use Case Examples
- Fetch all subscription records to synchronize with an external CRM system.
- Retrieve a limited number of subscription records for display in a dashboard or report.
Properties
| Name | Meaning |
|---|---|
| Get All | Whether to return all subscription records or only up to a specified limit. |
| Max Records | The maximum number of subscription records to return when 'Get All' is set to false. The value can range from 1 to 500. |
| Add Picklist Labels | Whether to automatically add '_label' fields for picklist fields with human-readable values in the subscription records. |
| Add Reference Labels | Whether to automatically add '_label' fields for reference fields with human-readable values in the subscription records. |
| Select Columns Names or IDs. | Choose which subscription fields to include in the response. If no fields are selected, all fields will be returned. The ID field is always included regardless of selection. |
| Flatten User-Defined Fields | Whether to bring user-defined fields up to the top level of each subscription object, making them directly accessible instead of nested in the userDefinedFields array. |
Output
JSON
id- Unique identifier of the subscription record.name- Name or title of the subscription.status- Current status of the subscription.startDate- Subscription start date.endDate- Subscription end date.userDefinedFields- Array of user-defined fields associated with the subscription, if not flattened._label- Human-readable labels for picklist or reference fields, if enabled.
Dependencies
- An API key credential for Autotask PSA REST API authentication.
Troubleshooting
- Ensure the API credentials are correctly configured and have sufficient permissions to access subscription data.
- If the node returns no data, verify that subscriptions exist in the Autotask system and that any filters or limits are set appropriately.
- Errors related to rate limits may occur; ensure the API usage complies with Autotask's rate limiting policies.
Links
- Autotask PSA REST API Documentation - Official documentation for the Autotask PSA REST API, useful for understanding available endpoints and data structures.