3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

This node interacts with the 3CX telephony system, specifically allowing users to update call type settings such as International, Local, Mobile, and National call configurations. It is useful in scenarios where an organization needs to programmatically manage or customize how different types of calls are handled within their 3CX system, for example, updating dialing rules or call restrictions dynamically.

Practical examples include:

  • Automatically updating call cost limits or routing preferences for international calls.
  • Adjusting local call parameters based on time of day or user roles.
  • Managing mobile call settings to optimize costs or compliance.
  • Configuring national call options to align with company policies.

Properties

Name Meaning
International JSON object representing the settings for international calls.
Local JSON object representing the settings for local calls.
Mobile JSON object representing the settings for mobile calls.
National JSON object representing the settings for national calls.

Each property expects a JSON-formatted string that will be parsed and sent as part of the request body to update the respective call type settings.

Output

The node outputs data in JSON format reflecting the response from the 3CX API after attempting to update the call type settings. The exact structure depends on the API's response but typically includes confirmation of updated settings or error details if the update failed.

No binary data output is indicated.

Dependencies

  • Requires an active connection to a 3CX telephony system.
  • Needs an API authentication token (OAuth2) configured in n8n credentials to authorize requests.
  • The base URL for the 3CX server must be provided in the credentials configuration.
  • The node sends HTTP requests with JSON payloads to the 3CX API endpoint /xapi/v1.

Troubleshooting

  • Invalid JSON Input: If the JSON provided in any of the call type properties is malformed, the node will fail to parse it, resulting in errors. Ensure all JSON inputs are valid.
  • Authentication Errors: Missing or incorrect API credentials will cause authorization failures. Verify that the OAuth2 credential is correctly set up and has necessary permissions.
  • API Endpoint Issues: Incorrect server URL or network issues can prevent communication with the 3CX API. Confirm the server URL is correct and accessible.
  • API Response Errors: The 3CX API may return errors if the provided settings are invalid or incomplete. Review the API documentation for required fields and constraints.

Links and References

Discussion