Actions31
- Company Actions
- Contact Actions
- Deal Actions
- Item Actions
- Lead Actions
- User Custom Method Actions
Overview
This node integrates with the Bitrix24 REST API to perform operations on CRM resources. Specifically, for the Contact resource and the Delete operation, it deletes a contact record identified by its ID from the Bitrix24 CRM system.
Common scenarios where this node is useful include:
- Automating cleanup of outdated or invalid contact records.
- Integrating with other systems to remove contacts when they are deleted elsewhere.
- Managing CRM data lifecycle programmatically within workflows.
Example: Automatically delete a contact after a certain event triggers in your workflow, such as unsubscribing from a mailing list or closing a deal.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method to authenticate API requests. Options: OAuth2, Webhook |
| ID | The unique identifier of the contact record to delete. Example: "12345" |
Output
The node outputs JSON data representing the response from the Bitrix24 API after attempting to delete the contact. This typically includes confirmation of deletion or error details if the operation failed.
No binary data output is produced by this node.
Dependencies
- Requires valid authentication credentials for Bitrix24, either via OAuth2 or Webhook authentication.
- The node depends on Bitrix24 REST API availability and correct permissions to delete contact records.
- No additional external dependencies beyond standard HTTP requests to Bitrix24 API.
Troubleshooting
- Invalid ID or Contact Not Found: If the provided contact ID does not exist, the API will return an error. Verify the ID is correct.
- Authentication Errors: Ensure that the selected authentication method is properly configured with valid credentials.
- Permission Denied: The authenticated user must have sufficient rights to delete contacts in Bitrix24.
- API Rate Limits: Excessive requests may be throttled by Bitrix24; implement retries or backoff as needed.