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). The "Set SPA Permissions" operation allows users to configure permissions related to SPA entities within Bitrix24. This is useful for automating permission management in workflows that involve custom SPA types, ensuring appropriate access control without manual intervention.
Practical examples include:
- Automatically setting user or group permissions on a SPA entity when it is created or updated.
- Integrating SPA permission changes into broader CRM automation processes.
- Managing access rights dynamically based on business logic executed in n8n workflows.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24. Options: OAuth2 (recommended for production), Webhook (simpler but less secure), API Key authentication. |
Output
The node outputs JSON data representing the result of the SPA permission setting operation. The exact structure depends on the Bitrix24 API response but generally includes confirmation of success or details about any errors encountered.
If an error occurs and the workflow is configured to continue on failure, the output JSON will contain an error field with the error message, along with the resource name and a timestamp.
No binary data output is indicated by the source code.
Dependencies
- Requires connection to Bitrix24 via one of the supported authentication methods (OAuth2, webhook URL, or API key).
- Uses Bitrix24 API endpoints internally to perform SPA-related operations.
- The node relies on internal helper functions (
makeStandardBitrix24Call) to communicate with Bitrix24 APIs. - Proper configuration of credentials in n8n is necessary for successful API calls.
Troubleshooting
Common issues:
- Authentication failures due to incorrect or expired credentials.
- API call errors if the specified SPA type or permissions are invalid or missing.
- Network connectivity problems preventing communication with Bitrix24.
Error messages:
- Errors returned from Bitrix24 API calls will be propagated as exceptions.
- If "Continue On Fail" is enabled, errors are returned in the output JSON under the
errorproperty. - Messages like "Failed to load SPA types" or "Failed to load SPA fields" indicate issues fetching metadata, often due to permission or API limitations.
Resolutions:
- Verify and refresh authentication credentials.
- Ensure the SPA type IDs and permission parameters used are valid and exist in the Bitrix24 instance.
- Check network connectivity and firewall settings.
- Enable detailed logging in n8n to capture API request/response details for debugging.