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 client data. Specifically, the "Client - Get" operation retrieves detailed information about a single client by its unique ID. This is useful when you need to fetch up-to-date client details for reporting, synchronization, or further processing in your workflows.
Common scenarios:
- Fetching client details before creating or updating related projects or tasks.
- Retrieving client information to display or log in other systems.
- Integrating Everhour client data into CRM or billing systems.
Example:
You have a workflow that triggers when a new project is created and needs to pull the associated client's full details to enrich the project metadata or send notifications.
Properties
| Name | Meaning |
|---|---|
| Client ID | The unique numeric identifier of the client to retrieve |
Output
The output is a JSON object representing the client data retrieved from Everhour. It contains all available fields for the client as returned by the Everhour API, such as client name, business details, and any other metadata stored in Everhour.
The output structure corresponds directly to the API response for a single client resource.
No binary data is produced 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 provided API credentials.
- Network access to the Everhour API endpoint is necessary.
Troubleshooting
- Invalid Client ID: If the client ID does not exist or is invalid, the API will likely return an error. Ensure the client ID is correct and exists in your Everhour account.
- Authentication Errors: If the API key credential is missing, expired, or incorrect, authentication will fail. Verify the API key configuration in n8n.
- Network Issues: Connectivity problems can cause request failures. Check network access and proxy settings if applicable.
- API Rate Limits: Excessive requests may be throttled by Everhour. Implement retry logic or reduce request frequency if needed.
Error messages from the node typically include the API error message. Review these messages to identify issues such as unauthorized access, not found resources, or malformed requests.
Links and References
- Everhour API Documentation
- Everhour Clients API Endpoint (for detailed client resource schema and operations)