BCP CRM

Overview

This node interacts with the BCP CRM API to perform various operations on CRM resources such as Deals, Contacts, Companies, Leads, and Tickets. Specifically, for the Deal - Get operation, it retrieves detailed information about a single deal identified by its unique Deal ID.

Typical use cases include:

• Fetching detailed data of a specific deal to display or process further in an automation workflow.
• Integrating deal information from BCP CRM into other systems or reports.
• Triggering actions based on deal details retrieved dynamically during workflow execution.

Example: You have a workflow that triggers when a new deal is created elsewhere, and you want to fetch all details of that deal by its ID to enrich your database or send notifications.

Properties

Output

The output is a JSON array where each item corresponds to the deal data retrieved from the BCP CRM API. The structure of each JSON object matches the deal's data fields as returned by the API, including all available properties of the deal.

No binary data output is produced by this operation.

Example output snippet (simplified):

[
  {
    "id": "12345",
    "name": "Important Deal",
    "status": "Open",
    "amount": 10000,
    "pipeline": "Sales Pipeline A",
    ...
  }
]

Dependencies

• Requires an API key credential for authenticating with the BCP CRM API.
• The node uses HTTP requests to communicate with the BCP CRM REST endpoints.
• The base URL and API key must be configured in the node credentials before use.

Troubleshooting

• Missing or invalid Deal ID: If the Deal ID is not provided or incorrect, the API call will fail. Ensure the Deal ID is correct and exists in the CRM.
• Authentication errors: If the API key credential is missing or invalid, requests will be rejected. Verify the API key configuration.
• API endpoint errors: Network issues or changes in the BCP CRM API may cause failures. Check connectivity and API documentation for updates.
• Empty or unexpected response: If the deal does not exist or has been deleted, the response might be empty or contain error messages. Handle such cases gracefully in your workflow.

Links and References

• BCP CRM API Documentation (example link; replace with actual if available)
• n8n HTTP Request Node documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/