Actions11
Overview
The node integrates with the PerfexCRM API to add a reply message to an existing support ticket. This operation is useful in customer support workflows where automated or manual responses need to be appended to tickets for tracking communication history. For example, after processing a customer inquiry, you can use this node to programmatically add a follow-up message or internal note to the related ticket.
Properties
| Name | Meaning |
|---|---|
| Ticket ID | The unique identifier of the ticket to which the reply will be added. |
| Message | The content of the reply message to be added to the ticket. |
| Additional Fields | Optional extra information about the person replying, including: |
| - Name | Name of the person replying. |
| Email address of the person replying. |
Output
The node outputs the JSON response returned by the PerfexCRM API after adding the reply. This typically includes details of the newly created reply such as its ID, message content, timestamps, and possibly metadata about the author. The output is structured as a single JSON object representing the reply resource.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the PerfexCRM API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The base URL and API version are obtained from the credential configuration.
Troubleshooting
Common issues:
- Invalid or missing Ticket ID will cause the API request to fail.
- Missing or empty Message property will result in an error since the reply content is required.
- Authentication errors if the API key or token is invalid or expired.
- Network connectivity problems preventing access to the PerfexCRM API endpoint.
Error messages:
- "Ticket not found" indicates the provided Ticket ID does not exist.
- "Unauthorized" or "Authentication failed" means the API credentials are incorrect or missing.
- Validation errors if required fields are empty or malformed.
Resolutions:
- Verify the Ticket ID exists in the CRM before running the node.
- Ensure the Message field is populated with meaningful text.
- Check and update the API credentials in n8n settings.
- Confirm network access to the PerfexCRM API endpoint.
Links and References
- PerfexCRM API Documentation (general reference for API endpoints)
- n8n documentation on HTTP Request Node for understanding how API calls are made within nodes.