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 interacts with the Autotask REST API to retrieve detailed information about a specific project by its ID. It is useful for workflows that need to fetch project data for reporting, integration, or automation purposes. For example, you can use it to get project details to update a CRM system, generate project status reports, or trigger notifications based on project attributes.
Properties
| Name | Meaning |
|---|---|
| Project ID | The unique identifier of the project to retrieve. |
| Add Picklist Labels | Determines whether to add additional '_label' fields for picklist fields to provide human-readable values instead of raw codes. |
| Add Reference Labels | Determines whether to add '_label' fields for reference fields to show human-readable values. |
| Select Columns Names or IDs. | Specifies which fields to include in the response. If none are selected, all fields are returned. The project ID is always included. |
| Flatten User-Defined Fields | If enabled, user-defined fields (UDFs) are moved to the top level of the returned object instead of being nested inside an array. |
Output
JSON
id- The unique identifier of the project.name- The name of the project.description- Description or details about the project.picklistField_label- Human-readable label for picklist fields if 'Add Picklist Labels' is enabled.referenceField_label- Human-readable label for reference fields if 'Add Reference Labels' is enabled.userDefinedFields- Array of user-defined fields associated with the project, unless flattened.flattenedUDFField- User-defined fields presented as top-level properties if 'Flatten User-Defined Fields' is enabled.
Dependencies
- Requires an API key credential for authenticating with the Autotask REST API.
Troubleshooting
- If the node returns an error indicating the project ID is invalid or not found, verify that the provided Project ID exists in Autotask.
- If no data is returned, check that the API credentials are correct and have sufficient permissions to access project data.
- Errors related to picklist or reference labels may occur if the fields do not have associated labels; consider disabling label addition if not needed.
- If user-defined fields are not appearing as expected, verify the 'Flatten User-Defined Fields' setting and the structure of the project data in Autotask.
Links
- Autotask Project API Documentation - Official Autotask API documentation for the Project resource.
- n8n Autotask Node Documentation - General documentation on using the Autotask node in n8n workflows.