Teamdeck icon

Teamdeck

Interact with Teamdeck API for project management and time tracking
Join our community

Actions15

Overview

This node integrates with the Teamdeck API to manage bookings of resources (people) on projects. Specifically, the Booking - Create operation allows users to create a new booking by specifying the project, resource, and booking period. This is useful in scenarios where you want to schedule or allocate resources to projects for specific date ranges, such as planning team availability, managing workloads, or tracking resource assignments.

Practical examples:

  • Automatically creating bookings when a new project phase starts.
  • Scheduling contractors or employees for certain projects within defined time frames.
  • Integrating with other systems to sync resource allocations dynamically.

Properties

Name Meaning
Project ID The unique identifier of the project for which the booking is created.
Resource ID The unique identifier of the person or resource to be booked.
Start Date The start date of the booking (format: YYYY-MM-DD).
End Date The end date of the booking (format: YYYY-MM-DD).
Additional Fields Optional extra fields to specify additional details about the booking:
  Description An optional text description for the booking.
  Time Fraction A number between 0 and 1 representing the fraction of full-time allocation (e.g., 0.5 = 50%).

| Add Additional JSON | Whether to add custom JSON data that will be passed through from input to output. |
| Additional JSON | Custom JSON data to pass through from input to output if "Add Additional JSON" is enabled. |

Output

The node outputs JSON data representing the newly created booking object returned by the Teamdeck API. The output includes all standard booking properties such as:

  • Booking ID
  • Project ID
  • Resource ID
  • Start and end dates
  • Description
  • Time fraction

If the "Add Additional JSON" option is used, the provided JSON data is merged into the output under an additionalJson field.

The node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating with the Teamdeck API.
  • The node makes HTTP requests to the Teamdeck API endpoint at https://api.teamdeck.io/v1/bookings.
  • Proper configuration of the API key credential in n8n is necessary for successful operation.

Troubleshooting

  • Missing required fields: The node requires project_id, resource_id, start_date, and end_date. Omitting any of these will cause errors.
  • Invalid date format: Dates must be in YYYY-MM-DD format. Incorrect formats may lead to API errors.
  • API authentication errors: Ensure the API key credential is valid and has sufficient permissions.
  • API response errors: If the API returns unexpected data or errors, the node throws an error indicating the problem.
  • Empty update fields (not applicable here but relevant for update operations): For update operations, at least one field must be specified; otherwise, an error is thrown.
  • Continue on Fail: If enabled, errors for individual items are captured and returned in a separate output, allowing the workflow to continue processing other items.

Links and References

This summary is based solely on static analysis of the provided source code and property definitions.

Discussion