3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

This node integrates with the 3CX telephony system, specifically allowing users to retrieve information about a receptionist by their phone number. It is useful in scenarios where you need to look up receptionist details dynamically based on an incoming or known phone number, such as in call routing, CRM integrations, or automated workflows that require receptionist identification.

For example, if you have a phone number and want to fetch the corresponding receptionist's profile or settings from the 3CX system, this operation will return that data.

Properties

Name Meaning
Number Phone number in international format (e.g., +1234567890). This is the key input to find the receptionist associated with this number.

Output

The node outputs JSON data containing the receptionist's details retrieved from the 3CX system. The exact structure depends on the 3CX API response but typically includes fields such as the receptionist's name, extension, status, and other relevant metadata.

If the node supports binary data output (not indicated here), it would typically represent files or media related to the receptionist, but this operation primarily returns JSON data.

Dependencies

  • Requires connection to a 3CX telephony system.
  • Needs an API authentication token configured via OAuth2 credentials for secure access.
  • The base URL of the 3CX server must be provided in the node credentials.
  • The node sends requests to the 3CX API endpoint /xapi/v1.

Troubleshooting

  • Invalid or missing phone number: Ensure the phone number is provided in the correct international format (e.g., +1234567890).
  • Authentication errors: Verify that the OAuth2 credentials are correctly set up and have not expired.
  • Server URL issues: Confirm the 3CX server URL is correct and accessible from the n8n instance.
  • No receptionist found: If the phone number does not match any receptionist, the node may return an empty result or an error indicating no data found.
  • API rate limits or connectivity problems: Check network connectivity and 3CX API usage limits.

Links and References

Discussion