Attio icon

Attio

Interact with Attio API

Overview

This node allows you to update an existing webhook in the Attio system by specifying its unique identifier and providing new configuration data. It is useful when you want to modify the target URL or change event subscriptions for a webhook without creating a new one. For example, you might update a webhook to point to a different endpoint or adjust which events it listens to, such as subscribing only to "note.created" events with specific filters.

Properties

Name Meaning
Webhook Id A UUID string that uniquely identifies the webhook you want to update.
Data JSON object containing the updated webhook configuration. This includes:
- target_url: The new URL where webhook events will be sent.
- subscriptions: An array of event subscription objects, each specifying:
- event_type: The type of event to subscribe to (e.g., "note.created").
- filter: Optional filter criteria to limit which events trigger the webhook.

Output

The node outputs the JSON response returned by the Attio API after updating the webhook. This typically contains the updated webhook details, confirming the changes made. The output is structured as:

{
  "id": "string",
  "target_url": "string",
  "subscriptions": [
    {
      "event_type": "string",
      "filter": { /* filter object */ }
    }
  ],
  // ... other webhook properties
}

No binary data is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the Attio API.
  • The node makes HTTP PATCH requests to the Attio API endpoint /v2/webhooks/{webhook_id}.
  • Ensure the API key has permissions to update webhooks.
  • No additional environment variables are required beyond the API authentication setup.

Troubleshooting

  • Invalid Webhook Id: If the provided webhook ID is not a valid UUID or does not exist, the API will return an error. Verify the webhook ID is correct.
  • Malformed JSON in Data: The Data property must be valid JSON. Parsing errors will cause the node to fail. Use proper JSON formatting.
  • Insufficient Permissions: If the API key lacks permission to update webhooks, the request will be denied. Check API key scopes.
  • Network Issues: Connectivity problems can cause request failures. Ensure network access to the Attio API.
  • API Errors: The node surfaces API error messages. Review the message for clues, such as invalid fields or rate limits.

Links and References

Discussion