Crm

Perform actions in BimeBazar CRM

Actions6

Overview

This node integrates with the BimeBazar CRM system to perform various lead and customer management operations. Specifically, the "Change Lead Segment" operation allows users to update the segment classification of a lead within the CRM. This is useful for marketing, sales, or customer service teams who want to dynamically reclassify leads based on new information or campaign targeting.

Common scenarios include:

Automatically moving leads to a different segment after a certain action or event.
Organizing leads into segments for targeted communication.
Updating lead segments as part of a larger workflow that manages lead lifecycle.

Example: After a lead completes a product demo, this node can be used to move the lead from a "New" segment to a "Qualified" segment automatically.

Properties

Name	Meaning
Lead ID	The unique numeric identifier of the lead to update. Required.
Segment ID	The unique numeric identifier of the new segment to assign to the lead. Required.

Output

The node outputs a JSON object for each input item processed with the following structure:

{
  "success": true,
  "operation": "changeLeadSegment",
  "leadId": <number>,
  "segmentId": <number>,
  "response": <object>
}

success: Indicates if the operation was successful.
operation: The name of the operation performed ("changeLeadSegment").
leadId: The ID of the lead that was updated.
segmentId: The new segment ID assigned to the lead.
response: The raw response object returned by the CRM API for this request.

No binary data is output by this operation.

Dependencies

Requires an API key credential for authenticating with the BimeBazar CRM API.
The node makes HTTP POST requests to the CRM's REST API endpoints.
The base URL and API token must be configured in the node credentials.
The user must have appropriate permissions in the CRM to update lead segments.

Troubleshooting

Common issues:
- Invalid or missing Lead ID or Segment ID will cause the API call to fail.
- Incorrect or expired API token will result in authentication errors.
- Network connectivity problems may prevent reaching the CRM API endpoint.
- Insufficient permissions in the CRM may cause authorization failures.
Error messages:
- Authentication errors typically indicate invalid API credentials; verify and update the API key.
- Validation errors from the API may indicate that the lead or segment IDs do not exist; confirm these IDs are correct.
- Timeout or network errors suggest connectivity issues; check network settings and CRM availability.
To handle errors gracefully, enable the node’s "Continue On Fail" option to allow workflow execution to proceed even if some items fail.

Links and References

BimeBazar CRM API Documentation (hypothetical link)
n8n HTTP Request Node documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/

Crm