BCP CRM icon

BCP CRM

Interact with BCP CRM API

Overview

This node integrates with the BCP CRM API to manage tickets and other CRM resources. Specifically, the Delete Ticket operation allows users to delete a ticket by its ID from the BCP CRM system. This is useful in scenarios where tickets are no longer relevant or were created by mistake and need to be removed to keep the CRM data clean.

Practical examples include:

  • Automatically deleting resolved or canceled support tickets.
  • Cleaning up test tickets created during development or QA.
  • Removing duplicate tickets identified during data audits.

Properties

Name Meaning
Ticket ID The unique identifier of the ticket to delete

Output

The output is a JSON array containing the response data from the BCP CRM API after attempting to delete the specified ticket(s). The structure depends on the API's response but generally includes confirmation of deletion or details about the deleted ticket.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the BCP CRM API.
  • The node makes HTTP requests to the BCP CRM endpoints using the base URL and API key provided in the credentials.
  • Proper configuration of the API key credential in n8n is necessary for successful operation.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Ticket ID will likely result in an error or no action.
    • Missing or incorrect API key credential configuration will cause authentication failures.
    • Network connectivity issues can prevent communication with the BCP CRM API.
  • Error messages:

    • Errors returned from the API (e.g., "Ticket not found") will be thrown unless the node is set to continue on fail, in which case the error message will be included in the output JSON.
    • Authentication errors due to invalid API keys typically manifest as HTTP 401 or 403 responses.
  • Resolutions:

    • Verify that the Ticket ID exists in the BCP CRM system before attempting deletion.
    • Ensure the API key credential is correctly configured and has sufficient permissions.
    • Check network connectivity and firewall settings to allow outbound requests to the BCP CRM API.

Links and References

Discussion