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 Company, Contact, Deal, Lead, and Ticket. Specifically, for the Company - Delete operation, it deletes a company record identified by its unique ID from the CRM system.
Common scenarios where this node is beneficial include:
- Automating cleanup of outdated or incorrect company records.
- Integrating with other systems to remove companies when they are deleted elsewhere.
- Managing CRM data lifecycle programmatically within workflows.
Example use case:
- A workflow that triggers when a company is marked as inactive in another system and then uses this node to delete the corresponding company record in BCP CRM.
Properties
| Name | Meaning |
|---|---|
| Company ID | The unique identifier (ID) of the company to delete |
Output
The node outputs JSON data representing the response from the BCP CRM API after attempting to delete the company. This typically includes confirmation of deletion or details about the deleted entity. The output structure mirrors the API's response and may be an object or an array of objects depending on the API behavior.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with 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 endpoint is necessary.
Troubleshooting
- Missing Company ID: If the "Company ID" property is empty or invalid, the API call will fail. Ensure the correct ID is provided.
- API Authentication Errors: If the API key is missing, invalid, or expired, requests will be rejected. Verify the API key credential configuration.
- HTTP Errors: Network issues or incorrect API endpoints can cause failures. Check connectivity and credential base URL.
- Error Handling: If the node is set to continue on failure, errors will be returned in the output JSON under an
errorfield; otherwise, execution stops with an error.
Links and References
- BCP CRM API Documentation (example link, replace with actual if available)
- n8n Documentation on Creating Custom Nodes