Actions10
Overview
This node integrates with Bitrix24 to manage categories and statuses within the CRM system. It supports creating, updating, retrieving, listing, and deleting these elements via Bitrix24's API using webhook URLs.
Common scenarios where this node is useful include:
- Automating the creation or update of product categories or deal statuses in Bitrix24.
- Synchronizing external data sources with Bitrix24 CRM categories or statuses.
- Bulk creation of multiple categories or statuses in one operation.
- Retrieving category or status details for reporting or further processing.
- Deleting obsolete categories or statuses programmatically.
For example, a sales automation workflow could use this node to create new deal stages (statuses) dynamically based on changing business processes, or to bulk import product categories from an external inventory system.
Properties
| Name | Meaning |
|---|---|
| Multiple Items | Boolean flag to create or update multiple elements at once. |
The node also supports additional properties depending on the resource and operation:
For Category resource with create/update operations:
- Name: The name of the product category.
- Sort: Sorting order number for the category.
- Is Default: Whether this category is the default one.
- Items (when Multiple Items is true): A list of categories each with Name, Sort, and Is Default fields.
For Status resource with create/update operations:
- Category ID: The ID of the product category the status belongs to.
- Status Name: The name of the status.
- Status Sort: Sorting order number for the status.
- Status Color: HEX color code representing the status.
- Status Semantic: Semantic meaning of the status; options are "Process", "Success", or "Failure".
- Status Items (when Multiple Items is true): A list of statuses each with Name, Sort, Color, and Semantic.
For get, getAll, and delete operations, relevant IDs or filters are required as input parameters.
Output
The node outputs a JSON array where each element corresponds to the result of an individual API call or item processed. Each successful output object includes:
success: Alwaystrueindicating the operation succeeded.id: The unique identifier returned by Bitrix24 for the created or updated element.- Other fields reflecting the input properties used for creation or update (e.g., name, sort, color).
In case of errors, the output contains objects with an error field describing the issue.
No binary data output is produced by this node.
Dependencies
- Requires a valid Bitrix24 API credential configured in n8n that provides a webhook URL.
- Uses the webhook URL to send HTTP POST requests to Bitrix24 endpoints.
- Optionally sets the environment variable for default language based on credential settings (defaults to Russian if not specified).
- Depends on the Axios HTTP client library for making API calls.
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 set up with a valid webhook URL.
- API Errors: If Bitrix24 returns an error, the node surfaces the error description. Common causes include invalid IDs, missing required fields, or permission issues. Verify input parameters and API permissions.
- Multiple Items Handling: When using the "Multiple Items" option, ensure the items collection is correctly structured; otherwise, the node may fail or skip items.
- Network Issues: Connectivity problems to Bitrix24 webhook URL will cause request failures. Check network access and webhook validity.
- Continue On Fail: If enabled, the node continues processing remaining items after an error, returning error details per failed item.