Actions32
- Assignment Actions
- Client Actions
- Project Actions
- Report Actions
- Task Actions
- Time Actions
- Timecard Actions
- Webhook Actions
Overview
This node interacts with the Everhour API to retrieve multiple projects based on specified criteria. It is designed to fetch a list of projects, optionally filtered by name and platform, and supports returning either all matching projects or a limited subset.
Common scenarios where this node is beneficial include:
- Synchronizing project lists from Everhour into other systems.
- Filtering projects by platform (e.g., Asana, Jira) for reporting or automation workflows.
- Retrieving a manageable number of projects when dealing with large datasets.
For example, you could use this node to get all Jira projects whose names contain "Marketing" or limit the results to 20 Trello projects for further processing.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching projects or only up to a specified limit. |
| Limit | Maximum number of projects to return if "Return All" is false. Minimum value is 1. |
| Search Query | Text string to search projects by their name. |
| Platform | Filter projects by platform. Options: All (no filter), Asana, Basecamp, Jira, Trello. |
Output
The output is an array of JSON objects, each representing a project retrieved from Everhour. Each object contains the project's details as returned by the Everhour API, such as project ID, name, associated client ID, platform, and other metadata.
No binary data is output by this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Everhour API.
- The node uses the base URL provided by the configured API credentials.
- No additional external dependencies are required beyond the Everhour API access.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing an invalid platform filter value (not in the allowed options) may result in no results or errors.
- Network connectivity issues can prevent successful API calls.
Error messages:
- Authentication errors typically indicate problems with the API key; verify that the credential is correctly set up.
- Rate limiting or API quota exceeded errors require checking Everhour account limits.
- If no projects are returned, ensure the search query and platform filters are correct and that projects exist matching those criteria.
Links and References
- Everhour API Documentation
- n8n Documentation on HTTP Request Node (for understanding API request handling)
- Everhour Official Website