Actions29
- Ticket Actions
- Company Actions
- Contact Actions
- Deal Actions
- Lead Actions
Overview
This node integrates with the BCP CRM API to manage deals within a CRM system. Specifically, the "Deal - Create" operation allows users to create new deal records by specifying various deal attributes such as name, expected value, associated company, pipeline, priority level, signing date, and deal type.
Common scenarios where this node is beneficial include automating sales workflows, integrating deal creation from external lead generation tools, or syncing deals from other platforms into BCP CRM. For example, when a new lead qualifies in a marketing automation tool, this node can automatically create a corresponding deal in BCP CRM with relevant details.
Properties
| Name | Meaning |
|---|---|
| Additional Fields | A collection of optional fields to specify additional deal details: |
| - Company Names or ID | Select one or more companies by name or ID to associate with the deal. |
| - Expected Value | Numeric field representing the expected monetary value of the deal. |
| - Name | The name/title of the deal. |
| - Pipeline Name or ID | Choose the sales pipeline the deal belongs to, by name or ID. |
| - Priority Level Name or ID | Set the priority level of the deal, selectable by name or ID. |
| - Signing Date | The date and time when the deal is expected to be signed. |
| - Type Name or ID | Specify the type/category of the deal, selectable by name or ID. |
The options for company, pipeline, priority level, and type are dynamically loaded from the CRM via API calls, allowing selection from existing CRM data or specification via expressions.
Output
The node outputs an array of JSON objects representing the created deal(s). Each object contains the data returned by the BCP CRM API for the newly created deal record, including any assigned IDs and fields set during creation.
If multiple deals are created in one execution, all are included in the output array.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the BCP CRM API using an API key credential.
- The node depends on the BCP CRM base URL and API key configured in the credentials.
- Dynamic option loading (e.g., companies, pipelines) requires network access to the CRM API endpoints.
Troubleshooting
- Missing Required Fields: If the "Name" field is not provided when creating a deal, the node will throw an error indicating that the field is required. Ensure mandatory fields are filled.
- API Authentication Errors: Invalid or missing API keys will cause authentication failures. Verify that the API key credential is correctly configured.
- Network Issues: Failure to reach the CRM API endpoints due to network problems will result in request errors. Check connectivity and endpoint URLs.
- Invalid Option Selections: Selecting non-existent IDs for company, pipeline, priority, or type may cause API errors. Use the dynamic dropdowns or valid expressions to avoid this.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if some fail, returning error details in the output.
Links and References
- BCP CRM API Documentation (example placeholder link)
- n8n Expressions Documentation
- n8n HTTP Request Helper