Overview
This node acts as a trigger for workflows based on events occurring in the PerfexCRM system. It listens to various predefined events such as creation, update, or deletion of customers, contacts, leads, invoices, proposals, contracts, projects, tasks, tickets, staff activities, and expenses. When one of the selected events happens in PerfexCRM, the node activates the workflow, passing along the event data.
This node is beneficial for automating business processes that depend on CRM changes. For example:
- Automatically sending welcome emails when a new customer is created.
- Notifying sales teams when a lead is converted.
- Updating accounting systems when an invoice is paid.
- Triggering follow-ups when a contract is about to expire.
Properties
| Name | Meaning |
|---|---|
| Events | The specific PerfexCRM events to listen for. Multiple events can be selected. Options include customer, contact, lead, invoice, payment, proposal, estimate, contract, project, task, ticket, staff, and expense related events. |
| Secret | An optional secret string used to verify the webhook signature for security purposes. If set, incoming webhook requests must include a valid signature matching this secret. |
Output
The node outputs JSON data representing the event payload received from PerfexCRM when the webhook is triggered. This includes all relevant details about the event, such as the entity affected (e.g., customer, invoice), its properties, and metadata.
Additionally, HTTP headers from the webhook request are also provided alongside the JSON data, which can be useful for debugging or verifying the webhook source.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential to authenticate with the PerfexCRM API.
- Needs network access to receive webhook POST requests from PerfexCRM.
- Optional: If using the secret property, the node verifies webhook signatures using HMAC SHA256 hashing.
Troubleshooting
- Webhook not triggering: Ensure the webhook URL is correctly registered in PerfexCRM and that the selected events match those sent by PerfexCRM.
- Signature verification failed: If a secret is set, incoming webhook requests must include a matching
x-webhook-signatureheader. Check that the secret matches between n8n and PerfexCRM. - API errors during webhook registration: Verify that the API credentials are correct and have sufficient permissions to create and delete webhooks.
- Missing or empty event data: Confirm that the webhook payloads from PerfexCRM contain data and that the node’s event filters include the triggered event type.
Links and References
- PerfexCRM Official Website
- PerfexCRM API Documentation (for webhook event details)
- n8n Webhook Node Documentation (general webhook usage)