AttioInstall

Overview

This node operation allows users to create a webhook in the external service's system. A webhook is a way for an application to provide other applications with real-time information by sending HTTP callbacks when certain events occur. This node is useful when you want to automate workflows triggered by specific events, such as the creation of notes or other activities tracked by the service.

For example, you can configure this node to create a webhook that listens for new notes being created (note.created event) and sends the data to your specified URL. This enables real-time synchronization or triggering downstream processes whenever relevant events happen.

Properties

The Data property expects a JSON structure similar to:

{
  "target_url": "https://example.com/webhook",
  "subscriptions": [
    {
      "event_type": "note.created",
      "filter": {
        "$or": [{}]
      }
    }
  ]
}

This JSON defines the webhook target and the events it subscribes to.

Output

The node outputs the response from the API call to create the webhook. The output is structured as JSON containing details about the newly created webhook, such as its ID, target URL, subscriptions, and status.

The output JSON can be used in subsequent workflow steps to reference the webhook or confirm its creation.

No binary data output is involved in this operation.

Dependencies

• Requires an API authentication token (API key or OAuth token) configured in n8n credentials to authorize requests to the external service.
• The node makes HTTPS requests to the service's API endpoint to create webhooks.
• No additional environment variables are required beyond standard credential setup.

Troubleshooting

• Invalid JSON in Data Property: Since the data property expects valid JSON, malformed JSON input will cause errors. Ensure the JSON is correctly formatted.
• Authorization Errors: If the API token is missing, expired, or invalid, the request to create the webhook will fail with authorization errors. Verify the API credentials are correct and have sufficient permissions.
• Invalid Target URL: The target_url must be a valid, reachable URL. If the URL is incorrect or unreachable, webhook delivery will fail after creation.
• Subscription Event Types: Using unsupported or misspelled event types in the subscriptions array will cause the API to reject the webhook creation. Confirm event types against the service documentation.
• API Rate Limits: Excessive webhook creation requests may hit rate limits imposed by the service, resulting in errors. Implement retry logic or limit frequency accordingly.

Links and References

• Webhook Concepts
• Refer to the external service's official API documentation for detailed webhook creation parameters and supported event types.