BAMBOOHR n8n INTEGRATION: AUTOMATE BAMBOOHR WITH N8N

This action allows you to programmatically add new employee records directly into BambooHR, making it essential for onboarding automation. Instead of manually entering each new hire's information, you can trigger employee creation based on events in your ATS, HRIS, or even a simple form submission.

Key parameters: First Name (required text field), Last Name (required text field), Synced with Trax Payroll (optional toggle), and Additional Fields where you can add custom fields like department, job title, hire date, email, and any custom fields configured in your BambooHR account.

Use cases: Automatically create employee records when candidates are marked as "hired" in Greenhouse or Lever, sync new employees from your payroll provider to BambooHR, or create employee records from form submissions during onboarding.

This action retrieves detailed information about a specific employee from BambooHR. It's the foundation for any workflow that needs to read employee data—whether for syncing, reporting, or conditional logic based on employee attributes.

Key parameters: Employee ID (required text field for targeting the correct record) and Options (additional configurations for filtering or specifying which fields to return).

Use cases: Fetch employee details to populate a welcome email with personalized information, check an employee's department before routing a document approval, or retrieve employee data to sync with external systems like Slack user directories.

Need to pull a list of employees for bulk operations or reporting? This action retrieves multiple employee records in a single request, with options to limit results or fetch the entire directory.

Key parameters: Return All (toggle to fetch every employee record—be mindful of API rate limits) and Limit (numeric field to cap results when "Return All" is off).

Use cases: Generate a daily employee roster for attendance systems, sync your entire employee directory with an external identity provider, or create weekly reports comparing employee counts across departments.

Employee data changes constantly—promotions, department transfers, address updates. This action lets you modify existing employee records programmatically, keeping BambooHR in sync with your other systems.

Key parameters: Employee ID (required unique identifier), Synced with Trax Payroll (optional toggle), and Update Fields (expandable section where you specify which fields to modify like job title, department, or manager).

Use cases: Automatically update job titles when promotions are approved in your HRIS, sync address changes from employee self-service portals, or update department assignments based on org chart changes in another system.

This action uploads files to your BambooHR account's general file storage. It's perfect for adding company-wide documents, templates, or resources that aren't tied to a specific employee.

Key parameters: Input Data Field Name (required, defaults to "data", specifies which field contains the file data) and Category Name or ID (optional parameter to organize the uploaded file).

Use cases: Automatically archive signed company policies from DocuSign, upload generated reports from BI tools for company-wide access, or store backup copies of important HR documents.

Retrieve a list of files from BambooHR's file storage, with options to fetch all files or limit the results. This action is useful for auditing, backup workflows, or building file inventories.

Key parameters: Return All (toggle to fetch every file—use with caution on accounts with extensive file libraries), Limit (numeric field to cap results), and Simplify (returns a cleaner data structure for easier processing).

Use cases: Create a weekly backup of all HR files to cloud storage, audit file storage for compliance reviews, or generate file inventories for annual HR audits.

This action downloads a specific file from BambooHR, making it available for processing, backup, or transfer to other systems within your workflow.

Key parameters: File ID (required unique identifier of the file to download) and Put Output In Field (specifies where to store the downloaded file data, defaults to "data").

Use cases: Download employee handbooks for automated email distribution to new hires, transfer HR documents to a backup storage system like AWS S3, or process file contents for data extraction or analysis.

Need to replace or modify metadata for an existing file? This action updates files already stored in BambooHR without requiring a delete-and-reupload workflow.

Key parameters: File ID (required unique identifier of the file to update) and Update Fields (expandable section where you can modify metadata like file name or category).

Use cases: Rename files automatically based on a standardized naming convention, recategorize files during organizational restructuring, or update file metadata when associated employee information changes.

This action removes a file from BambooHR's storage. Use it for cleanup workflows, compliance-driven data deletion, or removing outdated documents.

Key parameters: File ID (required unique identifier of the file to delete). This is a permanent action, so ensure you have the correct ID before execution.

Use cases: Automatically remove draft documents after final versions are approved, clean up expired compliance documents, or delete files associated with offboarded employees (following your retention policies).

Unlike general file uploads, this action attaches documents directly to a specific employee's record. It's essential for onboarding, where you need to file offer letters, tax forms, or ID copies under the correct employee.

Key parameters: Employee ID (required text field), Employee Document Category ID (optional field to organize the document into a category), and Input Data Field Name (required, defaults to "data", specifies the workflow field containing the file data).

Use cases: Automatically file signed offer letters from DocuSign to the correct employee record, upload tax forms (W-4, I-9) when employees complete them online, or store performance review documents after managers submit evaluations.

Retrieve a list of documents associated with one or more employees. This action is useful for auditing employee files, generating compliance reports, or preparing offboarding document packages.

Key parameters: Employee ID (optional filter for specific employee—leave blank to fetch documents across all employees), Return All (toggle to retrieve every matching document), Limit (numeric cap on results), and Simplify (returns a streamlined data structure).

Use cases: Audit that all employees have required compliance documents on file, prepare document packages for employee transfers between entities, or generate reports on missing documents during onboarding audits.

This action downloads a specific document from an employee's file, making it available for review, backup, or transfer within your workflow.

Key parameters: Employee ID (required), File ID (optional but typically needed to target the exact file), and Put Output In Field (where to store the downloaded file data, defaults to "data").

Use cases: Download signed contracts for archival in a legal document management system, retrieve tax documents for year-end processing, or export employee credentials or certifications for external verification systems.

Modify metadata or replace content for documents attached to employee records. This action keeps employee files accurate without manual intervention.

Key parameters: Employee ID (required), File ID (required unique identifier of the document to update), and Update Fields (expandable section for specifying which attributes to modify, such as document name or category).

Use cases: Rename documents to follow a standardized naming convention, recategorize documents when HR filing structures change, or update document metadata after employee name changes (marriage, legal name change).

Permanently remove a document from an employee's record. This is critical for compliance workflows where outdated or incorrect documents must be removed.

Key parameters: Employee ID (required) and File ID (required unique identifier of the document to remove, must be entered as an expression).

Use cases: Remove superseded documents when new versions are signed, delete incorrect uploads immediately after discovery, or clean up employee files during offboarding (following retention requirements).

BambooHR's custom reports are powerful, but manually exporting them gets tedious. This action programmatically retrieves company reports, enabling scheduled reporting and automated distribution.

Key parameters: Report ID (required unique identifier—find this in the report URL when viewing it in BambooHR), Format (required output format, defaults to JSON which works seamlessly with n8n's data processing), and Options (additional configurations for customizing the report output).

Use cases: Generate weekly headcount reports and send them to leadership via Slack or email through n8n, export payroll data reports for processing in external payroll systems, or create scheduled compliance reports and store them in SharePoint for auditors.