Actions43
- Earning Types Actions
- Email Templates Actions
- Employee Types Actions
- Employees Actions
- Entities Actions
- Classes Actions
- Contacts Actions
- Department Groups Actions
- Exchange Rate Lines Actions
- Exchange Rate Types Actions
- Exchange Rates Actions
- Attachment Folders Actions
- Get Next Value Actions
- Location Groups Actions
- Locations Actions
- Roles Actions
- User Groups Actions
- Users Actions
- Affiliate Entity Groups Actions
- Attachments Actions
- Departments Actions
- Document Sequences Actions
Overview
This node operation creates a new employee record within a company's configuration in the Sage Intacct system via AvantGuard's API. It is designed to facilitate adding detailed employee information, including contact details, job-related data, payment preferences, and organizational assignments.
Common scenarios for this node include:
- Automating employee onboarding by programmatically creating employee profiles.
- Integrating HR systems with Sage Intacct to keep employee records synchronized.
- Managing complex company structures where employees have multiple attributes such as departments, locations, and payment methods.
Practical example:
- When a new hire joins, an HR workflow can trigger this node to create their employee profile with all relevant details like start date, job title, manager, and payment setup, ensuring payroll and expense reporting are correctly configured from day one.
Properties
| Name | Meaning |
|---|---|
| Primary Contact | The main contact object representing the employee, including personal info (name, emails, phones), mailing address, and company affiliation. |
| Additional Body Fields | Optional additional fields to customize the employee record, including: - Key: System-assigned unique key - Id: Unique employee ID - Name: Employee name - Start Date: Employment start date - Job Title - Status: Active or Inactive - Birth Date - End Date: Termination date - Post Actual Cost With Variance: Boolean flag for salary cost posting - Merge Payment Requests: Boolean flag for merging payment requests - Send Automatic Payment Notification: Boolean flag for expense reimbursement notifications - Manager: Manager reference object - Gender: Female or Male - Location: Work location object - Department: Department object - Class: Employee class object - Default Currency: Currency code for expenses/payments - Employee Type: Full time, part time, contractor, etc. - Earning Type: Labor cost GL account type - SSN: Social security number (no dashes) - Employee Position: Position reference (construction only) - Termination Type: Voluntary, involuntary, deceased, disability, retired - Form 1099: Tax form info - ACH: ACH payment details - Is Placeholder Resource: Boolean for project placeholders - File Payment Service: Ach, Bank File, None - Bank File: Bank file payment details - Bank File Setup: Bank account setup array - Preferred Payment Method: Printed Check, EFT, Cash, ACH - Attachment Folder: Folder for employee documents - Employee Rates: Cost rates array - Position Skills: Array of skills/positions - Audit: Creation/modification audit info - Entity: Company entity association - Href: URL endpoint for the employee record |
Output
The node outputs JSON data representing the created employee object as returned by the API. This includes all submitted fields along with any additional metadata or identifiers assigned by the backend 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 credentials.
- The node depends on the
@avantguardllc/n8n-openapi-nodepackage and the provided OpenAPI specification for request construction.
Troubleshooting
- Invalid or missing API credentials: Ensure the API key and base URL are correctly set in the node credentials.
- Malformed JSON in properties: The
primaryContactand other JSON-type fields must be valid JSON strings; invalid JSON will cause errors. - Missing required fields: The
primaryContactproperty is mandatory; omitting it will result in failure. - Incorrect field types or values: For example, dates should be in ISO format (
YYYY-MM-DD), and enumerated options must match allowed values. - API errors: If the API returns errors, check the response message for details such as duplicate keys or invalid references (e.g., non-existent department or manager).