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 operations. Specifically, for the "Create Lead" operation, it allows users to create a new lead in the CRM by providing essential details such as the lead's name, phone number, panel number, and optional attributes like customer ID, team ID, segment, expert, source, status, sub-status, metadata, reminder date, and tags.

This node is beneficial in scenarios where businesses want to automate lead creation from external sources or workflows, such as capturing leads from web forms, marketing campaigns, or other systems, and directly pushing them into their CRM for further processing and follow-up.

Practical example:

  • Automatically create a new lead in BimeBazar CRM when a potential customer fills out a contact form on your website, including tagging the lead for segmentation and assigning it to a specific team or expert.

Properties

Name Meaning
Name The name of the lead (required).
Phone The phone number of the lead (required).
Panel Number The panel number associated with the lead (required).
Customer ID The numeric ID of the customer related to the lead (optional).
Team ID The numeric ID of the team responsible for the lead (optional).
Current Segment ID The numeric ID of the current segment the lead belongs to (optional).
Expert ID The numeric ID of the expert assigned to the lead (optional).
Source ID The numeric ID representing the source of the lead (optional).
Status ID The numeric ID of the lead's status (optional).
Sub Status ID The numeric ID of the lead's sub-status (optional).
Metadata Additional JSON-formatted metadata for the lead (optional).
Remind At A date-time string specifying a reminder date for the lead (optional).
Tags An array of tag IDs to assign to the lead (optional).
Customer Tags An array of tag IDs to assign to the customer related to the lead (optional).

Output

The node outputs an array of JSON objects, each representing the result of the create lead operation for each input item. The main output structure includes:

  • success: Boolean indicating if the operation was successful.
  • operation: The string "createLead" indicating the performed operation.
  • lead: An object containing the newly created lead data as returned by the CRM API.

Example output JSON snippet:

{
  "success": true,
  "operation": "createLead",
  "lead": {
    "id": 123,
    "name": "John Doe",
    "phone": "+1234567890",
    "panel_number": "PN001",
    "customer_id": 456,
    "team_id": 789,
    "current_segment_id": 10,
    "expert_id": 11,
    "source_id": 12,
    "status_id": 13,
    "sub_status_id": 14,
    "metadata": { "key": "value" },
    "remind_at": "2024-07-01T10:00:00Z",
    "tags": [1, 2],
    "customer_tags": [3, 4]
  }
}

The node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating with the BimeBazar CRM API.
  • The node makes HTTP POST requests to the CRM API endpoints using the base URL and API token provided by the credentials.
  • No additional external dependencies are required beyond the configured API authentication.

Troubleshooting

  • Common issues:

    • Missing required fields such as "Name", "Phone", or "Panel Number" will cause the API request to fail.
    • Invalid or expired API tokens will result in authentication errors.
    • Providing invalid IDs (e.g., non-existent customer, team, or tag IDs) may cause the CRM API to return errors.
    • Malformed JSON in the "Metadata" field can cause parsing errors.

  • Error messages and resolutions:

    • Authentication errors: Verify that the API key credential is correctly configured and has not expired.
    • Validation errors from the API: Check that all required fields are provided and valid.
    • JSON parse errors for metadata: Ensure the metadata input is valid JSON.
    • Network or connectivity errors: Confirm that the CRM API base URL is reachable from the n8n environment.

Links and References

Discussion