Everhour icon

Everhour

Interact with Everhour API
Join our community

Actions32

Overview

This node interacts with the Everhour API to manage webhooks among other resources. Specifically, for the Webhook - Get operation, it retrieves details of a single webhook by its ID. This is useful when you want to fetch configuration or status information about a specific webhook previously created in Everhour.

Practical scenarios include:

  • Verifying the settings of an existing webhook.
  • Fetching webhook details before updating or deleting it.
  • Auditing webhook configurations programmatically.

Properties

Name Meaning
Webhook ID The ID number of the webhook to retrieve

Output

The output is a JSON object representing the webhook's details as returned by the Everhour API. This typically includes fields such as the webhook's ID, target URL, subscribed events, and possibly metadata like creation date or status.

Example output structure (fields may vary):

{
  "id": 123,
  "targetUrl": "https://example.com/webhook",
  "events": [
    "api:client:created",
    "api:task:updated"
  ],
  "projectId": "optional-project-id",
  "createdAt": "2023-01-01T12:00:00Z",
  "active": true
}

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 from the configured credentials to make HTTP GET requests.
  • No additional external dependencies beyond standard HTTP request capabilities.

Troubleshooting

  • Common issues:

    • Invalid or missing webhook ID will cause the API to return an error.
    • Authentication failures if the API key credential is incorrect or expired.
    • Network connectivity problems preventing access to the Everhour API.

  • Error messages:

    • "404 Not Found": The specified webhook ID does not exist. Verify the ID is correct.
    • "401 Unauthorized": Authentication failed. Check that the API key credential is valid.
    • Timeout or network errors: Ensure your environment can reach the Everhour API endpoint.

  • To resolve errors, verify input parameters, ensure valid credentials, and check network connectivity.

Links and References

Discussion