Actions15
Overview
This node integrates with the Teamdeck API to manage projects, time entries, and bookings. Specifically for the Project - Get operation, it retrieves detailed information about a single project by its unique ID.
Typical use cases include:
- Fetching project details to display or process in workflows.
- Integrating project data into other systems or reports.
- Automating project status checks or updates based on retrieved data.
Example: You have a project ID from a previous step or external source, and you want to get all relevant details about that project (name, description, color, etc.) to use later in your workflow.
Properties
| Name | Meaning |
|---|---|
| Add Additional JSON | Whether to pass through extra JSON data from input to output alongside the main response. |
| Additional JSON | The actual JSON data to pass through if "Add Additional JSON" is enabled. |
| Project ID | The unique identifier of the project to retrieve. |
Output
The node outputs a JSON object representing the project data returned by the Teamdeck API. This includes all standard project fields such as:
id: The project’s unique identifier.name: The name of the project.description: A textual description of the project.color: The color associated with the project (hex code).- Any other fields provided by the Teamdeck API for a project.
If "Add Additional JSON" is enabled, the output JSON will also contain an additionalJson field containing the passed-through JSON data.
No binary data is output by this operation.
Example output structure (simplified):
{
"id": "12345",
"name": "Website Redesign",
"description": "Redesign the corporate website",
"color": "#FF5733",
"additionalJson": { /* optional additional JSON data */ }
}
Dependencies
- Requires an API key credential for authenticating with the Teamdeck API.
- The node uses the Teamdeck REST API endpoint at
https://api.teamdeck.io/v1/projects. - Proper configuration of the API key credential in n8n is necessary.
Troubleshooting
Error: "Please specify at least one field to update"
Occurs if an update operation is attempted without any fields set. For the Get operation, this does not apply but may appear if mixing operations.Invalid API response received
Indicates the API did not return expected data. Check the project ID is correct and the API key has sufficient permissions.Resource not found or 404 errors
Usually means the specified project ID does not exist or is inaccessible. Verify the ID and API credentials.Start date or End date required errors
Not applicable for the Get operation but relevant for other resource operations like bookings or time entries.If the node fails but "Continue On Fail" is enabled, error details are included in the second output.