Everhour icon

Everhour

Interact with Everhour API
Join our community

Actions32

Overview

This node integrates with the Everhour API to manage various resources such as clients, projects, tasks, time entries, users, teams, reports, webhooks, timecards, and assignments. Specifically for the Project - Create operation, it allows users to create a new project in Everhour by specifying the project's name and optionally associating it with a client via a client ID.

Common scenarios where this node is beneficial include automating project creation workflows, integrating project management with other systems, or bulk-creating projects based on external data sources.

Example use case: Automatically creating a new project in Everhour whenever a new sales opportunity is won in a CRM system, linking the project to the appropriate client.

Properties

Name Meaning
Project Name The name of the project to be created.
Client ID (Optional) The numeric ID of the client to associate the project with. Defaults to 0.

Output

The node outputs the JSON response returned by the Everhour API after creating the project. This typically includes details about the newly created project such as its unique ID, name, associated client ID, creation timestamps, and other metadata provided by Everhour.

The output structure is:

{
  "id": "string",
  "name": "string",
  "clientId": number,
  // ... other project-related fields returned by Everhour
}

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Everhour API.
  • The node uses the base URL from the configured credentials to send HTTP requests.
  • Proper permissions on the Everhour account are necessary to create projects.

Troubleshooting

  • Authentication errors: Ensure that the API key credential is correctly configured and has sufficient permissions.
  • Validation errors: The "Project Name" property is required; omitting it will cause the API to reject the request.
  • Client ID issues: If specifying a client ID, ensure it exists in Everhour; otherwise, the API may return an error.
  • API connectivity: Network issues or incorrect base URL configuration can cause request failures.

If the node throws an error related to HTTP status codes or API responses, check the error message for details and verify the input parameters and credentials.

Links and References

Discussion