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, the "Archive Lead" operation allows users to archive a lead by its ID, effectively marking it as archived in the CRM.

Common scenarios for using this node include automating CRM workflows such as cleaning up old or inactive leads, managing lead lifecycle stages, or integrating CRM updates into broader automation pipelines.

For example, after qualifying a lead through a marketing campaign, you might use this node to archive leads that did not convert, keeping your CRM data organized and focused on active prospects.

Properties

Name Meaning
Lead ID The unique numeric identifier of the lead to be archived. This is required for the operation.

Output

The node outputs a JSON object containing:

  • success: A boolean indicating if the operation was successful.
  • operation: The name of the performed operation ("archiveLead").
  • leadId: The ID of the lead that was archived.
  • response: The raw response from the CRM API after attempting to archive the lead.

No binary data output is produced by this operation.

Example output JSON:

{
  "success": true,
  "operation": "archiveLead",
  "leadId": 12345,
  "response": {
    // CRM API response details here
  }
}

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}/archive endpoint.
  • The base URL and API token must be configured in the node's credentials.

Troubleshooting

  • Common issues:

    • Invalid or missing Lead ID will cause the API request to fail.
    • Incorrect or expired API credentials will result in authentication errors.
    • Network connectivity problems can prevent the node from reaching the CRM API.

  • Error messages:

    • Authentication failures typically return 401 Unauthorized errors; verify API token validity.
    • 404 Not Found may indicate the specified lead ID does not exist.
    • Validation errors from the API may occur if the lead is already archived or cannot be archived due to business rules.

  • Resolution tips:

    • Double-check the Lead ID input and ensure it corresponds to an existing lead.
    • Confirm that the API credentials are correctly set up and have necessary permissions.
    • Review the CRM API documentation for any constraints on archiving leads.

Links and References

Discussion