Important: This documentation covers Yarn 1 (Classic).
For Yarn 2+ docs and migration guide, see yarnpkg.com.

Package detail

@avantguardllc/n8n-nodes-sageintacct

AvantGuardLLC100MIT0.1.5TypeScript support: included

@avantguardllc/n8n-nodes-sageintacct

n8n-community-node-package, MSP, Sage Intacct

readme

Banner image

n8n-nodes-starter

This repo contains example nodes to help you get started building your own custom integrations for n8n. It includes the node linter and other dependencies.

To make your custom node available to the community, you must create it as an npm package, and submit it to the npm registry.

Prerequisites

You need the following installed on your development machine:

  • git
  • Node.js and pnpm. Minimum version Node 18. You can find instructions on how to install both using nvm (Node Version Manager) for Linux, Mac, and WSL here. For Windows users, refer to Microsoft's guide to Install NodeJS on Windows.
  • Install n8n with:
    pnpm install n8n -g
  • Recommended: follow n8n's guide to set up your development environment.

Using this starter

These are the basic steps for working with the starter. For detailed guidance on creating and publishing nodes, refer to the documentation.

  1. Generate a new repository from this template repository.
  2. Clone your new repo:
    git clone https://github.com/<your organization>/<your-repo-name>.git
  3. Run pnpm i to install dependencies.
  4. Open the project in your editor.
  5. Browse the examples in /nodes and /credentials. Modify the examples, or replace them with your own nodes.
  6. Update the package.json to match your details.
  7. Run pnpm lint to check for errors or pnpm lintfix to automatically fix errors when possible.
  8. Test your node locally. Refer to Run your node locally for guidance.
  9. Replace this README with documentation for your node. Use the README_TEMPLATE to get started.
  10. Update the LICENSE file to use your details.
  11. Publish your package to npm.

More information

Refer to our documentation on creating nodes for detailed information on building your own nodes.

License

MIT

changelog

Changes

[Unreleased]

Added

  • Group optional parameters in collections: Required parameters are now displayed directly in the UI, while optional parameters are grouped under "Additional Query Parameters" and "Additional Body Fields" collections with "Add Field" functionality.

Changed

  • Modified the parseFields method in OperationsCollector.ts to separate parameters into required and optional groups.
  • Required parameters are now shown directly in the UI.
  • Optional query parameters are now grouped under an "Additional Query Parameters" collection field.
  • Optional body fields are now grouped under an "Additional Body Fields" collection field.
  • Added tests to verify this behavior.

Benefits

  • Cleaner UI with only required parameters shown by default.
  • All optional parameters remain accessible through the "Add Field" functionality.
  • Better organization of parameters based on importance.
  • Maintains all the routing information and parameter types correctly.

Usage

When generating n8n node properties from OpenAPI specifications:

  • Only required parameters will be shown by default in the n8n UI.
  • Optional parameters will be available through "Additional Query Parameters" or "Additional Body Fields" sections.
  • Users can click "Add Field" to select and configure optional parameters as needed.