3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

The node provides functionality to retrieve an email template by its path key from a 3CX telephony system. This operation is useful when you want to dynamically fetch and use predefined email templates stored in the 3CX system, for example, to send customized notifications or alerts based on specific events or triggers within your workflow.

Practical examples include:

  • Fetching a welcome email template to send to new users.
  • Retrieving notification templates for call summaries or voicemail alerts.
  • Dynamically loading templates for marketing campaigns managed within 3CX.

Properties

Name Meaning
Template Path The unique key or path identifying the email template to retrieve. Supports expressions.
Options Additional query options:
- Select Comma-separated list of properties to return from the email template (e.g., Id, Name).
- Expand Comma-separated list of related entities to expand and include in the response.

Output

The node outputs JSON data representing the requested email template. The structure includes the properties of the email template as returned by the 3CX API, potentially filtered or expanded according to the provided options.

If binary data were involved (e.g., attachments), it would be included in a separate binary output field, but this node focuses on JSON data retrieval only.

Dependencies

  • Requires connection to a 3CX telephony system API.
  • Needs an API authentication token configured via credentials in n8n.
  • The base URL for the 3CX API must be set in the node credentials.
  • The node sends HTTP requests with appropriate headers to the 3CX API endpoint.

Troubleshooting

  • Common issues:
    • Invalid or missing Template Path will cause the request to fail.
    • Incorrect API credentials or expired tokens will result in authentication errors.
    • Network connectivity problems to the 3CX server can cause timeouts or unreachable errors.
  • Error messages:
    • Authentication failures typically indicate invalid or missing API keys; verify credentials.
    • "Template not found" errors suggest the Template Path does not exist; check the key spelling and availability.
    • Malformed query parameters in Options may cause bad request errors; ensure correct formatting.

Links and References

Discussion