Actions29
- Ticket Actions
- Company Actions
- Contact Actions
- Deal Actions
- Lead Actions
Overview
This node integrates with the BCP CRM API to perform various operations on CRM resources such as companies, contacts, deals, leads, and tickets. Specifically, for the Company resource with the Update operation, it updates an existing company's details in the CRM system.
Typical use cases include:
- Updating company information like address, country, domain, email, phone, tax code, or name after receiving new data from other systems.
- Synchronizing company records between different platforms by updating fields programmatically.
- Automating CRM data maintenance workflows where company details need regular updates.
For example, if a company changes its address or contact email, this node can be used to update those fields automatically in the BCP CRM.
Properties
| Name | Meaning |
|---|---|
| Company ID | Unique identifier of the company record to update. |
| Additional Fields | Collection of optional fields to update for the company: |
| - Address: The company's physical address. | |
| - Country: The company's country. | |
| - Domain: The company's internet domain. | |
| - Email: The company's email address. | |
| - Name: The company's name. | |
| - Phone: The company's phone number. | |
| - Tax Code: The company's tax identification code. |
Output
The node outputs JSON data representing the updated company record(s) returned from the BCP CRM API. The structure typically includes the updated fields and metadata about the company.
If multiple items are processed, the output is an array of updated company objects.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating requests to the BCP CRM API.
- The node expects the base URL and API key to be configured in the credentials.
- Network access to the BCP CRM API endpoints is necessary.
Troubleshooting
- Missing Required Fields: If required fields (like "Company ID" for update) are missing or empty, the node will throw an error. Ensure all mandatory inputs are provided.
- API Authentication Errors: Invalid or missing API keys will cause authentication failures. Verify that the API key credential is correctly set up.
- HTTP Request Failures: Network issues or incorrect base URLs can cause request failures. Check connectivity and credential configuration.
- Invalid Field Values: Providing invalid values for fields (e.g., malformed email) may result in API errors. Validate input data before running the node.
- Continue On Fail: If enabled, the node will continue processing remaining items even if some fail, returning error details in the output.
Links and References
- BCP CRM API Documentation (example placeholder, replace with actual link if available)
- n8n Documentation on Creating Custom Nodes
- General REST API usage guidelines for CRM integrations