Overview

This node operation creates a new webhook for a specified repository in Forgejo. It allows users to specify the repository owner, repository name, the URL to which webhook payloads will be sent, the events that trigger the webhook, and whether the webhook is active. This is useful for automating workflows that depend on repository events, such as CI/CD pipelines, notifications, or integrations with other services.

Use Case Examples

1. Create a webhook to trigger on push events for a repository to notify a CI/CD system.
2. Set up a webhook to listen for issue comments and trigger a bot to respond automatically.

Properties

Output

JSON

• json
  • id - The unique identifier of the created webhook.
  • type - The type of the webhook, typically 'forgejo'.
  • config
    * url - The URL configured for the webhook to send payloads.
  • events - The list of events that trigger the webhook.
  • active - Indicates if the webhook is active.

Dependencies

• Requires an API key credential for Forgejo API authentication.

Troubleshooting

• Ensure the 'owner' and 'repository' parameters are correctly specified and exist in Forgejo.
• Verify the 'webhookUrl' is a valid and reachable URL to receive webhook payloads.
• Check that the API key credential has sufficient permissions to create webhooks on the repository.
• Common errors include authentication failures, invalid repository names, or insufficient permissions. Verify credentials and repository access rights.

Links

• Forgejo API Documentation - Official API documentation for Forgejo, useful for understanding webhook creation and other API endpoints.