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 manage clients and other resources. Specifically, for the Client - Get Many operation, it retrieves multiple client records from Everhour. It supports filtering clients by name through a search query and allows either fetching all matching clients or limiting the number of results returned.
Common scenarios where this node is beneficial include:
- Synchronizing client lists from Everhour into another system.
- Generating reports or dashboards that require client data.
- Automating workflows that depend on client information retrieval.
For example, you could use this node to fetch all clients whose names contain "Acme" and then process their data further in your workflow.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching clients or only up to a specified limit |
| Limit | Maximum number of client records to return (used only if "Return All" is false) |
| Search Query | Filter clients by name containing this string (optional; empty means no filtering) |
Output
The output is an array of JSON objects, each representing a client retrieved from Everhour. Each object contains the client's details as provided by the Everhour API.
- If "Return All" is true, all matching clients are returned.
- If "Return All" is false, only up to the specified "Limit" number of clients are returned.
- The output items are paired with the input item index for traceability.
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 configured in the credential to make HTTP GET requests.
- No additional external dependencies beyond the Everhour API and n8n's HTTP request helpers.
Troubleshooting
- Empty Results: If no clients are returned, verify the search query string and ensure clients exist in Everhour matching that query.
- Authentication Errors: Ensure the API key credential is valid and has sufficient permissions to read client data.
- Rate Limits: If many clients are requested with "Return All" enabled, be mindful of Everhour API rate limits which may cause errors or delays.
- Invalid Limit: Setting the limit below 1 will not work; the minimum allowed value is 1.
Common error messages:
- Authentication failures typically indicate invalid or missing API credentials.
- HTTP errors from the API (e.g., 404, 500) suggest issues with the endpoint or server status.
- Network errors may occur if the base URL is incorrect or there is connectivity loss.
Resolving these usually involves checking credentials, network settings, and API availability.