AvantGuard - Sage Intacct (Company Configuration) icon

AvantGuard - Sage Intacct (Company Configuration)

AvantGuard - Sage Intacct (Company Configuration)

Actions43

Overview

This node is designed to create a company configuration email template within the "Email Templates" resource, specifically for the operation "Create Company Config Email Template." It allows users to define and send customized email templates related to company configurations. This can be useful in scenarios where automated emails need to be generated and sent as part of company setup or configuration workflows, such as onboarding new clients, notifying teams about configuration changes, or sending templated status updates.

Properties

Name Meaning
Additional Body Fields Optional additional fields to include in the body of the email template. Currently supports adding an "Email" field as a string.

The "Additional Body Fields" property is a collection that lets you add extra data fields to the email body. For example, you can specify an email address to be included dynamically in the template.

Output

The node outputs JSON data representing the result of creating the company configuration email template. The exact structure depends on the API response but typically includes details about the created template such as its ID, status, and any metadata returned by the service.

If the node supports binary data output (not evident from the provided code), it would represent attachments or other binary content related to the email template.

Dependencies

  • Requires an API key credential for authentication with the AvantGuard Sage Intacct Company Configuration API.
  • The base URL for the API is configured via credentials.
  • Uses the @avantguardllc/n8n-openapi-node package and an OpenAPI specification (openapi.json) bundled with the node for request building and validation.

Troubleshooting

  • Authentication errors: Ensure the API key credential is correctly set up and has the necessary permissions.
  • Invalid input data: Verify that all required properties are provided and correctly formatted, especially any additional body fields.
  • API connectivity issues: Check network access to the configured base URL and confirm the API endpoint is reachable.
  • Unexpected API responses: Review the API documentation for expected request formats and response structures; enable debug logging if available to inspect raw requests and responses.

Links and References

Discussion