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
This node allows users to update a Smart Process Automation (SPA) type in Bitrix24, a CRM and business platform. It is useful for customizing SPA types by changing their properties such as enabling or disabling various fields, automation features, document printing, and access permissions.
Typical use cases include:
- Modifying an existing SPA type to enable client binding or product linking.
- Activating automation rules and triggers for a specific SPA type.
- Adjusting visibility and permission settings for new SPA elements.
- Enabling additional fields like payment stages, source, observers, or company details.
For example, a user might update a SPA type to enable the "Payment Stage" field and activate automation rules to streamline sales processes.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication: OAuth2, Webhook URL, or API Key. |
| Type Name | The name of the Smart Process type to update. |
| Type ID | Select the Smart Process type to update by its identifier. |
| Enable Client Field | Whether to enable the Client field with bindings to Contacts and Companies. |
| Enable Document Printing | Whether to enable document printing functionality. |
| Enable Use in User Field | Whether to enable the use of this SPA type in user fields. |
| Enable Product Binding | Whether to enable binding of catalog products to the SPA type. |
| Enable Company Details Field | Whether to enable the "Your Company Details" field. |
| Enable Observers Field | Whether to enable the Observers field. |
| Enable Recycle Bin | Whether to enable recycle bin functionality for deleted SPA items. |
| Enable Automation Rules & Triggers | Whether to enable automation rules and triggers for the SPA type. |
| Enable Start Date & End Date Fields | Whether to enable Start Date and End Date fields for SPA items. |
| Enable Business Process Designer | Whether to enable the use of the business process designer for this SPA type. |
| Enable Custom Sales Funnels | Whether to enable custom sales funnels and tunnels. |
| Enable Source Field | Whether to enable the Source field. |
| Enable Set Open Permissions for New Elements | Whether to enable setting open permissions for new SPA elements. |
| Enable Payment Stage Field | Whether to enable the Payment Stage field. |
| Enable REST API | Whether to enable external access via REST API (default enabled). |
| Options | A collection of additional optional parameters: - Access Token: Use a specific access token instead of credentials. - Entity Type ID: Numeric identifier of the SPA (≥ 1030 or in range 128-192). - Entity Type Code: Code identifier (lowercase, no spaces). - Description: Description text for the SPA type. - Relations: JSON object defining links to other CRM entities. - Linked User Fields: JSON object specifying user fields where this SPA should appear when enabled. |
Output
The node outputs an array of items representing the result of the update operation. Each item contains a json property with the response data from Bitrix24's API regarding the updated SPA type.
If an error occurs and the node is configured to continue on failure, the output will contain an item with an error message, the resource name, and a timestamp.
No binary data output is produced by this node.
Dependencies
- Requires connection to Bitrix24 CRM platform.
- Supports three authentication methods: OAuth2, webhook URL, or API key.
- Needs appropriate API credentials configured in n8n for authentication.
- Uses Bitrix24 API endpoints to perform SPA type updates.
- Optional: An access token can be provided directly in the node options to override credential tokens.
Troubleshooting
Common issues:
- Invalid or missing SPA Type ID: Ensure the selected SPA type exists and the ID is correct.
- Insufficient permissions: The API credentials must have rights to modify SPA types.
- Incorrect authentication method or expired tokens may cause authorization failures.
- Malformed JSON in "Relations" or "Linked User Fields" options can cause API errors.
Error messages:
- Errors returned from Bitrix24 API will be included in the output if "Continue On Fail" is enabled.
- Typical errors include "Invalid SPA Type ID", "Access Denied", or "Malformed JSON".
Resolutions:
- Verify SPA Type ID and ensure it is selected from the available list.
- Check and refresh API credentials or tokens.
- Validate JSON syntax in options before saving.
- Enable detailed logging to capture API responses for debugging.