3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

The "Update Fxs Template" operation in the 3CX node allows users to modify an existing FXS template entity within the 3CX telephony system. This operation is useful for administrators or automation workflows that need to programmatically update configuration templates related to FXS devices, such as changing allowed network configurations, device branding, supported languages, or other template-specific settings.

Practical examples include:

  • Updating the list of supported device models or languages for a specific FXS template.
  • Changing the template type or enabling/disabling SSL provisioning on the template.
  • Modifying variables or content associated with the template to customize device behavior.

This operation helps maintain and automate telephony device configurations efficiently without manual intervention in the 3CX management console.

Properties

Name Meaning
Id The unique identifier of the FXS template entity to update. Can be provided directly or via an expression (e.g., {{$json.Id}}).
Allowed Net Configs JSON array specifying allowed network configurations for the template.
Allow SSL Provisioning Boolean flag indicating whether SSL provisioning is allowed for this template.
Brand String representing the brand name associated with the template.
Content String content related to the template, possibly containing configuration or descriptive data.
Device Type Option to specify the device type; choices are "Fxs" or "Dect".
Is Custom Boolean indicating if the template is custom-defined (true) or default/system (false).
Languages JSON array listing supported languages for the template.
Models JSON array describing device models supported by the template.
Number Of Extensions Numeric value indicating how many extensions are supported or configured in the template.
Rps Enabled Boolean flag to enable or disable RPS (Remote Provisioning Server) functionality.
Template Type Option defining the template category. Possible values: "Preferred", "Supported", "Dedicated", "Third Party", "Deleted", "Unknown".
Time Zones JSON array specifying time zones applicable to the template.
URL String URL associated with the template, potentially for provisioning or reference.
Variables JSON array of variable objects, each possibly containing choices or options relevant to the template's configuration.

Output

The node outputs JSON data representing the updated FXS template entity as returned by the 3CX API after the update operation. This typically includes all properties of the template reflecting the new state post-update.

If the node supports binary data output (not indicated here), it would represent any file or media content related to the template, but based on the provided information, output is purely JSON.

Dependencies

  • Requires an active connection to a 3CX telephony system instance.
  • Needs an API authentication token or OAuth2 credential configured in n8n to authorize requests against the 3CX API.
  • The base URL for the 3CX server must be correctly set in the credentials.
  • The node uses HTTP requests with JSON payloads to interact with the 3CX API endpoints.

Troubleshooting

  • Invalid or missing Id: The update operation requires a valid template ID. Ensure the "Id" property is correctly set and corresponds to an existing template.
  • Malformed JSON inputs: Properties like Allowed Net Configs, Languages, Models, Time Zones, and Variables expect valid JSON arrays. Invalid JSON will cause parsing errors.
  • Authentication errors: If the API key or OAuth token is invalid or expired, the node will fail to authenticate. Refresh or reconfigure credentials as needed.
  • Permission issues: The authenticated user must have sufficient rights to update templates in 3CX.
  • Network connectivity: Ensure the n8n instance can reach the 3CX server URL specified in credentials.
  • Unsupported property values: For enumerated fields like Device Type or Template Type, use only the allowed options to avoid API rejection.

Links and References

Discussion