Overview
This node acts as a webhook trigger for Nalpeiron Zentitle2 events. It listens for specific events from the Nalpeiron Zentitle2 service and triggers workflows when those events occur. This is useful for automating processes based on changes or actions in the Nalpeiron Zentitle2 system, such as customer creation, entitlement updates, or provisioning activities.
Common scenarios include:
- Automatically updating internal databases or CRMs when a new customer is created.
- Triggering notifications or follow-up tasks when entitlements are renewed or expired.
- Initiating provisioning workflows when an entitlement provision event occurs.
Properties
| Name | Meaning |
|---|---|
| Events | The specific Nalpeiron Zentitle2 events to listen for. Multiple events can be selected. Options include: Customer Created, Customer Updated, Entitlement Activated, Entitlement Created, Entitlement Expired, Entitlement Expires1day, Entitlement Expires7days, Entitlement Expires30days, Entitlement Maintenance Expired, Entitlement Maintenance Expires1day, Entitlement Maintenance Expires7days, Entitlement Maintenance Expires30days, Entitlement Provision, Entitlement Renewed, Entitlement Seat Activated, Entitlement Seat Deactivated, Entitlement Updated. |
Output
The node outputs JSON data representing the event payload received from the Nalpeiron Zentitle2 webhook. The output contains detailed information about the event that triggered the workflow, including event type and associated data.
If multiple events are subscribed to, the output will correspond to whichever event triggered the webhook.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Nalpeiron Zentitle2 API.
- The node internally manages webhook registration and deletion via the Nalpeiron Zentitle2 API.
- Requires proper configuration of the webhook URL in n8n to receive incoming HTTP POST requests from Nalpeiron Zentitle2.
Troubleshooting
- No events selected: If no events are selected in the "Events" property, the webhook subscription creation will fail with an error indicating that at least one event must be selected.
- Webhook registration failure: Errors during webhook creation or deletion usually relate to invalid credentials or network issues. Verify the API key credential and ensure the n8n instance is accessible externally if using webhooks.
- Event filtering: If the node receives events not selected in the properties, it will ignore them and respond with status 200 OK without triggering the workflow. Ensure correct event selection to avoid missed triggers.
- Missing webhook ID: If the webhook ID is missing in the workflow's static data, webhook deletion may silently fail. This typically happens if the webhook was never successfully created.
Links and References
- Nalpeiron Zentitle2 API Documentation (general reference for event types and webhook setup)
- n8n Webhook Trigger Documentation (for understanding webhook nodes in n8n)