Actions89
- Direct API Actions
- CRM Actions
- Task Actions
- User Actions
- SPA Actions
- Activity Actions
- Automation Actions
- Document Generator Actions
- Data Storage Actions
- Chat Actions
Overview
The node integrates with the Bitrix24 platform, specifically enabling interaction with its Data Storage resource to list stored data entities. It supports multiple authentication methods including OAuth2, webhook URLs, and API keys, making it flexible for different security requirements.
This node is useful when you want to retrieve lists of data records from Bitrix24's CRM or business platform, such as fetching contacts, deals, leads, or other custom entities stored in Bitrix24. For example, you might use it to pull all customer contacts for syncing with another system or to get a filtered list of deals based on certain criteria.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24: OAuth2 (recommended), Webhook URL (simpler), or API Key |
| Return All | Whether to return all results or limit the output to a specified number |
| Options | Additional parameters to customize the listing: |
| - Access Token | Access token string for authentication |
| - Filter | JSON object specifying filter criteria to narrow down results |
| - Select | Comma-separated list of fields to include in the response |
| - Order | JSON object defining sorting order of the results |
| - Start | Number indicating the start position for pagination |
Output
The node outputs an array of JSON objects representing the listed data entities retrieved from Bitrix24. Each item corresponds to one record matching the query parameters. The structure of each JSON object depends on the selected fields and filters applied.
If an error occurs during execution and "Continue On Fail" is enabled, the output will contain an error object with the error message, resource name, and timestamp.
No binary data output is indicated by the source code.
Dependencies
- Requires valid authentication credentials for Bitrix24 via OAuth2, webhook URL, or API key.
- Depends on Bitrix24 API endpoints to fetch data.
- No additional external services are required beyond Bitrix24 itself.
- Proper configuration of credentials in n8n is necessary for successful API calls.
Troubleshooting
Common Issues:
- Authentication failures due to invalid or expired tokens.
- Incorrect filter or order JSON syntax causing API errors.
- Pagination issues if "Return All" is false but the limit is too low.
- Network connectivity problems affecting API calls.
Error Messages:
- Errors thrown by the Bitrix24 API will be surfaced in the node output if "Continue On Fail" is enabled.
- Typical messages include authentication errors, invalid parameter formats, or rate limiting notices.
Resolutions:
- Verify and refresh authentication credentials.
- Ensure JSON inputs for filters and ordering are correctly formatted.
- Adjust pagination settings or enable "Return All" to retrieve complete datasets.
- Check network access and proxy configurations if applicable.