3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

This node interacts with the 3CX telephony system, specifically allowing retrieval of user information within that system. The "Get User" operation fetches details about a specific user by their unique identifier. This is useful in scenarios where you need to integrate telephony user data into workflows, such as syncing user info with CRM systems, automating call routing based on user attributes, or generating reports involving telephony users.

For example, you might use this node to get detailed information about a user who just made a call, then pass that data downstream for logging or notification purposes.

Properties

Name Meaning
Id The unique identifier of the user entity to retrieve. You can provide a static number or use an expression like {{$json.Id}} to dynamically specify the user ID.
Options Additional query options to customize the returned data:
- $select Comma-separated list of specific user properties to return (e.g., Id,Name).
- $expand Comma-separated list of related entities to expand and include in the response.

Output

The node outputs JSON data representing the user entity retrieved from the 3CX system. The structure depends on the selected properties and expansions specified in the options. It typically includes fields such as user ID, name, and any related entities expanded via the $expand option.

No binary data output is indicated.

Dependencies

  • Requires an API authentication token credential configured in n8n to connect securely to the 3CX system.
  • The base URL for the 3CX API must be provided in the credentials configuration.
  • The node sends requests to the 3CX REST API endpoint /xapi/v1.

Troubleshooting

  • Invalid or missing user ID: Ensure the Id property is set correctly and corresponds to an existing user in 3CX.
  • Authentication errors: Verify that the API key or OAuth2 token is valid and has sufficient permissions.
  • Network or URL issues: Confirm the base URL in credentials is correct and accessible from the n8n instance.
  • Incorrect $select or $expand syntax: Use comma-separated lists without spaces; invalid property names may cause errors or empty responses.

Links and References

Discussion