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, assigning appropriate roles, departments, and permissions 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, mailing address, and URLs.
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: Type of user (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: JSON array of allowed locations.
- Departments: JSON array of allowed departments.
- Territories: JSON array of assigned territories.
- Roles: JSON array of assigned roles.
- Permission Assignments: JSON array defining permissions and access rights.
- Audit: JSON with audit info.
- 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 additional metadata or identifiers assigned by the system.

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 node uses the base URL provided in the credentials to send requests to the Sage Intacct Company Configuration API endpoint.
  • The node depends on the @avantguardllc/n8n-openapi-node package for building and sending OpenAPI-based requests.

Troubleshooting

  • Missing Required Fields: Errors may occur if required fields like id, accountEmail, or contact are missing or malformed. Ensure these are correctly provided.
  • Invalid JSON Format: Properties expecting JSON input (e.g., contact, webServices, password) must be valid JSON strings. Invalid JSON will cause parsing errors.
  • Permission Issues: If the API key lacks sufficient permissions, the user creation request may fail. Verify that the API key has rights to create users.
  • User ID Conflicts: Attempting to create a user with an existing id will result in an error. Use unique user IDs.
  • Status Field Restrictions: Setting status to inactive when creating a new user is not allowed; use active or omit to default.
  • Admin Privileges Constraints: Full or limited admin privileges require the user type to be business. Mismatched settings will cause validation errors.

Links and References

Discussion