Actions29
- Ticket Actions
- Company Actions
- Contact Actions
- Deal Actions
- Lead Actions
Overview
This node integrates with the BCP CRM API to manage tickets within the CRM system. Specifically, the "Ticket - Create" operation allows users to create new support or service tickets linked to various CRM resources such as companies, contacts, deals, or leads.
Common scenarios where this node is beneficial include:
- Automatically creating support tickets when a customer submits a request via a web form.
- Logging internal tasks or issues related to specific CRM entities for tracking and resolution.
- Integrating ticket creation into automated workflows that respond to business events.
For example, when a new lead is qualified, an automated workflow can create a ticket assigned to the support team to follow up on the lead's inquiry.
Properties
| Name | Meaning |
|---|---|
| Type Name or ID | The type of ticket to create. Choose from predefined ticket types loaded dynamically from the API. |
| Linked Resource | The CRM resource to which the ticket will be linked. Options: Company, Contact, Deal, Lead. |
| Linked ID | Unique identifier of the linked resource (company, contact, deal, or lead). |
| Additional Fields | Optional extra fields for the ticket: |
| - Description | Detailed description of the ticket. |
| - Expires At | Date and time when the ticket expires. |
| - Handler Names or IDs | Users responsible for handling the ticket. Select multiple from a list or specify IDs. |
| - Name | Name/title of the ticket. Required for ticket creation. |
| - Priority | Priority level of the ticket. Options: Low, Medium, High. |
| - Relate Names or IDs | Related users associated with the ticket. Select multiple from a list or specify IDs. |
Output
The node outputs JSON data representing the created ticket(s) as returned by the BCP CRM API. The structure typically includes all ticket details such as its ID, name, type, linked resource information, priority, handlers, and other metadata.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the BCP CRM API.
- The node makes HTTP requests to the BCP CRM endpoints to perform operations.
- Proper configuration of the base URL and API key in the credentials is necessary.
Troubleshooting
- Missing Required Fields: If the "Name" field is not provided when creating a ticket, the node throws an error indicating it is required. Ensure all mandatory fields are filled.
- Invalid Linked Resource or ID: Providing an incorrect linked resource type or invalid linked ID may cause API errors. Verify these values correspond to existing CRM records.
- API Authentication Errors: If the API key is invalid or missing, requests will fail. Confirm the API key credential is correctly set up.
- Network Issues: Connectivity problems to the BCP CRM API endpoint will result in request failures. Check network access and endpoint availability.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if some fail, returning error details in the output.
Links and References
- BCP CRM API Documentation
- n8n Expressions Documentation
- n8n HTTP Request Node (for understanding underlying HTTP calls)