Actions11
Overview
This node integrates with the PerfexCRM API to create a new support ticket within the CRM system. It is useful for automating ticket creation workflows, such as when a customer submits a support request via a form or when an issue is detected in another system that requires tracking in PerfexCRM.
Typical use cases include:
- Automatically logging customer issues reported through external channels.
- Creating tickets from monitoring alerts or error reports.
- Integrating ticket creation into broader customer service automation pipelines.
For example, you could use this node to create a ticket with a subject and department, optionally specifying priority, status, assigned staff, and other details, directly from an incoming webhook or form submission.
Properties
| Name | Meaning |
|---|---|
| Subject | The subject or title of the ticket. |
| Department | The ID of the department to which the ticket belongs. |
| Additional Fields | Optional extra fields to specify more ticket details: |
| - Message | The main message or description of the ticket. |
| - Priority | The urgency level of the ticket. Options: Low (1), Medium (2), High (3), Urgent (4). |
| - Status | The current status of the ticket. Options: Open (1), In Progress (2), Answered (3), On Hold (4), Closed (5). |
| - Customer ID | The ID of the customer associated with the ticket. |
| - Contact ID | The ID of the contact person related to the ticket. |
| Email address associated with the ticket. | |
| - Name | Name associated with the ticket. |
| - Service | The ID of the service related to the ticket. |
| - Assigned | Staff ID to whom the ticket should be assigned. |
Output
The node outputs the JSON response returned by the PerfexCRM API after creating the ticket. This typically includes all details of the newly created ticket, such as its unique ID, timestamps, and any other metadata provided by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the PerfexCRM API using an API key credential configured in n8n.
- The node uses the base URL and API version specified in the credentials to construct requests.
- Network access to the PerfexCRM instance is necessary.
Troubleshooting
Common Issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing invalid department IDs or other required fields may result in API errors.
- Network connectivity problems can prevent successful API calls.
Error Messages:
- Authentication errors usually indicate incorrect or expired API keys; verify and update credentials.
- Validation errors from the API often mean required fields are missing or contain invalid values; ensure all mandatory properties like "Subject" and "Department" are correctly set.
- Rate limiting or server errors from the API should be retried after some delay.
Links and References
- PerfexCRM API Documentation (official API docs for reference on ticket creation endpoints)
- n8n Documentation (for general guidance on using credentials and HTTP request nodes)