BCP CRM icon

BCP CRM

Interact with BCP CRM API

Actions29

Overview

This node integrates with the BCP CRM API to manage CRM data such as companies, contacts, deals, leads, and tickets. Specifically, for the Deal resource with the Delete operation, it deletes a deal record identified by its ID from the CRM system.

Common scenarios where this node is useful include:

  • Automating cleanup of outdated or invalid deals in your CRM.
  • Integrating with other workflows that require removing deals after certain conditions are met (e.g., deal lost, duplicate entries).
  • Synchronizing deal deletions between BCP CRM and other systems.

Example: Automatically delete a deal when it is marked as "Cancelled" in another system, ensuring your CRM stays up-to-date without manual intervention.

Properties

Name Meaning
Deal ID The unique identifier of the deal to delete

Output

The output is a JSON array containing the response data from the BCP CRM API after attempting to delete the specified deal(s). The structure typically includes confirmation of deletion or details about the deleted deal. If multiple deals are processed, the output will contain an array of such responses.

No binary data 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 execution.

Troubleshooting

  • Missing Deal ID: The "Deal ID" property is required. Omitting it will cause the node to fail.
  • Invalid Deal ID: Providing an incorrect or non-existent deal ID may result in an error or no deletion occurring.
  • API Authentication Errors: Ensure the API key credential is valid and has sufficient permissions to delete deals.
  • Network Issues: Connectivity problems with the BCP CRM API endpoint can cause request failures.
  • Error Handling: If the node is set to continue on failure, errors will be returned in the output JSON under an error field; otherwise, the workflow will stop on error.

Links and References

Discussion