Gitea icon

Gitea

Interact with Gitea via API
Join our community

Actions393

Overview

This node interacts with the Gitea API to retrieve information about a specific webhook configured for an organization. The "Org Get Hook" operation fetches details of a particular hook by its ID within a given organization. This is useful for monitoring, auditing, or managing webhooks that trigger actions based on repository or organization events.

Practical examples include:

  • Retrieving the configuration of a webhook to verify its URL and events it listens to.
  • Checking the status or metadata of a webhook before updating or deleting it.
  • Integrating with automation workflows that depend on webhook configurations.

Properties

Name Meaning
Org The name of the organization in which the webhook exists. This identifies the scope for the hook retrieval.
Id The numeric identifier of the webhook to retrieve. This specifies which hook's details to fetch.

Output

The node outputs JSON data representing the webhook's details as returned by the Gitea API. This typically includes fields such as the hook's ID, URL, content type, secret (if any), events it listens to, active status, and timestamps related to creation or updates.

If the webhook contains binary data (e.g., certificates or secrets), it would be included in the output accordingly, but this node primarily deals with JSON metadata.

Dependencies

  • Requires an API key credential for authenticating with the Gitea instance.
  • Needs the base URL of the Gitea server configured in the credentials.
  • Depends on the Gitea REST API being accessible and the user having permission to read organization hooks.

Troubleshooting

  • Common issues:

    • Invalid organization name or hook ID will result in errors or empty responses.
    • Insufficient permissions may cause authorization errors.
    • Network connectivity problems can prevent API calls from succeeding.

  • Error messages:

    • 404 Not Found: The specified organization or hook ID does not exist. Verify the inputs.
    • 401 Unauthorized: Authentication failed. Check the API key and credentials.
    • 400 Bad Request: Input parameters are invalid or missing. Ensure "Org" and "Id" are correctly set.

Resolving these usually involves verifying input values, checking API credentials, and ensuring network access to the Gitea server.

Links and References

Discussion