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 Leads, Contacts, Companies, Deals, and Tickets. Specifically for the Lead - Get operation, it retrieves detailed information about a single lead identified by its unique Lead ID.
Typical use cases include:
- Fetching detailed data of a specific lead to enrich workflows or trigger follow-up actions.
- Integrating lead data into other systems or automations.
- Validating lead information before processing or updating records.
For example, you might use this node to get a lead’s contact details and status before sending a personalized email campaign or assigning the lead to a sales representative.
Properties
| Name | Meaning |
|---|---|
| Lead ID | Unique identifier for a particular lead. This is required to specify which lead to fetch. |
Output
The node outputs JSON data representing the detailed information of the requested lead. The structure corresponds to the lead record as stored in the BCP CRM system, including all fields and metadata associated with that lead.
If multiple leads were returned (though for "Get" operation typically only one), 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 with the BCP CRM API.
- The node makes HTTP requests to the BCP CRM REST API endpoints.
- Proper configuration of the API base URL and API key in the credentials is necessary.
Troubleshooting
- Missing or invalid Lead ID: The node requires a valid Lead ID to retrieve data. 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 errors: Network issues or changes in the BCP CRM API could cause failures. Check connectivity and API documentation if errors occur.
- Error messages from the node: Errors thrown during execution will contain messages from the API or internal validation, e.g., "Lead not found" or "Unauthorized". Use these messages to verify input parameters and credentials.
Links and References
- BCP CRM API Documentation (example placeholder, replace with actual link if available)
- n8n Documentation: Creating Custom Nodes
- General REST API usage in n8n: HTTP Request Node