Crm icon

Crm

Perform actions in BimeBazar CRM

Actions6

Overview

This node integrates with the BimeBazar CRM system to perform various lead and customer 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.

Common scenarios where this node is beneficial include automating lead lifecycle management, such as moving leads through different sales stages or updating their statuses based on external triggers or workflows. For example, after qualifying a lead in a marketing campaign, you could use this node to update its status to "Qualified" automatically.

Properties

Name Meaning
Lead ID The unique identifier of the lead whose status you want to change.
Status The ID of the new status to assign to the lead.
Sub Status (Optional) The ID of the new sub-status to assign to the lead, providing more granularity.

Output

The node outputs a JSON object for each input item processed, containing:

  • success: A boolean indicating if the operation was successful.
  • operation: The string "changeLeadStatus" identifying the performed operation.
  • 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 call, typically including details about the updated lead status.

No binary data output is produced by this operation.

Example output JSON:

{
  "success": true,
  "operation": "changeLeadStatus",
  "leadId": 12345,
  "status": 10,
  "subStatus": 5,
  "response": {
    /* CRM API response details */
  }
}

Dependencies

  • Requires an API key credential for authenticating with the BimeBazar CRM API.
  • The node makes HTTP POST requests to the CRM's /api/bot/leads/{leadId}/status endpoint.
  • The base URL and API token must be configured in the node credentials.
  • The node expects the CRM API to accept JSON payloads with status_id and sub_status_id.

Troubleshooting

  • Invalid Lead ID: If the lead ID does not exist or is incorrect, the CRM API may return an error. Verify the lead ID before running the node.
  • Invalid Status or Sub Status IDs: Using non-existent status or sub-status IDs will cause the API to reject the request. Ensure these IDs are valid within your CRM setup.
  • Authentication Errors: If the API token is missing, expired, or invalid, the node will fail to authenticate. Check the API key credential configuration.
  • Malformed JSON or Missing Parameters: The node requires leadId and status parameters; missing these will cause errors.
  • API Rate Limits or Network Issues: Temporary failures might occur due to network problems or rate limiting by the CRM API. Retrying or adding error handling can help.

Links and References

Discussion