3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

This node operation updates an existing Trunk Template in the 3CX telephony system. It allows users to modify various attributes of a trunk template such as its name, description, allowed countries, ports, messaging templates, and other configuration details.

Typical use cases include:

  • Adjusting trunk template settings after initial creation to reflect changes in telephony infrastructure.
  • Managing trunk templates programmatically as part of automated telephony system administration.
  • Updating messaging templates or allowed countries dynamically based on business needs.

For example, you might update a trunk template to add new allowed countries or change the default proxy port used by the trunk.

Properties

Name Meaning
Id The unique identifier of the trunk template to update. Can be set via expression like {{$json.Id}}.
Add Allowed Boolean flag indicating whether adding is allowed (true/false).
Content String content related to the trunk template (specific usage depends on 3CX API).
Countries JSON array specifying allowed countries for this trunk template.
Default Proxy Port Number specifying the default proxy port for the trunk.
Default Registrar Port Number specifying the default registrar port for the trunk.
Description Text description of the trunk template.
Editors JSON array listing editors who can modify the trunk template.
Messaging Template JSON object defining messaging variables and templates associated with the trunk.
Name Name of the trunk template.
Tags JSON array of tags associated with the trunk template.
Template Type Type of the trunk template. Options: Preferred, Supported, Dedicated, Third Party, Deleted, Unknown.
Url URL associated with the trunk template (usage depends on context).

Output

The node outputs JSON data representing the updated trunk template entity as returned by the 3CX API. This typically includes all properties of the trunk template after the update operation.

No binary data output is indicated.

Dependencies

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

Troubleshooting

  • Invalid Id: If the provided Id does not correspond to an existing trunk template, the API will likely return an error. Verify the Id value is correct.
  • Authentication errors: Ensure that the API credentials are valid and have sufficient permissions to update trunk templates.
  • Malformed JSON inputs: Properties like Countries, Editors, Messaging Template, and Tags expect valid JSON strings. Invalid JSON will cause parsing errors.
  • Missing required fields: The Id property is mandatory; omitting it will prevent the update.
  • API connectivity issues: Check network access to the 3CX server and that the base URL is correctly configured.

Links and References

Discussion