Crm

Perform actions in BimeBazar CRM

Actions4

Overview

This node integrates with the BimeBazar CRM system to perform various lead management actions. Specifically, for the "Change Lead Status" operation, it updates the status and optionally the sub-status of a specified lead within the CRM. This is useful in sales or customer relationship workflows where leads progress through different stages, and their statuses need to be updated programmatically based on external triggers or automation.

Practical examples include:

Automatically updating a lead's status after a phone call or email interaction.
Moving leads to a "Qualified" or "Negotiation" status when certain criteria are met.
Setting a sub-status to provide more granular tracking of lead progress.

Properties

Name	Meaning
Lead ID	The unique identifier of the lead whose status you want to change.
Status	The identifier of the new status to assign to the lead.
Sub Status	(Optional) The identifier of the new sub-status to assign to the lead for finer detail.

Output

The node outputs a JSON object for each input item processed, structured as follows:

{
  "success": true,
  "operation": "changeLeadStatus",
  "leadId": <number>,
  "status": <number>,
  "subStatus": <number|null>,
  "response": <object>
}

success: Indicates whether the operation was successful.
operation: The name of the operation performed ("changeLeadStatus").
leadId: The ID of the lead that was updated.
status: The new status ID assigned to the lead.
subStatus: The new sub-status ID assigned to the lead, if provided.
response: The raw response from the CRM API, typically containing details about the update.

No binary data output is produced 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's credentials.
Proper permissions in the CRM are needed to update lead statuses.

Troubleshooting

Common issues:
- Invalid or missing Lead ID, Status, or Sub Status values will cause the API request to fail.
- Incorrect or expired API tokens will result in authentication errors.
- Network connectivity problems can prevent communication with the CRM API.
Error messages:
- Authentication failures usually return 401 Unauthorized errors; verify API token validity.
- 404 Not Found may indicate the lead ID does not exist.
- Validation errors from the API may occur if status or sub-status IDs are invalid.
Resolutions:
- Double-check all input IDs and ensure they exist in the CRM.
- Refresh or reconfigure API credentials if authentication fails.
- Ensure the node has internet access and the CRM API endpoint is reachable.

Links and References

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

CrmInstall