3CX icon

3CX

Interact with 3CX telephony system

Actions462

Overview

This node interacts with the 3CX telephony system, specifically to retrieve a parameter by its name. It is useful in scenarios where you need to fetch configuration or runtime parameters from the 3CX system dynamically during workflow execution. For example, you might want to get the current status of a telephony feature or retrieve a specific setting to make decisions in your automation.

Properties

Name Meaning
Name The exact name of the parameter to retrieve from the 3CX system. Usage format: name={name} where {name} is replaced by the actual parameter name string. This property is required.

Output

The node outputs JSON data containing the value of the requested parameter fetched from the 3CX system. The structure typically includes the parameter's name and its corresponding value as returned by the 3CX API. There is no indication that binary data is output by this node.

Dependencies

  • Requires an API key credential for authenticating with the 3CX system (OAuth2-based).
  • Needs the base URL of the 3CX server configured in the credentials.
  • The node sends requests to the 3CX API endpoint /xapi/v1.

Troubleshooting

  • Common issues:
    • Incorrect or missing parameter name will result in failure to retrieve the parameter.
    • Invalid or expired API credentials can cause authentication errors.
    • Misconfigured server URL may lead to connection failures.
  • Error messages:
    • Authentication errors usually indicate problems with the OAuth2 token; re-authenticate or update credentials.
    • "Parameter not found" errors suggest the specified parameter name does not exist; verify the exact name.
    • Network or timeout errors imply connectivity issues with the 3CX server; check network settings and server availability.

Links and References

Discussion