Actions25
Overview
This node integrates with the Bitrix24 CRM system to manage Contact records. Specifically, the "List" operation retrieves multiple Contact records from Bitrix24. It supports fetching all contacts or limiting the number of returned records and allows selecting specific fields to retrieve for each contact.
Common scenarios where this node is useful include:
- Synchronizing contacts from Bitrix24 into another system.
- Generating reports or lists of contacts based on selected fields.
- Automating workflows that require bulk access to contact data.
For example, you can use this node to fetch all contacts with their email and phone numbers to send a marketing campaign or to update an external database with the latest contact information.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all contact records or limit the number of records fetched. |
| Limit | The maximum number of contact records to return (used only if "Return All" is false). |
| Select Fields | Choose which fields of the contact records to retrieve. Options are dynamically loaded from Bitrix24 and may include fields like name, email, phone, etc. |
Output
The output is a JSON array where each element corresponds to a contact record retrieved from Bitrix24. Each record contains key-value pairs representing the selected fields and their values.
If binary data were involved, it would be summarized here, but this node deals only with JSON data representing contact fields.
Dependencies
- Requires an API authentication token configured as credentials in n8n to access the Bitrix24 API.
- Uses the Bitrix24 webhook URL from the credentials to construct API endpoints.
- Relies on the Bitrix24 REST API endpoints for contacts (
crm.contact.list.json).
Troubleshooting
- Missing Credentials: If no API credentials or webhook URL are provided, the node will throw an error indicating these are required.
- Invalid Field Names: Selecting fields not available in Bitrix24 may cause errors or empty results. Use the dynamic field loader to select valid fields.
- API Errors: Network issues or invalid permissions can cause API request failures. Check the API key validity and network connectivity.
- Limit vs Return All: Setting "Return All" to false but not specifying a reasonable "Limit" may result in fewer records than expected.