Everhour icon

Everhour

Interact with Everhour API
Join our community

Actions32

Overview

This node integrates with the Everhour API to manage clients and other related resources such as projects, tasks, time entries, users, and more. Specifically for the Client - Create operation, it allows you to create a new client in your Everhour account by providing the client's name and optional business details.

Common scenarios where this node is beneficial include automating client management workflows, syncing client data from other systems into Everhour, or programmatically adding clients as part of project setup processes.

Practical example:
You have a CRM system and want to automatically add new customers as clients in Everhour whenever they are created in your CRM. Using this node's Client Create operation, you can pass the customer name and business details to Everhour without manual entry.

Properties

Name Meaning
Client Name The name of the client to be created. This is a required field.
Business Details Optional additional information about the client's business.

Output

The output of the Client Create operation is a JSON object representing the newly created client as returned by the Everhour API. This typically includes fields such as the client's unique ID, name, business details, creation timestamps, and any other metadata provided by the API.

The node does not output binary data.

Example output structure (simplified):

{
  "id": 123,
  "name": "Client Name",
  "businessDetails": "Optional business details",
  "createdAt": "2024-01-01T12:00:00Z",
  ...
}

Dependencies

  • Requires an API key credential for authenticating requests to the Everhour API.
  • The node uses the base URL configured in the credential to send HTTP requests.
  • No additional external dependencies beyond the Everhour API and n8n's built-in HTTP request helpers.

Troubleshooting

  • Authentication errors: If the node fails due to authentication issues, verify that the API key credential is correctly configured and has sufficient permissions.
  • Validation errors: Missing required properties like "Client Name" will cause the API to reject the request. Ensure all required fields are provided.
  • API rate limits: Frequent calls may hit Everhour API rate limits; consider adding delays or handling retries.
  • Network issues: Connectivity problems between n8n and Everhour API will cause request failures; check network access and proxy settings if applicable.

Common error messages:

  • "401 Unauthorized" — Check API key validity.
  • "400 Bad Request" — Verify input parameters meet API requirements.
  • "404 Not Found" — Usually indicates incorrect endpoint or resource ID (not typical for create).
  • "429 Too Many Requests" — Rate limit exceeded; implement retry logic or reduce request frequency.

Links and References

Discussion