AvantGuard - Sage Intacct (Company Configuration) icon

AvantGuard - Sage Intacct (Company Configuration)

AvantGuard - Sage Intacct (Company Configuration)

Actions43

Overview

This node operation creates a new user within a company's configuration in the Sage Intacct system. It is designed to facilitate the addition of users with detailed profile information, permissions, and access controls tailored to the organization's needs.

Common scenarios where this node is beneficial include:

  • Automating user onboarding by programmatically creating user accounts with predefined roles and permissions.
  • Integrating HR or identity management systems with Sage Intacct to synchronize user data.
  • Managing user access and security settings centrally through workflows.

Practical example:
A company wants to automatically create employee user accounts in Sage Intacct when new hires are added to their HR system. This node can be used to send all necessary user details, including contact info, roles, and permissions, ensuring consistent setup without manual intervention.

Properties

Name Meaning
Id User login ID. This unique identifier cannot be changed after the user is created.
Account Email User email address.
Contact JSON object containing detailed contact information such as name, emails, phone numbers, company name, and mailing address.
Additional Body Fields Optional additional fields for the user creation request. Includes:
- Key: System-assigned unique key for the user.
- User Name: Display name for the user.
- User Type: Defines maximum feature access; options include Business, Employee, View Only, Dashboard, Project Manager, Payment Approver, Platform, CRM, Warehouse, Construction Manager.
- Admin Privileges: Off, Limited, Full.
- Status: Active, Inactive, Locked Out.
- Web Services: JSON defining API access.
- Password: JSON defining password properties.
- SSO: JSON for single sign-on settings.
- Entity Access: JSON for entity-level restrictions.
- Trusted Devices: Company Default, Always, Never.
- Is Chatter Disabled: Boolean to disable collaboration feature.
- Hide Other Department Transactions: Boolean to restrict transaction visibility.
- Locations, Departments, Territories, Roles, Permission Assignments: JSON arrays defining user's organizational scope and permissions.
- Audit: JSON with creation/modification metadata.
- Entity: JSON defining associated entity.
- Href: URL endpoint for the user.

Output

The node outputs JSON data representing the newly created user object as returned by the Sage Intacct API. This includes all user details submitted plus any system-generated fields such as keys or timestamps.

If the node supports binary data output (not indicated here), it would typically represent files or attachments related to the user, but this operation focuses on JSON user data only.

Dependencies

  • Requires an API key credential for authenticating with the Sage Intacct API.
  • The base URL for the API must be configured in the node credentials.
  • The node depends on the @avantguardllc/n8n-openapi-node package for building requests based on the OpenAPI specification.
  • Network connectivity to the Sage Intacct service endpoint is required.

Troubleshooting

  • Invalid or missing required fields: Ensure that mandatory properties like id, accountEmail, and contact are provided and correctly formatted.
  • Authentication errors: Verify that the API key credential is valid and has sufficient permissions to create users.
  • Status field restrictions: The inactive status cannot be used when creating a new user; use active or lockedOut instead.
  • JSON parsing errors: For properties expecting JSON input (e.g., contact, webServices), ensure the JSON is well-formed.
  • Permission issues: If the user type or admin privileges are set inconsistently (e.g., full admin privileges without business user type), the API may reject the request.
  • API rate limits or network issues: Check connectivity and API usage quotas if requests fail unexpectedly.

Links and References

Discussion