Nifty icon

Nifty

Interact with Nifty project management API

Actions10

Webhook → Create

AI-generated

Overview

This node creates a webhook in the Nifty project management system. It allows users to specify a target URL where webhook events will be sent, select which events will trigger the webhook, and optionally provide additional details such as a description and whether the webhook is active. This node is useful for automating workflows by receiving real-time notifications about changes in tasks, projects, comments, or milestones in Nifty.

Use Case Examples

  1. Automatically notify a team chat when a task is created or updated.
  2. Trigger an external system to update its records when a project is archived.
  3. Send alerts to a monitoring service when comments or milestones are created.

Properties

Name Meaning
Target URL The URL to send webhook events to.
Events The events that will trigger this webhook, such as task creation, updates, completion, deletion, project changes, comments, and milestones.
Additional Fields Optional fields including a description for the webhook and whether it is active.
Request Options Settings for the HTTP request such as batching, SSL certificate validation, proxy configuration, and timeout.

Output

JSON

  • id - The unique identifier of the created webhook.
  • target_url - The URL where webhook events will be sent.
  • events - The list of events that trigger the webhook.
  • description - The description of the webhook, if provided.
  • is_active - Indicates whether the webhook is active.

Dependencies

  • Nifty project management API
  • An API key or OAuth2 token for authentication

Troubleshooting

  • Ensure the target URL is reachable and correctly configured to receive POST requests.
  • Verify that the selected events are valid and supported by the Nifty API.
  • Check that the API credentials are correct and have permissions to create webhooks.
  • If SSL issues occur, consider enabling the option to ignore SSL certificate validation, but be aware of security risks.
  • Proxy settings must be correctly configured if used, including authentication details if required.
  • Timeout settings should be adjusted based on network conditions to avoid premature request termination.

Links

Discussion