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 user by their phone number. It is useful in scenarios where you need to look up user details based on their international phone number, such as verifying caller identity, fetching user profiles for call routing, or integrating telephony data into other workflows.

For example, you might use this node to:

  • Automatically fetch user details when a call comes in from a specific number.
  • Enrich CRM records with telephony user information.
  • Trigger notifications or actions based on the presence or attributes of a user identified by their phone number.

Properties

Name Meaning
Number Phone number in international format (e.g., +1234567890). This is the key input used to find the corresponding user in the 3CX system.

Output

The node outputs JSON data representing the user details retrieved from the 3CX system for the given phone number. The exact structure depends on the 3CX API response but typically includes user identifiers, contact information, and possibly status or extension details.

If the node supports binary data output (not indicated here), it would typically relate to attachments or media associated with the user, but no such indication is present in the provided code.

Dependencies

  • Requires an active connection to a 3CX telephony system.
  • Needs an API authentication token configured via OAuth2 credentials to authorize requests.
  • The base URL for the 3CX server must be set in the node credentials configuration.
  • The node sends HTTP 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 configured and have not expired.
  • Connection issues: Check the 3CX server URL and network connectivity.
  • User not found: If no user matches the provided number, the node may return an empty result or an error; verify the number exists in the 3CX system.
  • API changes: If the 3CX API changes, the node might fail; ensure compatibility with the current API version.

Links and References

Discussion