3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

This node integrates with the 3CX telephony system, specifically allowing batch updates to multiple user records simultaneously. It is useful in scenarios where an administrator needs to update settings or configurations for several users at once, such as modifying forwarding rules, greetings, group memberships, or transcription modes across a set of users. For example, updating call forwarding exceptions or group rights for a list of user IDs in one operation saves time compared to updating each user individually.

Properties

Name Meaning
Ids A JSON array containing the IDs of the users to be updated. Each ID identifies a user record in the 3CX system.
User A JSON object representing the user data to apply to all specified users. This includes complex nested structures such as:
- ForwardingExceptions: Rules for call forwarding exceptions including destinations and active hours.
- ForwardingProfiles: Call routing profiles for busy, no answer, or not registered states.
- Greetings: Audio or message greetings associated with the user.
- Groups: Group memberships and associated rights and tags.
- TranscriptionMode: Settings related to call transcription.
Users provide this data as a JSON string which is parsed and sent in the request body.

Output

The node outputs JSON data representing the response from the 3CX API after attempting to update the specified users. The structure typically includes success or error information per user updated. There is no indication that binary data is output by this node.

Dependencies

  • Requires an API authentication token credential configured in n8n to authenticate requests against the 3CX telephony system.
  • The base URL for the 3CX API must be provided via credentials.
  • The node sends HTTP requests to the 3CX API endpoint /xapi/v1.

Troubleshooting

  • Invalid JSON input: Since the Ids and User properties expect JSON strings that are parsed before sending, malformed JSON will cause errors. Ensure valid JSON formatting.
  • Authentication errors: If the API key or OAuth2 token is missing or invalid, the node will fail to authenticate. Verify credentials configuration.
  • API endpoint issues: Incorrect or unreachable base URL will cause connection failures. Confirm the server URL is correct and accessible.
  • Partial updates: If some user IDs do not exist or have permission restrictions, the API may return partial success or errors. Check the response details for individual user update statuses.

Links and References

Discussion