Actions389
- Contract Actions
- Ticket History Actions
- Ticket Note Webhook Actions
- Ticket Note Actions
- Ticket Webhook Actions
- Time Entry Actions
- Resource Actions
- Role Actions
- Resource Role Actions
- Search Filter Actions
- Service Actions
- Skill Actions
- Service Call Actions
- Survey Results Actions
- Survey Actions
- Ticket Actions
- Opportunity Actions
- Notification History Actions
- Invoice Actions
- Product Actions
- Product Vendor Actions
- Project Actions
- Project Charge Actions
- Project Phase Actions
- Project Task Actions
- Project Note Actions
- Contract Retainer Actions
- Contract Service Actions
- Contract Service Adjustment Actions
- Contract Service Bundle Actions
- Contract Service Bundle Unit Actions
- Contract Service Bundle Adjustment Actions
- Contract Ticket Purchase Actions
- Contract Service Unit Actions
- Domain Registrar Actions
- Holiday Actions
- Holiday Set Actions
- Contract Exclusion Billing Code Actions
- Contract Rate 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 Role Costs Actions
- Contact Groups Actions
- Contact Actions
- Contact Webhook Actions
- Contact Group Contacts Actions
- Contract Block Hour Factor Actions
- Contract Block Actions
- Contract Billing Rule Actions
- Contract Charge 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
- Company Alert Actions
- Company Actions
- Billing Code Actions
- Company Location Actions
- Company Note Actions
- Company Webhook Actions
- Configuration Item Actions
- Configuration Item Billing Product Association Actions
Overview
The node's 'Survey' resource with the 'Get Many' operation retrieves multiple survey records from the Autotask system. It allows users to fetch a list of surveys with control over which fields to include, how many records to return, and whether to include human-readable labels for picklist and reference fields. This operation is useful for scenarios such as reporting, data synchronization, or bulk processing of survey data within automation workflows.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines which survey fields to retrieve and map in the output. Supports custom mapping and selection of specific fields. |
| Get All | Determines whether to return all available survey records or limit the number of records returned. |
| Max Records | Specifies the maximum number of survey records to return when 'Get All' is false. Range is 1 to 500. |
| Add Picklist Labels | If enabled, adds additional fields with '_label' suffix containing human-readable labels for picklist fields in the survey data. |
| Add Reference Labels | If enabled, adds additional fields with '_label' suffix containing human-readable labels for reference fields in the survey data. |
| Select Columns Names or IDs. | Allows selection of specific survey fields to include in the response. If none selected, all fields are returned. The ID field is always included. |
| Flatten User-Defined Fields | If enabled, user-defined fields (UDFs) are promoted to top-level properties in each survey object instead of being nested inside a userDefinedFields array. |
Output
JSON
id- Unique identifier of the survey record.
- Requested survey fields as specified in the 'Fields' property._label - Human-readable labels for picklist or reference fields if enabled.userDefinedFields- Array of user-defined fields if 'Flatten User-Defined Fields' is disabled; otherwise, UDFs appear as top-level properties.
Dependencies
- Requires an API key credential for Autotask REST API authentication.
Troubleshooting
- If no records are returned, verify that the survey data exists and that the selected fields are valid for the 'Survey' resource.
- If the node returns an authentication error, ensure the Autotask API credentials are correctly configured and have sufficient permissions.
- When selecting specific fields, ensure the field IDs or names are correct; otherwise, the node may return incomplete data or errors.
- If enabling 'Add Picklist Labels' or 'Add Reference Labels' results in missing labels, check that the corresponding fields have valid values and that the API supports label retrieval for those fields.