AvantGuard - NinjaOne icon

AvantGuard - NinjaOne

AvantGuard - NinjaOne

Actions159

Overview

This node configures webhooks for receiving activity notifications from an external service. It allows users to specify a callback URL where the webhook payloads will be sent, filter which activities trigger the webhook, expand references in the payloads, and add custom HTTP headers such as authorization tokens.

Common scenarios include:

  • Setting up real-time notifications for specific events or activities in an external system.
  • Integrating with third-party services that support webhook callbacks.
  • Automating workflows triggered by external events without polling APIs.

For example, a user can configure a webhook to receive notifications only for certain activities, specify a secure callback URL, and include custom headers for authentication.

Properties

Name Meaning
Url The callback (webhook) URL where activity notifications will be sent.
Activities JSON object specifying filters to select which activities trigger the webhook notifications.
Expand JSON array defining which references should be expanded in the webhook payloads.
Headers JSON object containing custom HTTP headers to include in the webhook requests (e.g., Authorization).

Output

The node outputs JSON data representing the response from the webhook configuration API call. This typically includes confirmation details about the configured webhook, such as its ID, status, and any metadata returned by the external service.

No binary data output is involved.

Dependencies

  • Requires an API key credential for authenticating with the external service.
  • Needs the base URL of the external API configured in the node credentials.
  • Depends on the external service's webhook API endpoint to create or update webhook configurations.

Troubleshooting

  • Invalid URL errors: Ensure the callback URL is correctly formatted and publicly accessible.
  • Authentication failures: Verify that the API key or token used in credentials is valid and has permissions to manage webhooks.
  • Malformed JSON in Activities, Expand, or Headers: These fields expect valid JSON; invalid syntax will cause errors. Use proper JSON formatting.
  • Webhook not triggering: Confirm that the specified activities match actual events and that the external service supports those filters.
  • Custom headers ignored: Check that headers are correctly formatted as JSON objects and supported by the external API.

Links and References

Discussion