Actions73
- Repository Actions
- Issue Actions
- Pull Request Actions
- User Actions
- Organization Actions
- Release Actions
- Webhook Actions
- Branch Actions
- Commit Actions
- Tag Actions
Overview
This node interacts with the Forgejo API to perform various operations related to webhooks within a repository. Specifically, the 'Get' operation under the 'Webhook' resource retrieves detailed information about a specific webhook identified by its ID within a given repository owned by a specified user or organization. This is useful for scenarios where you need to programmatically access webhook configurations, verify webhook details, or audit webhook settings in your Forgejo repositories.
Use Case Examples
- Retrieve details of a webhook by specifying the repository owner, repository name, and webhook ID to monitor webhook configurations.
- Use the node to fetch webhook information as part of an automated workflow that manages repository integrations or notifications.
Properties
| Name | Meaning |
|---|---|
| Owner | The username or organization that owns the repository where the webhook is configured. |
| Repository | The name of the repository containing the webhook. |
| Webhook ID | The unique identifier of the webhook to retrieve. |
Output
JSON
json- The JSON object containing the webhook details returned from the Forgejo API.
Dependencies
- Requires an API key credential for Forgejo API authentication.
Troubleshooting
- Ensure the 'Owner', 'Repository', and 'Webhook ID' fields are correctly specified; incorrect values will result in API errors or no data returned.
- Verify that the API credentials have sufficient permissions to access webhook information in the specified repository.
- Common error messages may include 'Not Found' if the webhook ID does not exist or 'Unauthorized' if authentication fails. Check credentials and webhook existence to resolve these issues.