Overview
This node interacts with the Hubstaff API to retrieve multiple tasks associated with a project or organization. It is designed to fetch lists of tasks filtered by project and status, which is useful for project management automation, reporting, or synchronization workflows.
Typical use cases include:
- Retrieving all active tasks for a specific project to display in dashboards.
- Fetching archived or filtered tasks for audit or review purposes.
- Integrating task data into other systems or automations that require up-to-date task lists from Hubstaff.
Properties
| Name | Meaning |
|---|---|
| Project ID | The unique identifier of the project whose tasks you want to retrieve. |
| Status Filter | Filter tasks by their status. Options: All (no filter), Active, Archived, Archived Native Active, Archived Native Deleted |
Output
The output is an array of JSON objects, each representing a task retrieved from Hubstaff. Each task object contains the fields as returned by the Hubstaff API under the /tasks endpoint, such as task ID, summary, description, assignee, status, and other metadata.
No binary data is output by this node.
Dependencies
- Requires an API authentication token obtained via a refresh token credential configured in n8n.
- Needs the organization ID configured in credentials or a project ID provided as input to determine the scope of tasks.
- Makes HTTPS requests to the Hubstaff API endpoints.
Troubleshooting
- Missing Refresh Token: If the refresh token is not set in credentials, the node will throw an error indicating it is required.
- Organization ID or Project ID Missing: When fetching tasks, either the project ID must be provided or the organization ID must be configured in credentials; otherwise, an error is thrown.
- API Request Failures: Network issues or invalid tokens can cause request failures. Ensure the API credentials are valid and have proper permissions.
- Empty or Unexpected Responses: If no tasks match the filters, the output will be empty. Verify the project ID and status filter values.
- Rate Limits: Excessive requests may hit API rate limits; handle errors accordingly and consider adding delays or retries.