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
This node operation retrieves a specific survey result from the Autotask system by its unique Survey Result ID. It is useful when you need to fetch detailed data about a particular survey response, for example, to analyze customer feedback or integrate survey data into other workflows.
Properties
| Name | Meaning |
|---|---|
| Survey Result ID | The unique identifier of the survey result to retrieve, required to specify which survey result to fetch. |
| Add Picklist Labels | Whether to automatically add human-readable "_label" fields for picklist fields in the survey result, enhancing readability of picklist values. |
| Add Reference Labels | Whether to automatically add human-readable "_label" fields for reference fields in the survey result, improving clarity of referenced data. |
| Select Columns Names or IDs. | Specify which fields (columns) to include in the response. If none are selected, all fields are returned. The ID field is always included regardless of selection. |
| Flatten User-Defined Fields | Whether to bring user-defined fields (UDFs) up to the top level of the returned object instead of nested inside a userDefinedFields array, simplifying access to these fields. |
Output
JSON
id- The unique identifier of the survey result.fieldName_label- Human-readable labels for picklist or reference fields if enabled.
userDefinedFields- Array of user-defined fields if not flattened; otherwise, UDFs appear as top-level properties.
Dependencies
- Requires an API key credential for Autotask REST API authentication.
Troubleshooting
- Ensure the Survey Result ID provided is correct and exists in the Autotask system; otherwise, the node will return an error indicating the resource was not found.
- If picklist or reference labels are not appearing, verify that the corresponding boolean options are enabled and that the fields have non-empty values.
- If selecting specific columns, ensure the column names or IDs are valid; invalid selections may cause incomplete or empty responses.
- Authentication errors may occur if the API key credential is missing or invalid; verify credentials in the node settings.