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 manage webhooks within repositories. Specifically, the 'List' operation under the 'Webhook' resource retrieves a list of webhooks configured for a specified repository owned by a user or organization. It supports pagination options to control the number of results per page and the starting page, making it useful for managing and auditing webhooks in software development workflows.
Use Case Examples
- Listing all webhooks for a repository to audit active integrations.
- Fetching webhooks to monitor or update their configurations programmatically.
Properties
| Name | Meaning |
|---|---|
| Owner | The username or organization name that owns the repository for which webhooks are being listed. |
| Additional Options | Optional parameters to control pagination of the webhook list, including 'Page' to specify the starting page number and 'Limit' to specify the maximum number of results per page. |
Output
JSON
json- An array of webhook objects returned from the Forgejo API, each representing a webhook configured in the specified repository.
Dependencies
- Requires an API key credential for Forgejo API authentication, including the server URL.
Troubleshooting
- Common issues include authentication failures due to invalid or missing API credentials. Ensure the Forgejo API credentials are correctly configured.
- Pagination parameters might be ignored if automatic pagination is enabled, leading to retrieval of all pages regardless of 'Page' and 'Limit' settings.
- API rate limits or permission issues on the repository may cause errors when listing webhooks. Verify API access rights and rate limits.
Links
- Forgejo API Documentation - Official documentation for the Forgejo API, including webhook management endpoints.