Actions15
Overview
This node integrates with the Teamdeck API to manage project-related data, including time entries, projects, and bookings. Specifically, for the Time-Entry - Get operation, it retrieves a single time entry by its unique ID from Teamdeck.
Common scenarios where this node is beneficial include:
- Fetching detailed information about a specific time entry logged by a resource.
- Integrating time tracking data into workflows for reporting or billing.
- Automating retrieval of time entry details for further processing or validation.
Practical example:
- A user wants to retrieve the details of a particular time entry (e.g., hours worked on a project) to generate an invoice or update another system with accurate time tracking data.
Properties
| Name | Meaning |
|---|---|
| Time Entry ID | The unique identifier of the time entry to retrieve. |
| Add Additional JSON | Boolean flag indicating whether to pass through additional JSON data from input to output. |
| Additional JSON | Custom JSON data provided by the user that will be passed through unchanged from input to output if enabled. |
Output
The node outputs a JSON object representing the requested time entry. The structure includes all fields returned by the Teamdeck API for a time entry, such as IDs, dates, minutes logged, description, and related project/resource identifiers.
If "Add Additional JSON" is enabled, the output JSON also contains an additionalJson field carrying the user-provided JSON data.
No binary data output is produced by this operation.
Example output JSON structure (simplified):
{
"id": "string",
"project_id": "string",
"resource_id": "string",
"start_date": "YYYY-MM-DD",
"end_date": "YYYY-MM-DD",
"minutes": 60,
"description": "string",
"additionalJson": { /* user-provided JSON if enabled */ }
}
Dependencies
- Requires an API key credential for authenticating with the Teamdeck API.
- The node makes HTTP requests to
https://api.teamdeck.io/v1/time-entries/{timeEntryId}. - No other external dependencies are required.
Troubleshooting
- Missing or invalid Time Entry ID: The node requires a valid time entry ID. If omitted or incorrect, the API will return an error.
- API authentication errors: Ensure the API key credential is correctly configured and has sufficient permissions.
- Invalid API response: If the API returns unexpected data or no data, the node throws an error "Invalid API response received".
- Date format issues: Although not directly relevant for the Get operation, other operations require dates in
YYYY-MM-DDformat; ensure correct formatting when using those. - Continue On Fail behavior: If enabled, errors for individual items will be captured in the output with error details instead of stopping execution.
Links and References
- Teamdeck API Documentation (general reference for endpoints and data structures)
- n8n documentation on HTTP Request Authentication (for setting up API credentials)
This summary focuses exclusively on the Time-Entry > Get operation as requested.