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 update a Contact record. It allows users to modify existing contact data by specifying the contact's unique ID and providing new values for one or more fields. This is useful in scenarios where contact information needs to be kept current, such as updating phone numbers, email addresses, or custom fields after receiving new data from other systems or user input.
Practical examples include:
- Automatically updating a contact’s details when a customer submits a form.
- Synchronizing contact information between Bitrix24 and another CRM or database.
- Correcting or enriching contact records based on external data sources.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24 API: either via OAuth2 or Webhook. |
| ID | The unique identifier of the contact record to update. |
| Input Type | How to provide the update data: "Using Fields" to specify individual fields or "Using JSON" to provide raw JSON data. |
| Fields | When using "Using Fields" input type, specify one or more field name-value pairs to update. Field names can be selected from available contact fields. |
| JSON Body | When using "Using JSON" input type, provide the complete update data as raw JSON. |
Output
The node outputs the response from the Bitrix24 API after attempting to update the contact. The json output typically contains the updated contact data or confirmation of the update operation. If the API returns any errors, those will also be included in the output.
The node does not output binary data.
Dependencies
- Requires an active connection to Bitrix24 via either OAuth2 authentication or a Webhook URL.
- Users must configure appropriate credentials in n8n for authentication.
- The node depends on Bitrix24 REST API availability and permissions granted to the authenticated user.
Troubleshooting
- Invalid ID: If the provided contact ID does not exist, the API will return an error indicating the record was not found. Verify the ID is correct.
- Authentication Errors: Incorrect or expired credentials will cause authentication failures. Re-authenticate or update credentials as needed.
- Field Validation Errors: Providing invalid field names or values may result in API errors. Use the node’s field selector or validate JSON structure carefully.
- API Rate Limits: Frequent updates might hit Bitrix24 API rate limits; consider adding delays or batching requests.
- JSON Parsing Issues: When using raw JSON input, ensure the JSON is well-formed to avoid parsing errors.
Links and References
- Bitrix24 REST API Documentation
- n8n Expressions Documentation (for dynamic field value expressions)