BCP CRM icon

BCP CRM

Interact with BCP CRM API

Actions29

Overview

This node allows updating a Deal record in the BCP CRM system via its API. It is useful for automating updates to deal information such as changing the deal name, expected value, pipeline stage, priority level, signing date, or type. For example, you can use this node to update deal details after receiving new information from sales teams or external systems, ensuring your CRM data stays current without manual entry.

Properties

Name Meaning
Deal ID Unique identifier of the deal to update.
Additional Fields Optional fields to update on the deal:
- Company Names or ID: Select one or more companies associated with the deal.
- Expected Value: Numeric expected value of the deal.
- Name: The name/title of the deal.
- Pipeline Name or ID: The pipeline stage the deal belongs to.
- Priority Level Name or ID: Priority level assigned to the deal.
- Signing Date: Date when the deal was signed.
- Type Name or ID: Type/category of the deal.

Output

The node outputs an array of JSON objects representing the updated deal(s) returned by the BCP CRM API. Each object contains the updated deal data as confirmed by the API response. The output does not include binary data.

Dependencies

  • Requires an API key credential for authenticating with the BCP CRM API.
  • The node makes HTTP requests to the BCP CRM base URL configured in the credentials.
  • No additional environment variables are required beyond the API key and base URL.

Troubleshooting

  • Missing Required Fields: If the "Deal ID" is not provided, the update will fail because the node needs it to identify which deal to update.
  • API Authentication Errors: Ensure the API key credential is valid and has permissions to update deals.
  • Invalid Field Values: Providing invalid IDs for pipeline, priority level, or type may cause errors. Use the node's load options to select valid values.
  • Network Issues: Connectivity problems to the BCP CRM API endpoint will cause request failures.
  • Error Messages: The node throws errors if required fields are missing or if the API returns an error status. Review the error message for details and verify input parameters.

Links and References

Discussion