Beex icon

Beex

Beex Contact Center API Interaction and Consumption

Import → Receive Many

AI-generated

Overview

This node operation allows users to perform a massive import of various data types into the Beex Contact Center platform. It supports importing telephones, directions, emails, contacts, payments, external typifications, user assignments, account activations/deactivations, client activations/deactivations, phone activations/deactivations, account field updates, and sequence assignments. Users provide details such as import type, portfolio ID, company ID, assignment type, base ID, country code, and the file to import. The node sends this data to the Beex API to process the massive import, making it useful for bulk data updates or migrations in contact center management.

Use Case Examples

  1. Massively import telephone data for a specific campaign and company.
  2. Bulk update account fields across multiple clients using a CSV file.
  3. Activate multiple client accounts in one operation by importing a prepared file.

Properties

Name Meaning
Type of Imports Select the type of data to import, such as telephones, directions, emails, contacts, payments, etc.
Portfolio ID Campaign ID (Portfolio) to which the import applies.
Company ID Company ID associated with the import.
Assignment Type Select whether the import is an assignment or an update.
Base ID Base ID related to the import.
Country Code Country code relevant to the import.
File to Import The file containing the data to be imported.

Output

JSON

  • json - Response data from the Beex API for the massive import operation

Dependencies

  • Beex Contact Center API
  • API key credential for authentication

Troubleshooting

  • Ensure the API key credential is correctly configured and has the necessary permissions.
  • Verify that the file to import is correctly formatted and accessible.
  • Check that all required parameters (type_import, portfolio, entity, type_assignment, base, country, file_import) are provided and valid.
  • Handle API rate limits or delays as the node includes a 1-second delay between requests to avoid throttling.

Discussion