3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

This node operation updates an existing contact in the 3CX telephony system. It allows users to modify various details of a contact such as names, phone numbers, email, company information, and other contact-related fields. This is useful for keeping contact information current within the 3CX system, ensuring that call routing, caller ID, and other telephony features use up-to-date data.

Practical examples include:

  • Updating a contact’s phone number or email after they have changed.
  • Modifying the company or department information for a contact.
  • Adding tags or notes to contacts for better categorization.

Properties

Name Meaning
Id The unique identifier of the contact to update. Can be set using expressions like {{$json.Id}}. This is required.
Business Business phone number of the contact.
Business 2 Secondary business phone number.
Business Fax Business fax number.
Company Name Name of the company the contact belongs to.
Contact Type Type/category of the contact (e.g., client, vendor).
Department Department within the company.
Email Contact's email address.
First Name Contact's first name.
Home Home phone number.
Last Name Contact's last name.
Mobile 2 Secondary mobile phone number.
Other Other phone number or contact detail.
Pager Pager number.
Phone Number Primary phone number.
Tag Tags or labels associated with the contact.
Title Job title or position of the contact.

All properties except Id are optional and can be used to update specific fields of the contact.

Output

The node outputs JSON data representing the updated contact record as returned by the 3CX API. This typically includes all the contact fields after the update has been applied, confirming the new state of the contact.

If the node supports binary data output (not indicated here), it would generally relate to attachments or related media, but this operation focuses on JSON contact data only.

Dependencies

  • Requires an active connection to a 3CX telephony system via its API.
  • Needs an API authentication token or OAuth2 credentials configured in n8n to authorize requests.
  • The base URL for the 3CX server must be provided in the credentials configuration.
  • The node uses HTTP requests to the 3CX API endpoint /xapi/v1.

Troubleshooting

  • Missing or invalid Id: The update operation requires a valid contact Id. If missing or incorrect, the API will return an error indicating the contact was not found.
  • Authentication errors: Ensure the API credentials are correctly set up and have sufficient permissions to update contacts.
  • Invalid field values: Some fields may have format restrictions (e.g., phone numbers, emails). Invalid formats might cause the API to reject the update.
  • Network issues: Connectivity problems with the 3CX server will prevent the update from succeeding.
  • API version mismatch: Using an outdated or incompatible API version could cause unexpected errors.

To resolve these, verify the Id value, check credential validity, confirm field formats, and ensure network connectivity.

Links and References

Discussion