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 Bitrix24 node enables interaction with the Bitrix24 CRM and business platform, specifically supporting operations on various resources including Smart Process Automation (SPA) types. The "Get Type" operation under the SPA resource retrieves detailed information about a specific Smart Process type by its ID.
This node is beneficial for automating workflows that require fetching metadata or details about SPA types within Bitrix24, such as dynamically adapting automation logic based on SPA type properties or integrating SPA data into other systems.
Practical example:
A user wants to retrieve the configuration or schema of a particular Smart Process type to display it in a custom dashboard or to use it as part of a conditional workflow step in n8n.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24. Options: OAuth2 (recommended), Webhook (simpler), API Key |
| Type ID | The identifier of the Smart Process type to retrieve. This is a required field. The list of available SPA types is dynamically loaded from Bitrix24. |
Output
The node outputs an array of items where each item contains a json object representing the response from Bitrix24 for the requested SPA type. The exact structure depends on the Bitrix24 API response but generally includes fields describing the SPA type's properties, metadata, and configuration.
If an error occurs and "Continue On Fail" is enabled, the output will contain an item with an error message, the resource name, and a timestamp.
No binary data output is indicated in the source code.
Dependencies
- Requires connection to Bitrix24 via one of the supported authentication methods:
- OAuth2 authentication (recommended for production)
- Webhook URL authentication
- API key authentication
- The node relies on Bitrix24 API endpoints, particularly those related to CRM and SPA types.
- Proper credentials must be configured in n8n for the chosen authentication method.
Troubleshooting
Common issues:
- Invalid or missing authentication credentials can cause authorization failures.
- Providing an invalid or non-existent SPA Type ID will result in no data or an error.
- Network connectivity issues may prevent API calls from succeeding.
Error messages:
- Errors thrown during execution will include the message from the Bitrix24 API or internal errors.
- If "Continue On Fail" is enabled, errors are returned as part of the output JSON with an
errorproperty. - Loading SPA types or fields may fail if the Bitrix24 API changes or is temporarily unavailable.
Resolutions:
- Verify that the correct authentication method and valid credentials are set up.
- Ensure the SPA Type ID exists and is correctly selected from the dynamic options.
- Check network connectivity and Bitrix24 service status.
- Enable "Continue On Fail" to handle errors gracefully in workflows.