BCP CRM icon

BCP CRM

Interact with BCP CRM API

Actions29

Overview

This node integrates with the BCP CRM API to manage CRM data programmatically. Specifically, for the Contact resource and the Delete operation, it deletes a contact record identified by its unique ID from the CRM system.

Typical use cases include automating cleanup of outdated or incorrect contact records, integrating CRM contact deletion into workflows triggered by external events, or bulk deleting contacts based on certain criteria.

For example, you might use this node in a workflow that removes contacts who have unsubscribed from your mailing list or who no longer meet your customer criteria.

Properties

Name Meaning
Contact ID The unique identifier (ID) of the contact to delete

Output

The node outputs JSON data representing the response from the BCP CRM API after attempting to delete the contact. This typically includes confirmation of deletion or details about the deleted contact. The output is an array of JSON objects if multiple items are returned.

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 REST endpoints.
  • The base URL and API key must be configured in the node credentials before execution.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Contact ID will likely result in an error or no deletion.
    • Missing or incorrect API key credential configuration will cause authentication failures.
    • Network connectivity issues can prevent successful API calls.

  • Error messages:

    • Errors thrown by the node will include messages from the API response or internal request errors.
    • If the "Contact ID" property is empty or missing, the node may throw an error indicating the required field is not set.

  • Resolutions:

    • Verify the Contact ID exists in the CRM before attempting deletion.
    • Ensure the API key credential is correctly set up and has sufficient permissions.
    • Check network access and endpoint availability.

Links and References

Discussion