3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

This node integrates with the 3CX telephony system to update emergency notification settings. It allows users to configure who receives chat notifications during emergencies, specify prompts for emergency dial numbers and playback messages, and define a custom list of recipients. This is useful in scenarios where organizations need to quickly adjust their emergency communication preferences within the 3CX system, such as updating alert groups or changing voice prompts.

Practical examples:

  • Updating the group of users who receive emergency chat alerts.
  • Changing the audio prompt played during an emergency call.
  • Specifying a custom list of contacts to notify in case of an emergency.

Properties

Name Meaning
Chat Recipients Selects which group receives emergency chat notifications. Options: None, My Group Managers, My Group All Members, All Groups Managers.
Emergency DN Prompt JSON object defining membership and tags related to emergency dial number prompts.
Emergency Play Prompt String specifying the audio prompt to play during emergency calls.
Specified List Custom string list specifying particular recipients for emergency notifications.

Output

The node outputs JSON data reflecting the updated emergency notification settings as returned by the 3CX API. The structure corresponds to the properties sent in the request, confirming the applied configuration changes.

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.
  • The base URL for the 3CX API must be set in the credentials.

Troubleshooting

  • Invalid JSON in Emergency DN Prompt: Since this property expects valid JSON, malformed input will cause errors. Ensure the JSON syntax is correct.
  • Authentication Errors: If the OAuth2 token is missing or expired, the node will fail to connect. Refresh or reconfigure credentials as needed.
  • Invalid Recipient Option: Selecting an unsupported option for Chat Recipients may cause the API to reject the request.
  • Empty Required Fields: Some fields might be mandatory depending on the 3CX setup; ensure all required properties are provided.

Links and References

Discussion