Actions11
Overview
This node acts as an integration point for a chatbot platform, enabling various interactions such as sending messages, retrieving leads and conversations, managing chatbots, and handling webhook triggers. Specifically, the Trigger resource with the On Lead Submission operation listens for new lead submissions from a selected chatbot via a webhook.
Common scenarios include:
- Automatically processing new leads submitted through a chatbot to trigger follow-up workflows.
- Integrating chatbot lead data into CRM or marketing automation systems.
- Debugging webhook events related to lead submissions.
For example, when a user submits their contact information through a chatbot, this node can capture that event in real-time and start a workflow to notify sales teams or update databases.
Properties
| Name | Meaning |
|---|---|
| Chatbot Name or ID | Select a chatbot from the list or specify its ID dynamically. This identifies which chatbot's lead submissions to listen for. |
| Webhook | Hidden property representing the webhook identifier used internally (default). |
| Options | Collection of optional settings: |
| Enable Webhook Debug | Boolean flag to enable additional logging for webhook debugging purposes. |
Output
The node outputs JSON data representing the webhook payload received from the chatbot platform when a lead is submitted. The structure mirrors the lead submission data sent by the chatbot, typically including lead details such as contact info, message content, timestamps, and any custom fields.
No binary data output is involved.
Example output JSON structure (simplified):
{
"leadId": "string",
"name": "string",
"email": "string",
"phone": "string",
"submittedAt": "timestamp",
"additionalData": { /* other lead-related fields */ }
}
Dependencies
- Requires an API key credential for authenticating with the chatbot platform's API.
- Needs the base URL of the chatbot API configured in credentials.
- The node registers and manages webhooks on the chatbot platform to receive lead submission events.
- n8n workflow must be accessible via a public URL to receive webhook calls.
Troubleshooting
- Webhook registration failure: If the webhook cannot be registered, check that the API key and base URL are correctly configured and that the chatbot ID is valid.
- Invalid response format: Errors may occur if the chatbot API returns unexpected data; ensure the chatbot platform is operational and the API version matches expectations.
- Missing base URL in credentials: The node throws an error if the base URL is not set in the credentials.
- Webhook debug logs: Enable the "Enable Webhook Debug" option to get more detailed logs for troubleshooting webhook issues.
- JSON parsing errors: Incoming webhook data must be valid JSON; malformed payloads will cause errors.
Links and References
- n8n Expressions Documentation
- Chatbot platform API documentation (refer to your chatbot provider's official docs for webhook setup and lead submission event details)