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 time tracking data, specifically focusing on "Time-Entry" resources. The Get Many operation retrieves multiple time entries from Teamdeck, optionally filtered by criteria such as start date, end date, project ID, or resource ID. This is useful for scenarios where you want to analyze or report on logged time across projects and resources, for example:

  • Generating timesheets for a team over a specific period.
  • Extracting all time entries related to a particular project.
  • Auditing resource utilization by filtering entries by resource ID.

The node supports pagination internally and can return either all matching results or limit the number of returned entries.

Properties

Name Meaning
Filters Collection of optional filters to narrow down the time entries:
- Start Date: Filter entries starting from this date (inclusive).
- End Date: Filter entries up to this date (inclusive).
- Project ID: Filter entries belonging to a specific project.
- Resource ID: Filter entries associated with a specific resource/person.
Return All Boolean flag indicating whether to return all matching results or limit the output.
Limit Maximum number of results to return if "Return All" is false. Minimum 1, default 50.
Add Additional JSON Whether to include additional user-provided JSON data in the output alongside each entry.
Additional JSON JSON object to pass through from input to output when "Add Additional JSON" is enabled.

Output

The node outputs an array of JSON objects representing time entries retrieved from Teamdeck. Each item includes all standard fields provided by the Teamdeck API for a time entry, such as IDs, dates, minutes logged, description, project and resource references, etc.

If "Add Additional JSON" is enabled, the specified JSON data is merged into each output item under the additionalJson property.

No binary data is produced by this node.

Example output item structure (simplified):

{
  "id": "string",
  "project_id": "string",
  "resource_id": "string",
  "start_date": "YYYY-MM-DD",
  "end_date": "YYYY-MM-DD",
  "minutes": 120,
  "description": "Worked on feature X",
  "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.
  • No other external dependencies are required.

Troubleshooting

  • Common issues:

    • Missing or invalid API key will cause authentication failures.
    • Providing invalid filter values (e.g., malformed dates) may result in API errors.
    • Requesting too many results without enabling "Return All" may truncate data unexpectedly.

  • Error messages:

    • "Start date is required" or "End date is required": These appear if creating or updating entries without specifying mandatory dates (not applicable for Get Many but relevant for other operations).
    • "Invalid API response received": Indicates unexpected or empty responses from the API; check network connectivity and API status.
    • "Unknown operation" or "Unknown resource": Configuration errors where unsupported operations or resources are selected.

  • Resolution tips:

    • Ensure the API key credential is correctly configured and has necessary permissions.
    • Validate date formats and filter inputs before running the node.
    • Use "Return All" cautiously to avoid large data loads that might impact performance.

Links and References

Discussion