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, projects, and time entries for project management and resource scheduling. Specifically, the Booking - Get Many operation retrieves multiple booking records from Teamdeck based on optional filters such as start date, end date, project ID, and resource ID.

Typical use cases include:

  • Fetching all bookings within a specific date range to analyze resource allocation.
  • Retrieving bookings related to a particular project or resource for reporting or further automation.
  • Integrating Teamdeck booking data into other workflows or dashboards.

Example: You want to get all bookings for a given project between January 1st and January 31st to generate a utilization report.

Properties

Name Meaning
Filters Collection of optional filters to narrow down the bookings retrieved:
  Start Date Filter bookings starting from this date (inclusive). Format: YYYY-MM-DD or ISO datetime.
  End Date Filter bookings ending by this date (inclusive). Format: YYYY-MM-DD or ISO datetime.
  Project ID Filter bookings by the unique identifier of a project.
  Resource ID Filter bookings by the unique identifier of a resource/person.
Add Additional JSON Boolean flag indicating whether to pass through additional custom JSON data from input to output.
Additional JSON Custom JSON data to be passed through from input to output if "Add Additional JSON" is enabled.

Output

The output is an array of JSON objects, each representing a booking record retrieved from Teamdeck. Each object contains the booking's properties as returned by the Teamdeck API, including but not limited to:

  • Booking identifiers
  • Project and resource IDs
  • Start and end dates of the booking
  • Description and time fraction (allocation percentage)

If the "Add Additional JSON" option is enabled, the provided custom JSON is included in each output item under the additionalJson field.

No binary data is output by this node.

Dependencies

  • Requires an API key credential for authenticating with the Teamdeck API.
  • The node makes HTTP GET requests to the Teamdeck API endpoint /v1/bookings.
  • No additional environment variables are required beyond the API key credential configuration.

Troubleshooting

  • Common issues:

    • Missing or invalid API key will cause authentication failures.
    • Incorrect filter values (e.g., invalid date formats) may result in empty results or API errors.
    • Requesting too many pages without limits could lead to long execution times or rate limiting.

  • Error messages:

    • "Start date is required" or "End date is required" errors occur if these fields are missing when creating or updating bookings (not applicable for Get Many).
    • "Unknown operation: getAll" indicates an unsupported operation was requested.
    • "Invalid API response received" means the API returned unexpected data format.

  • Resolutions:

    • Ensure the API key is correctly configured and has necessary permissions.
    • Validate date inputs and filter parameters before running the node.
    • Use filters to limit the amount of data retrieved.
    • Enable "Continue On Fail" in the node settings to handle partial failures gracefully.

Links and References

Discussion