3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

This node integrates with the 3CX telephony system, specifically allowing users to update email templates within 3CX. It is useful in scenarios where automated or programmatic management of email templates is needed, such as customizing notification emails sent by the telephony system based on dynamic data or workflow conditions.

For example, a user might update the subject and body of an email template used for conference invitations or voicemail notifications, ensuring that the content is always up-to-date and personalized without manual intervention.

Properties

Name Meaning
Template Path The key or identifier of the email template to update. Supports expressions (e.g., {{$json.TemplatePath}}).
Body The main content/body of the email template.
From The sender's email address shown in the email.
Is Conference Boolean flag indicating if the template is for a conference-related email.
Is Default Boolean flag indicating if this template should be marked as the default one.
Lang Language code for the email template (e.g., "en", "fr").
Name The display name of the email template.
Subject The subject line of the email template.

Output

The node outputs JSON data representing the response from the 3CX API after updating the email template. This typically includes confirmation details about the updated template, such as its ID, status, or any error messages returned by the API.

No binary data output is involved.

Dependencies

  • Requires an active connection to a 3CX telephony system.
  • Needs an API authentication token or OAuth2 credentials configured in n8n to authorize requests to the 3CX API.
  • The base URL for the 3CX server must be provided in the credentials configuration.

Troubleshooting

  • Invalid Template Path: If the specified template path does not exist, the API may return an error. Verify the template path value and ensure it matches an existing template.
  • Authentication Errors: Missing or invalid API credentials will cause authorization failures. Ensure the API key or OAuth2 token is correctly set up.
  • Network Issues: Connectivity problems to the 3CX server can cause request failures. Check network access and server availability.
  • Incorrect Property Values: Providing invalid values for boolean flags or language codes may result in errors. Validate input data before execution.

Links and References

Discussion