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 office hours settings. The "Update Office Hours" operation lets you configure working periods, break times, holidays, system language, and time zone for an office environment managed within 3CX. This is useful for businesses that want to automate or programmatically manage their call routing and availability schedules based on office hours.

Practical examples include:

  • Automatically updating office hours during holiday seasons.
  • Adjusting break times dynamically based on team schedules.
  • Changing system language or time zone settings when expanding to new regions.

Properties

Name Meaning
Break Time JSON object defining break periods within office hours. Example structure: { "Periods": [ ... ] }
Hours JSON object defining working periods (office hours). Example structure: { "Periods": [ ... ] }
Office Holidays JSON array listing dates or periods considered as holidays when office is closed.
System Language String specifying the language setting of the system (e.g., "en-US", "fr-FR").
Time Zone Id String representing the time zone identifier (e.g., "America/New_York", "Europe/London").

Output

The node outputs JSON data reflecting the result of the update operation. This typically includes confirmation of the updated office hours configuration or any error messages returned by the 3CX API. There is no indication of binary data output.

Dependencies

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

Troubleshooting

  • Invalid JSON input: Since several properties expect JSON strings parsed into objects, malformed JSON will cause errors. Ensure JSON syntax is correct.
  • Authentication errors: If the API key or OAuth2 token is missing or invalid, the node will fail to authenticate. Verify credentials are properly set.
  • Incorrect time zone or language codes: Using unsupported or incorrect identifiers may cause the API to reject the request.
  • API endpoint issues: Make sure the server URL in credentials is correct and reachable.
  • Empty or incomplete periods: Providing empty period arrays or objects without required fields might lead to unexpected behavior or errors.

Links and References

Discussion