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 supporting operations on various resources including Smart Process Automation (SPA). The "Update SPA" operation allows users to update records within a Smart Process entity in Bitrix24. This is useful for automating business workflows where custom data structures (SPAs) are used, such as managing custom pipelines, processes, or data collections unique to an organization.
Typical use cases include:
- Updating SPA records when external events occur, e.g., updating a customer onboarding process status.
- Automating updates to SPA entities based on other CRM changes.
- Integrating SPA updates into broader automation workflows within n8n.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: - OAuth2 (recommended for production) - Webhook (simpler but less secure) - API Key |
Note: The provided properties JSON only includes the "Authentication" property. The full node supports selecting resource and operation, but here we focus on SPA Update operation.
Output
The node outputs an array of items, each containing a json object representing the response from Bitrix24 after processing the requested operation. For the SPA update operation, this typically includes the updated SPA record details or confirmation of the update.
If an error occurs and the node is configured to continue on failure, the output will contain an item with an error field describing the issue, 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 REST API endpoints internally to perform operations.
- Requires appropriate credentials configured in n8n for the chosen authentication method.
- No additional external dependencies beyond Bitrix24 API access.
Troubleshooting
Common issues:
- Authentication failures due to incorrect or expired credentials.
- Missing or invalid SPA type or entity ID parameters causing API errors.
- Network connectivity issues preventing API calls.
- Insufficient permissions in Bitrix24 for the authenticated user to update SPA records.
Error messages:
- Errors returned from Bitrix24 API will be surfaced in the node's output if "Continue On Fail" is enabled.
- Typical error messages may include authorization errors, invalid parameter errors, or resource not found.
Resolutions:
- Verify that the correct authentication method and valid credentials are used.
- Ensure the SPA type and record IDs exist and are accessible.
- Check network connectivity and Bitrix24 service status.
- Confirm user permissions in Bitrix24 allow updating SPA entities.