Everhour icon

Everhour

Interact with Everhour API
Join our community

Actions32

Overview

This node integrates with the Everhour API to manage webhooks. Specifically, the Webhook - Create operation allows users to register a new webhook URL that will receive notifications for specified events occurring within Everhour. This is useful for automating workflows based on project, task, client, or time tracking changes.

Common scenarios include:

  • Automatically triggering downstream processes when a new client or project is created.
  • Receiving real-time updates about task changes or timer events.
  • Filtering webhook notifications to a specific project to reduce noise.

For example, you could create a webhook that listens for "Task Created" and "Timer Started" events for a particular project, enabling your system to react immediately when work begins on new tasks.

Properties

Name Meaning
Target URL The URL where Everhour will send webhook notifications (HTTP POST requests).
Events The list of event types to listen for. Multiple can be selected. Options include:
- Client Created, Client Updated
- Estimate Updated
- Project Created, Project Removed, Project Updated
- Section Created, Section Removed, Section Updated
- Task Created, Task Removed, Task Updated
- Time Updated
- Timer Started, Timer Stopped
Project ID Optional filter to restrict webhook events to a specific project by its ID.

Output

The node outputs the JSON response from the Everhour API after creating the webhook. This typically includes details such as the webhook's unique ID, target URL, subscribed events, and any other metadata returned by the API.

No binary data output is involved.

Example output JSON structure (simplified):

{
  "id": "12345",
  "targetUrl": "https://example.com/webhook",
  "events": [
    "api:task:created",
    "api:timer:started"
  ],
  "projectId": "abcde",
  "createdAt": "2024-01-01T12:00:00Z"
}

Dependencies

  • Requires an API key credential for authenticating with the Everhour API.
  • The node uses HTTP requests to communicate with Everhour's REST API endpoints.
  • No additional external dependencies beyond standard n8n credentials and HTTP request helpers.

Troubleshooting

  • Invalid or missing API credentials: Ensure the API key credential is correctly configured in n8n; otherwise, authentication errors will occur.
  • Invalid Target URL: The target URL must be a valid, reachable endpoint capable of receiving POST requests. Invalid URLs may cause webhook creation to fail.
  • Event selection required: At least one event must be selected; otherwise, the API may reject the webhook creation.
  • Project ID filtering: If provided, the project ID must exist in Everhour; otherwise, no events may be triggered or the API may return an error.
  • API rate limits or network issues: Temporary failures communicating with Everhour's API can cause errors; retry or check network connectivity.

Error messages from the API are passed through and should be reviewed to adjust parameters accordingly.

Links and References

Discussion