Actions10
Overview
This node integrates with Bitrix24 to manage auxiliary CRM entities, specifically categories and statuses related to deals. It supports operations such as creating, updating, retrieving, listing, and deleting these entities via Bitrix24's API.
Typical use cases include:
- Automating the creation or update of deal categories or statuses in Bitrix24 based on external data.
- Synchronizing status lists or categories from other systems into Bitrix24.
- Bulk creation or update of multiple categories or statuses in one execution.
- Fetching details or lists of existing categories or statuses for reporting or further processing.
For example, a sales automation workflow could use this node to update deal stages (statuses) dynamically based on changing business rules or import a predefined set of categories for deals.
Properties
| Name | Meaning |
|---|---|
| Multiple Items | Boolean flag indicating whether to create/update multiple items at once (true or false). |
| Items | When Multiple Items is true and resource is "category", this is a list of categories to create/update. Each category has: Name, Sort order, Is Default flag. |
| Status Items | When Multiple Items is true and resource is "status", this is a list of statuses to create/update. Each status has: Name, Sort order, Color (HEX), Semantic (Process, Success, Failure). |
| ID | The identifier of the category or status to update, get, or delete. Required for update/get/delete operations. |
| Name | The name of the category or status to create or update. |
| Sort | Numeric sort order for the category or status. |
| Is Default | Boolean flag indicating if the category is the default one. |
| Category ID | For statuses, the ID of the category they belong to. |
| Status Name | Name of the status (for single status create/update). |
| Status Sort | Sort order of the status (for single status create/update). |
| Status Color | HEX color code representing the status color. |
| Status Semantic | Semantic meaning of the status: Process (P), Success (S), or Failure (F). |
Output
The node outputs an array of JSON objects representing the results of each processed item. Each object typically contains:
success: Boolean indicating if the operation succeeded.id: The ID of the created or updated entity.- Other fields depending on the resource type, e.g.,
name,sort,isDefaultfor categories;NAME,SORT,COLOR,SEMANTIC_INFOfor statuses. - In case of errors (if continue on fail is enabled), an object with an
errorfield describing the issue.
No binary data output is produced by this node.
Dependencies
- Requires a valid Bitrix24 API webhook URL credential configured in n8n.
- Uses HTTP POST requests to Bitrix24 REST API endpoints.
- Optionally sets the environment language variable based on credential settings (defaulting to Russian).
Troubleshooting
- Missing Credentials or Webhook URL: The node throws an error if no credentials or webhook URL are provided. Ensure the Bitrix24 API credential is properly configured with a valid webhook URL.
- API Errors: If Bitrix24 returns an error, the node surfaces the error description. Common causes include invalid IDs, permission issues, or malformed requests.
- Bulk Operations Failures: When using multiple items, partial failures may occur. Enable "Continue On Fail" to process all items and collect individual errors.
- Invalid Property Values: Ensure required properties like IDs, names, and category IDs are correctly set according to the operation and resource.
- Language Setting: The node sets a default language environment variable which might affect localization; verify if this impacts your workflows.