Overview
The Opencell Trigger node is designed to handle events from the Opencell platform via webhooks. It allows you to listen for specific events (such as entity creation, updates, deletions, and other business-related triggers) on a wide range of Opencell entities (like Subscriptions, Invoices, Customers, etc.). When an event occurs in Opencell that matches your configuration, this node will trigger your n8n workflow and provide the event data.
Common scenarios:
- Automating downstream processes when a new customer or subscription is created in Opencell.
- Reacting to payment status changes, invoice generation, or low balance alerts.
- Integrating Opencell with other systems by forwarding event data to CRMs, ERPs, or notification services.
Practical examples:
- Send a welcome email when a new customer is created.
- Notify finance teams when an invoice is generated or paid.
- Update external analytics dashboards when a subscription is terminated.
Properties
| Name | Type | Meaning |
|---|---|---|
| Authentication | options | Selects the authentication method for connecting to Opencell (Basic Authentication or OAuth2). |
| Entity | options | Specifies the type of Opencell entity to monitor for events (e.g., Subscription, Invoice). |
| Event | options | Chooses the event type to trigger the workflow (e.g., Created, Updated, Terminated, etc.). |
Output
The node outputs the body of the incoming webhook request from Opencell as JSON. The structure of this output depends on the event and entity configured in Opencell, but typically includes fields such as:
{
"id": "...",
"code": "...",
// ...other event-specific fields
}
- The output is always a JSON object containing the event payload sent by Opencell.
- No binary data is produced by this node.
Dependencies
- External Service: Requires access to an Opencell instance with API/webhook capabilities enabled.
- Authentication: Needs valid credentials for either Basic Authentication or OAuth2, configured in n8n.
- n8n Configuration: The node must be accessible from Opencell (publicly reachable URL if running outside local network).
Troubleshooting
Common issues:
- Webhook not triggering: Ensure that the n8n instance is accessible from Opencell and the webhook URL is correctly registered.
- Authentication errors: Double-check the provided credentials and authentication method.
- Event not received: Verify that the correct entity and event type are selected, and that corresponding events are actually occurring in Opencell.
Error messages:
"ERROR CREATING A WEBHOOK": Indicates failure during webhook registration in Opencell. Check Opencell API connectivity, permissions, and input parameters.- No data received: If the output is empty, confirm that Opencell is sending the expected payload and that the webhook is active.