Plain Trigger
AI-generatedOverview
This node acts as a webhook trigger for events from the Plain.com platform. It listens for various event types related to threads, customers, messages, and notes within a Plain workspace. When one of the selected events occurs, Plain sends a webhook POST request to this node’s configured URL, triggering the workflow.
Common scenarios where this node is beneficial include:
- Automating responses or follow-up actions when new threads or customer records are created or updated.
- Tracking communication events such as emails, Slack messages, or Microsoft Teams messages sent or received on threads.
- Monitoring changes in thread status, priority, labels, or SLA status to update internal systems or notify teams.
- Reacting to note creation or customer group membership changes for CRM or support workflows.
Practical example: Automatically create a task in a project management tool whenever a new thread is created or a customer is updated in Plain.
Properties
| Name | Meaning |
|---|---|
| To trigger this workflow, add the Webook URL to your Plain.com workspace under Settings > Webhooks | A notice guiding users to configure the webhook URL in their Plain.com workspace settings to enable event delivery. |
| Events | The specific Plain.com events that will trigger this webhook. Multiple events can be selected. Options include thread lifecycle events (created, status changed, assignment, labels, priority, SLA), email and chat messages, notes, customer creation/update/deletion, and message events from Slack and Microsoft Teams. |
| Verify Signature | Boolean option to enable verification of the webhook payload signature for security purposes. |
| Signature Secret | The secret key used to verify the webhook signature. Required if "Verify Signature" is enabled. |
| Options > Path | The URL path segment for the webhook endpoint. Defaults to "webhook". |
Output
The node outputs JSON data representing the webhook event received from Plain.com. The structure includes:
eventType: The type of event triggered (e.g., "thread.thread_created").eventId: Unique identifier for the event.workspaceId: Identifier of the Plain workspace where the event originated.timestamp: When the event occurred.payload: The detailed event data payload sent by Plain.headers: HTTP headers received with the webhook request.
This output allows downstream nodes to access all relevant event information for further processing.
The node does not output binary data.
Dependencies
- Requires an active Plain.com workspace configured to send webhooks to the URL provided by this node.
- If signature verification is enabled, requires the user to provide the webhook signature secret from Plain.com settings.
- No external API calls or additional credentials are required beyond the webhook setup.
Troubleshooting
- Missing or incorrect webhook URL configuration: Ensure the webhook URL generated by this node is correctly added in the Plain.com workspace under Settings > Webhooks.
- Signature verification errors: If enabled, the node expects the
Plain-Request-Signatureheader and verifies it using the provided secret. Errors like "Missing Plain-Request-Signature header" or "Invalid webhook signature" indicate misconfiguration of the secret or that the webhook requests are tampered with. - No events triggering: Confirm that at least one event type is selected in the "Events" property and that Plain.com is sending those events.
- Webhook path mismatch: If you customize the webhook path, ensure the same path is configured in Plain.com.
Links and References
- Plain.com Webhooks Documentation (for setting up webhook URLs and obtaining signature secrets)
- n8n Webhook Trigger Nodes (general info about webhook triggers in n8n)