3CX icon

3CX

Interact with 3CX telephony system

Actions462

Overview

This node integrates with the 3CX telephony system, specifically allowing users to retrieve information about a particular MCU (Multipoint Control Unit) row within conference settings. It is useful in scenarios where you need to programmatically access detailed configuration or status of MCU rows in 3CX conferences, such as monitoring conference participants or managing conference resources.

A practical example would be automating the retrieval of MCU row details by providing a unique identifier (GUID), which can then be used for reporting or further processing within an n8n workflow.

Properties

Name Meaning
Guid The unique identifier (GUID) of the MCU row to retrieve. This is required and should be provided in the format guid={guid}.

Output

The node outputs JSON data representing the MCU row details fetched from the 3CX system. This typically includes all relevant properties of the MCU row such as participant information, status, and configuration parameters. The output does not include binary data.

Dependencies

  • Requires an API key credential for authenticating with the 3CX telephony system.
  • The node expects the base URL of the 3CX server to be configured in the credentials.
  • The node sends requests to the 3CX REST API endpoint /xapi/v1.

Troubleshooting

  • Missing or invalid GUID: If the GUID property is empty or incorrect, the node will fail to retrieve the MCU row. Ensure the GUID is correctly specified.
  • Authentication errors: If the API key or OAuth2 token is missing or invalid, the node will return authentication errors. Verify that the correct credentials are set up.
  • Network or URL issues: If the 3CX server URL is misconfigured or unreachable, the node will fail to connect. Confirm the server URL is correct and accessible.
  • API changes: If the 3CX API changes, some fields or endpoints might become deprecated. Check the 3CX API documentation if unexpected errors occur.

Links and References

Discussion