BCP CRM icon

BCP CRM

Interact with BCP CRM API

Actions29

Overview

This node integrates with the BCP CRM API to update existing tickets within the CRM system. It allows users to modify ticket details such as type, linked resource, priority, handlers, and other metadata. This is useful in scenarios where ticket information needs to be kept current, for example, updating the status or details of a customer support ticket after receiving new information.

Practical examples include:

  • Updating the priority or description of a support ticket based on customer feedback.
  • Changing the assigned handlers or related contacts for a ticket.
  • Linking a ticket to a different company, contact, deal, or lead as relationships evolve.

Properties

Name Meaning
Ticket ID Unique identifier for the ticket to update.
Type Name or ID The ticket type, selectable from a list or specified by an expression.
Linked Resource The type of resource linked to the ticket; options are Company, Contact, Deal, or Lead.
Linked ID Unique identifier of the linked resource (company, contact, deal, or lead).
Additional Fields A collection of optional fields to update on the ticket:
- Description Text description of the ticket.
- Expires At Date/time when the ticket expires.
- Handler Names or IDs One or more users assigned as handlers of the ticket.
- Name Name/title of the ticket.
- Priority Priority level of the ticket; options are Low, Medium, High.
- Relate Names or IDs One or more users related to the ticket.

Output

The node outputs JSON data representing the updated ticket(s) returned from the BCP CRM API. The structure corresponds to the CRM's ticket object, including all updated fields. If multiple tickets are processed, the output is an array of ticket objects.

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 updates.
  • Proper configuration of the API base URL and API key in the credentials is necessary.

Troubleshooting

  • Missing Required Fields: When updating a ticket, ensure that required fields like "Ticket ID", "Type Name or ID", "Linked Resource", and "Linked ID" are provided. Missing these will cause errors.
  • Invalid IDs: Providing invalid or non-existent ticket IDs or linked resource IDs will result in API errors.
  • API Authentication Errors: Incorrect or expired API keys will cause authentication failures. Verify the API key credential.
  • Network Issues: Connectivity problems can cause request failures. Check network access to the BCP CRM API endpoint.
  • Permission Issues: The API key must have sufficient permissions to update tickets; otherwise, the operation will fail.

Common error messages typically come from the API response and may indicate missing parameters, invalid IDs, or authorization failures. Review the error message details and verify input parameters and credentials accordingly.

Links and References

Discussion