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 resource with the Get operation, it retrieves detailed information about a single company identified by its unique ID.
Typical use cases include:
- Fetching detailed company data for display or processing in workflows.
- Integrating company information into other systems or automations.
- Using company details to enrich customer profiles or trigger conditional logic.
Example: Given a company ID, the node fetches all stored details about that company from BCP CRM, enabling further automation like sending targeted emails or updating records elsewhere.
Properties
| Name | Meaning |
|---|---|
| Company ID | Unique identifier for a particular company. This is required to specify which company to retrieve. |
Output
The node outputs JSON data representing the detailed information of the requested company. The structure corresponds to the company's fields as stored in BCP CRM, typically including identifiers, names, contact info, and any custom fields defined in the CRM.
If multiple companies were returned (not typical for Get operation), they would be output as an array of 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 makes HTTP requests to the BCP CRM base URL configured in the credentials.
- Proper network access to the BCP CRM API endpoints is necessary.
Troubleshooting
- Missing or invalid Company ID: The node requires a valid company ID; if omitted or incorrect, the API will likely return an error or empty response.
- Authentication errors: Ensure the API key credential is correctly set up and has sufficient permissions.
- API endpoint issues: Network problems or changes in the BCP CRM API may cause request failures.
- Error messages: If the node throws errors related to HTTP requests or responses, verify the input parameters and credentials. Enabling "Continue On Fail" can help handle individual item errors gracefully.
Links and References
- BCP CRM API Documentation (example placeholder, replace with actual)
- n8n documentation on HTTP Request Node for understanding underlying HTTP calls
- General n8n node development guide: https://docs.n8n.io/integrations/creating-nodes/