Actions43
- Location Groups Actions
- Locations Actions
- Roles Actions
- User Groups Actions
- Users Actions
- Affiliate Entity Groups Actions
- Attachments Actions
- Classes Actions
- Contacts Actions
- Department Groups Actions
- Departments Actions
- Document Sequences Actions
- Earning Types Actions
- Email Templates Actions
- Employee Types Actions
- Employees Actions
- Entities Actions
- Exchange Rate Lines Actions
- Exchange Rate Types Actions
- Exchange Rates Actions
- Attachment Folders Actions
- Get Next Value Actions
Overview
This node integrates with the AvantGuard Sage Intacct Company Configuration API to create a new employee record within a company's configuration. It is designed for scenarios where users need to programmatically add detailed employee information into their Sage Intacct system, such as during onboarding automation or bulk employee data imports.
Practical examples include:
- Automating the creation of employee profiles when new hires are added in an HR system.
- Synchronizing employee data from external systems into Sage Intacct.
- Setting up complex employee configurations including contact details, payment preferences, and organizational assignments.
Properties
| Name | Meaning |
|---|---|
| Primary Contact | The main contact object representing the employee, including personal details like name, emails, phone numbers, mailing address, and company affiliation. |
| Additional Body Fields | Optional additional fields to customize the employee record. These include: - Key: System-assigned unique key for the employee - Id: Unique employee ID - Name: Employee's full name - Start Date: Employment start date - Job Title: Employee's job title - Status: Active or Inactive status - Birth Date: Date of birth - End Date: Employment termination date - Post Actual Cost With Variance: Boolean flag related to salary cost posting - Merge Payment Requests: Boolean flag to allow merging payment requests - Send Automatic Payment Notification: Boolean flag for expense reimbursement notifications - Manager: JSON object representing the employee's manager - Gender: Female or Male - Location: JSON object specifying work location - Department: JSON object for department assignment - Class: JSON object for employee class association - Default Currency: Currency code for expenses/payments - Employee Type: JSON object defining employment status (full-time, part-time, contractor) - Earning Type: JSON object specifying labor cost GL accounts - SSN: Social security number without dashes - Employee Position: JSON object for position reference (construction-specific) - Termination Type: Voluntary, involuntary, deceased, disability, retired - Form 1099: JSON object with tax form info - ACH: JSON object with ACH payment details - Is Placeholder Resource: Boolean to mark as placeholder resource (Projects app) - File Payment Service: Ach, Bank File, None - Bank File: JSON object with bank file payment details - Bank File Setup: JSON array configuring bank file setup - Preferred Payment Method: Printed Check, EFT, Cash, ACH - Attachment Folder: JSON object for document storage folder - Employee Rates: JSON array of cost rates - Position Skills: JSON array of associated skills/positions - Audit: JSON object with audit metadata - Entity: JSON object associating the employee with an entity - Href: URL endpoint for the employee record |
Output
The node outputs a JSON object representing the newly created employee record as returned by the Sage Intacct API. This includes all submitted fields along with any additional metadata or identifiers assigned by the system.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the AvantGuard Sage Intacct API.
- The base URL for the API must be configured in the node credentials.
- Uses the
@avantguardllc/n8n-openapi-nodepackage for OpenAPI integration. - The node expects JSON-formatted input for complex properties such as contacts, managers, locations, etc.
Troubleshooting
- Invalid JSON Input: Since many properties require JSON strings, malformed JSON will cause errors. Ensure JSON inputs are correctly formatted.
- Missing Required Fields: The "Primary Contact" property is mandatory. Omitting it or providing incomplete contact details may result in API errors.
- Authentication Errors: Incorrect or missing API credentials will prevent successful requests.
- Field Validation Errors: Providing invalid values for enumerated options (e.g., status, gender, termination type) can cause failures.
- API Endpoint Issues: Ensure the base URL in credentials is correct and accessible.
- Data Type Mismatches: Boolean fields must be true/false, dates should be in ISO format (YYYY-MM-DD).