HARVEST n8n INTEGRATION: AUTOMATE HARVEST WITH N8N

This action lets you modify existing user profiles in your Harvest account directly from your n8n workflows. It's particularly valuable for keeping user information synchronized across multiple platforms or for bulk-updating team member details when organizational changes occur.

Key parameters: Credential to connect with (select your Harvest account credentials, required), Resource (set to "User"), Operation (set to "Update"), Account Name or ID (specify which Harvest account to target, required), Time Entry ID (optional field for linking updates to specific time entries), Update Fields (dynamic section where you add specific properties to modify: first name, last name, email, roles, etc.).

Use cases: Automatically update user roles when someone gets promoted in your HR system, sync email addresses when team members update their contact info in your central directory, bulk-deactivate users when they leave the company.

This action retrieves detailed information about the currently authenticated user—the person whose credentials are being used for the API connection. It's the quickest way to verify your connection and grab user-specific data for personalized workflows.

Key parameters: Credential to connect with (your authenticated Harvest account, required), Resource (set to "User"), Operation (set to "Me" to fetch the authenticated user's details), Account Name or ID (the target Harvest account, required).

Use cases: Verify API connection at the start of complex workflows, fetch the current user's ID to filter their specific time entries or projects, build personalized dashboards showing the authenticated user's data.

Need to pull a list of team members? This action retrieves multiple user records from your Harvest account with full control over pagination and filtering. Perfect for building team reports, syncing user directories, or auditing account access.

Key parameters: Credential to connect with (your Harvest credentials, required), Resource (set to "User"), Operation (set to "Get Many"), Account Name or ID (target account, required), Return All (toggle to fetch all users or limit results), Limit (maximum number of users to return, default 100), Filters (add conditions to narrow down results: active status, etc.).

Use cases: Weekly sync of all active users to your team management tool, generate a report of all team members for capacity planning, audit user access across your Harvest accounts.

When you need details about a specific team member, this action fetches comprehensive data for a single user by their ID. Unlike "Get Many," this targets one record precisely—ideal when you already know who you're looking for.

Key parameters: Credential to connect with (Harvest authentication, required), Resource (set to "User"), Operation (set to "Get"), Account Name or ID (the relevant Harvest account, required), User ID (the unique identifier of the user to retrieve, required).

Use cases: Look up a user's details after receiving their ID from a previous workflow step, verify user existence before attempting updates, fetch specific user data for personalized notifications.

This action removes a user from your Harvest account. Use it carefully—this is typically reserved for cleanup operations when team members depart or for removing test accounts during development.

Key parameters: Credential to connect with (Harvest credentials, required), Resource (set to "User"), Operation (set to "Delete"), Account Name or ID (target account, required), User ID (the specific user to delete, required).

Use cases: Automated offboarding workflow when HR systems flag departures, clean up test users after development cycles, remove duplicate user entries during data cleanup.

Onboarding new team members? This action creates new user profiles in Harvest, complete with all the details needed to get them tracking time immediately. Perfect for automated onboarding sequences.

Key parameters: Credential to connect with (Harvest authentication, required), Resource (set to "User"), Operation (set to "Create"), Account Name or ID (target account, required), First Name (new user's first name, optional but recommended), Last Name (new user's last name, optional but recommended), Email (user's email address, typically required for account access), Additional Fields (add roles, permissions, cost rates, and other profile details).

Use cases: Automatically create Harvest users when new employees are added to your HR system, bulk-create users when onboarding a new client's team, set up contractor accounts when new projects begin.

Modify existing time entries to correct mistakes, add notes, or update billing information. This action is essential for maintaining accurate time records and ensuring proper invoicing.

Key parameters: Credential to connect with (Harvest credentials, required), Resource (set to "Time Entry"), Operation (set to "Update"), Account Name or ID (target account, required), Time Entry ID (the specific entry to modify, required), Update Fields (add fields to modify: hours, notes, project, task, billable status, etc.).

Use cases: Automatically mark time entries as billable when project managers approve them, update notes on time entries based on Slack messages or comments, correct project assignments in bulk after categorization errors.

Currently tracking time? This action stops an active timer on a specific time entry. It's the automation equivalent of clicking the stop button in Harvest, useful for workflows that manage time tracking based on external triggers.

Key parameters: Credential to connect with (Harvest authentication, required), Resource (set to "Time Entry"), Operation (set to "Stop"), Account Name or ID (target account, required), Time Entry ID (the running timer to stop, required).

Use cases: Stop timers automatically when a Slack status changes to "Away," end tracking when a Jira ticket moves to "Done," implement automatic end-of-day timer shutoff.

Resume a previously stopped time entry with this action. Useful for break management or when work resumes on a paused task.

Key parameters: Credential to connect with (Harvest credentials, required), Resource (set to "Time Entry"), Operation (set to "Restart"), Account Name or ID (target account, required), Time Entry ID (the stopped entry to resume, required).

Use cases: Restart timers when Slack status changes back to "Active," resume tracking when a paused Jira ticket reopens, implement lunch break automation (stop at noon, restart at 1 PM).

Pull multiple time entries with sophisticated filtering options. This is your go-to action for reporting, analysis, and syncing time data with other systems.

Key parameters: Credential to connect with (Harvest authentication, required), Resource (set to "Time Entry"), Operation (set to "Get Many"), Account Name or ID (target account, required), Return All (toggle to fetch all entries or limit results), Limit (maximum entries to return, default 100), Filters (filter by date range, user, project, client, billable status, etc.).

Use cases: Generate weekly timesheets for payroll processing, sync billable hours to your invoicing system, build project status dashboards with real-time time data.

Fetch detailed information about a single time entry. Use this when you need specific entry data, perhaps after receiving an ID from a webhook or previous workflow step.

Key parameters: Credential to connect with (Harvest credentials, required), Resource (set to "Time Entry"), Operation (set to "Get"), Account Name or ID (target account, required), Time Entry ID (the specific entry to retrieve, required).

Use cases: Look up entry details after receiving a time entry ID from a notification, verify entry data before performing updates, fetch entry information for approval workflows.

Time entries in Harvest can have external references linking them to other systems. This action removes those references—useful when cleaning up integrations or correcting mistaken links.

Key parameters: Credential to connect with (Harvest authentication, required), Resource (set to "Time Entry"), Operation (set to "Delete External Reference"), Account Name or ID (target account, required), Time Entry ID (the entry whose external reference to remove, required).

Use cases: Clean up orphaned references when decommissioning integrated tools, correct mistaken external links on time entries, prepare entries for re-linking to different external systems.

Permanently remove a time entry from Harvest. This action deletes the record entirely—use it for cleanup operations or removing erroneous entries.

Key parameters: Credential to connect with (Harvest credentials, required), Resource (set to "Time Entry"), Operation (set to "Delete"), Account Name or ID (target account, required), Time Entry ID (the entry to delete, required).

Use cases: Remove test entries after workflow development, delete duplicate entries from import errors, clean up rejected time entries after review.

Create new time entries by specifying exact start and end times. This method is ideal when you have precise timestamps from external systems—like calendar events from Google Calendar or project management tools.

Key parameters: Credential to connect with (Harvest authentication, required), Resource (set to "Time Entry"), Operation (set to "Create via Start and End Time"), Account Name or ID (target account, required), Project ID (the project to log time against, required), Task ID (the specific task within the project, required), Spent Date (the date the time was spent), Additional Fields (start time, end time, notes, billable status, user assignment, etc.).

Use cases: Auto-log meeting time from Google Calendar or Outlook events, create time entries from Toggl exports with precise timestamps, convert call logs into time entries with exact durations.

Create time entries by specifying a duration in hours rather than start/end times. This simpler method works well when you know how long something took but don't have exact timestamps.

Key parameters: Credential to connect with (Harvest credentials, required), Resource (set to "Time Entry"), Operation (set to "Create via Duration"), Account Name or ID (target account, required), Project ID (target project, required), Task ID (target task, required), Spent Date (date of the time entry), Additional Fields (hours, notes, billable status, user, external reference, etc.).

Use cases: Log fixed-duration tasks automatically (daily standups, weekly reviews), create time entries from estimated project phases, batch-import historical time data with known durations.

Modify existing task definitions in Harvest. Tasks are the categories within projects that users select when logging time—keeping them updated ensures accurate tracking.

Key parameters: Credential to connect with (Harvest authentication, required), Resource (set to "Task"), Operation (set to "Update"), Account Name or ID (target account, required), Task ID (the task to modify, required), Update Fields (name, default hourly rate, billable status, etc.).

Use cases: Sync task names when project phases change, update billing rates across all instances of a task type, toggle billable status when project contracts change.

Retrieve a list of tasks from your Harvest account. Use this for building task selection dropdowns, syncing task libraries, or auditing your task structure.

Key parameters: Credential to connect with (Harvest credentials, required), Resource (set to "Task"), Operation (set to "Get Many"), Account Name or ID (target account, required), Return All (fetch all tasks or limit results), Limit (maximum number to return, default 100), Filters (filter by active status, updated date, etc.).

Use cases: Populate task selection options in custom forms, sync Harvest tasks with project management tool task types, generate reports on task usage across projects.

Fetch details about a specific task by its ID. This targeted lookup is useful when you need information about a particular task for conditional logic or updates.

Key parameters: Credential to connect with (Harvest authentication, required), Resource (set to "Task"), Operation (set to "Get"), Account Name or ID (target account, required), Task ID (the specific task to retrieve, required).

Use cases: Verify task existence before assigning it to a project, fetch task details for logging or notification purposes, check current task settings before making updates.

Remove a task from your Harvest account. Note that this affects the task globally—use with caution if the task might be in use on existing projects.

Key parameters: Credential to connect with (Harvest credentials, required), Resource (set to "Task"), Operation (set to "Delete"), Account Name or ID (target account, required), Task ID (the task to delete, required).

Use cases: Clean up unused task types from legacy projects, remove duplicate tasks during account optimization, delete test tasks after development.

Create new task types in your Harvest account. Tasks define the categories of work users can log time against—creating them programmatically helps maintain consistency across projects.

Key parameters: Credential to connect with (Harvest authentication, required), Resource (set to "Task"), Operation (set to "Create"), Account Name or ID (target account, required), Name (the task name, required), Additional Fields (default hourly rate, billable status, active status).

Use cases: Auto-create task types when new service offerings launch, sync task categories from project management templates, bulk-create tasks when setting up new client accounts.

Update existing project details in Harvest. This action lets you modify project settings, budgets, billing information, and more—keeping your Harvest projects in sync with reality.

Key parameters: Credential to connect with (Harvest credentials, required), Resource (set to "Project"), Operation (set to "Update"), Account Name or ID (target account, required), Project ID (the project to modify, required), Update Fields (name, code, client, budget, billing method, notes, dates, etc.).

Use cases: Update project budgets when contracts change, modify billing rates based on new agreements, change project status when phases complete.

Retrieve a list of projects from your Harvest account. Essential for building project selection interfaces, generating reports, or syncing project data to other systems.

Key parameters: Credential to connect with (Harvest authentication, required), Resource (set to "Project"), Operation (set to "Get Many"), Account Name or ID (target account, required), Return All (fetch all projects or limit), Limit (maximum to return, default 100), Filters (filter by active status, client, date ranges, etc.).

Use cases: Weekly project status sync to management dashboards, populate project dropdowns in custom intake forms, generate capacity reports across all active projects.

Fetch comprehensive details about a specific project. Use this when you need full project information for reporting, validation, or conditional workflow logic.

Key parameters: Credential to connect with (Harvest credentials, required), Resource (set to "Project"), Operation (set to "Get"), Account Name or ID (target account, required), Project ID (the project to retrieve, required).

Use cases: Verify project settings before assigning new team members, fetch budget remaining for status notifications, check project details for invoice generation.

Remove a project from Harvest. This is a significant action—typically used for cleanup or when projects are definitively cancelled. Consider archiving instead if you might need historical data.

Key parameters: Credential to connect with (Harvest authentication, required), Resource (set to "Project"), Operation (set to "Delete"), Account Name or ID (target account, required), Project ID (the project to delete, required).

Use cases: Clean up cancelled projects after confirmation, remove duplicate projects from import errors, delete test projects after development cycles.

Create new projects in Harvest with full configuration options. This action enables automated project setup based on CRM deals, signed contracts, or project management system triggers.

Key parameters: Credential to connect with (Harvest credentials, required), Resource (set to "Project"), Operation (set to "Create"), Account Name or ID (target account, required), Name (project name, required), Client ID (associate with a client, optional but recommended), Is Billable (toggle for billable status), Bill By (billing method: None, People, Project, Tasks), Budget By (budget tracking method: None, Hours per Project, Hours per Task, etc.), Additional Fields (code, dates, notes, budget amount, hourly rate, and more).

Use cases: Auto-create Harvest projects when deals close in your CRM, set up projects from Asana or ClickUp when status changes to "Active," batch-create projects from contract management system approvals.

Modify existing invoices in Harvest. Use this for correcting details, updating statuses, or adjusting line items before sending to clients.

Key parameters: Credential to connect with (Harvest authentication, required), Resource (set to "Invoice"), Operation (set to "Update"), Account Name or ID (target account, required), Invoice ID (the invoice to modify, required), Update Fields (subject, notes, issue date, due date, purchase order, tax rates, etc.).

Use cases: Update invoice notes with payment reminders automatically, adjust due dates based on client communication, add purchase order numbers when received from clients.

Retrieve multiple invoices from Harvest with filtering options. Perfect for financial reporting, payment tracking, and syncing invoice data with accounting systems.

Key parameters: Credential to connect with (Harvest credentials, required), Resource (set to "Invoice"), Operation (set to "Get Many"), Account Name or ID (target account, required), Return All (fetch all or limit), Limit (maximum to return, default 100), Filters (filter by status, client, date ranges, etc.).

Use cases: Weekly sync of unpaid invoices to a payment tracking dashboard, export invoices to QuickBooks or Xero for accounting, generate accounts receivable reports.

Fetch complete details about a specific invoice. Use this when you need full invoice information for payment processing, reporting, or client communication.

Key parameters: Credential to connect with (Harvest authentication, required), Resource (set to "Invoice"), Operation (set to "Get"), Account Name or ID (target account, required), Invoice ID (the specific invoice to retrieve, required).

Use cases: Fetch invoice details for payment confirmation emails, verify invoice amounts before processing in accounting, check invoice status for overdue payment workflows.

Remove an invoice from Harvest. Use this for draft invoices that won't be sent or for cleanup of test data.

Key parameters: Credential to connect with (Harvest credentials, required), Resource (set to "Invoice"), Operation (set to "Delete"), Account Name or ID (target account, required), Invoice ID (the invoice to delete, required).

Use cases: Delete draft invoices that were created in error, clean up test invoices from development, remove duplicate invoices from automation errors.

Generate new invoices in Harvest automatically. This powerful action enables automated billing workflows based on time entries, project milestones, or calendar triggers.

Key parameters: Credential to connect with (Harvest authentication, required), Resource (set to "Invoice"), Operation (set to "Create"), Account Name or ID (target account, required), Client ID (the client to invoice, required), Additional Fields (subject, notes, issue date, due date, payment terms, line items, etc.).

Use cases: Generate monthly invoices automatically on the first of each month, create invoices when project milestones complete, auto-bill retainer clients at regular intervals.

Modify existing expense records in Harvest. Keep expense data accurate by updating categories, amounts, or billing status as needed.

Key parameters: Credential to connect with (Harvest credentials, required), Resource (set to "Expense"), Operation (set to "Update"), Account Name or ID (target account, required), Invoice ID (optional—link expense to an invoice), Update Fields (category, amount, notes, billable status, receipt, etc.).

Use cases: Mark expenses as billable when approved by project managers, update expense categories after receipt review, link expenses to invoices during billing preparation.

Retrieve multiple expense records with filtering. Essential for expense reporting, reimbursement processing, and billing preparation.

Key parameters: Credential to connect with (Harvest authentication, required), Resource (set to "Expense"), Operation (set to "Get Many"), Account Name or ID (target account, required), Return All (fetch all or limit), Limit (maximum to return, default 100), Filters (filter by user, project, date range, billable status, etc.).

Use cases: Weekly expense sync to accounting software, generate per-project expense reports for client billing, compile reimbursement batches for payroll.

Fetch details about a specific expense by its ID. Use this for targeted lookups when verifying or processing individual expense records.

Key parameters: Credential to connect with (Harvest credentials, required), Resource (set to "Expense"), Operation (set to "Get"), Account Name or ID (target account, required), Expense ID (the specific expense to retrieve, required).

Use cases: Verify expense details before approval workflows, fetch receipt information for audit processes, check expense status before invoice generation.

Remove an expense record from Harvest. Use for cleanup of erroneous entries or cancelled expenses.

Key parameters: Credential to connect with (Harvest authentication, required), Resource (set to "Expense"), Operation (set to "Delete"), Account Name or ID (target account, required), Expense ID (the expense to delete, required).

Use cases: Delete duplicate expense entries, remove expenses rejected during approval, clean up test expenses after development.

Log new expenses in Harvest automatically. Connect to receipt scanning apps, credit card feeds, or expense report systems to automate expense tracking.

Key parameters: Credential to connect with (Harvest credentials, required), Resource (set to "Expense"), Operation (set to "Create"), Account Name or ID (target account, required), Project ID (link to a project, optional), Expense Category ID (categorize the expense, optional), Spent Date (when the expense occurred), Additional Fields (amount, notes, billable status, receipt attachment, etc.).

Use cases: Auto-log expenses from Expensify or Receipt Bank, create expense entries from credit card transaction feeds, log mileage expenses from travel tracking apps.

Modify existing estimates in Harvest. Keep your quotes current by updating line items, amounts, or client details as negotiations progress.

Key parameters: Credential to connect with (Harvest authentication, required), Resource (set to "Estimate"), Operation (set to "Update"), Account Name or ID (target account, required), Invoice ID (the estimate ID to modify, required), Update Fields (subject, notes, line items, amounts, dates, etc.).

Use cases: Update estimate amounts after scope discussions, modify line items based on client feedback, change estimate status after client decisions.

Retrieve multiple estimates from Harvest. Useful for pipeline reporting, win/loss analysis, and syncing estimate data with CRM systems.

Key parameters: Credential to connect with (Harvest credentials, required), Resource (set to "Estimate"), Operation (set to "Get Many"), Account Name or ID (target account, required), Return All (fetch all or limit), Limit (maximum to return, default 100), Filters (filter by client, status, date ranges, etc.).

Use cases: Sync pending estimates to CRM pipeline reports, generate win/loss analysis from estimate outcomes, track estimate conversion rates over time.

Fetch complete details about a specific estimate. Use when you need full estimate information for follow-up workflows or client communication.

Key parameters: Credential to connect with (Harvest authentication, required), Resource (set to "Estimate"), Operation (set to "Get"), Account Name or ID (target account, required), Estimate ID (the specific estimate to retrieve, required).

Use cases: Verify estimate details before converting to project, fetch estimate info for client follow-up emails, check estimate status for pipeline workflows.

Remove an estimate from Harvest. Use for cleanup of outdated quotes or rejected proposals.

Key parameters: Credential to connect with (Harvest credentials, required), Resource (set to "Estimate"), Operation (set to "Delete"), Account Name or ID (target account, required), Estimate ID (the estimate to delete, required).

Use cases: Delete outdated estimates older than a certain period, remove duplicate estimates from automation errors, clean up rejected proposals after final decisions.

Generate new estimates in Harvest. Automate quote creation based on CRM opportunities, client inquiries, or project scoping workflows.

Key parameters: Credential to connect with (Harvest authentication, required), Resource (set to "Estimate"), Operation (set to "Create"), Account Name or ID (target account, required), Client ID (the client receiving the estimate, required), Additional Fields (subject, notes, issue date, line items, amounts, etc.).

Use cases: Auto-generate estimates from CRM opportunity data, create estimates from project scoping form submissions, produce standard quotes for productized services.

Modify existing contact records in Harvest. Keep client contacts current by syncing updates from CRM systems or directory services.

Key parameters: Credential to connect with (Harvest credentials, required), Resource (set to "Contact"), Operation (set to "Update"), Account Name or ID (target account, required), Contact ID (the contact to modify, required), Update Fields (name, title, email, phone, etc.).

Use cases: Sync contact updates from HubSpot or Salesforce, update contact roles when client team changes occur, correct contact information from form submissions.

Retrieve multiple contacts from your Harvest account. Useful for syncing contact directories, building mailing lists, or auditing client contact data.

Key parameters: Credential to connect with (Harvest authentication, required), Resource (set to "Contact"), Operation (set to "Get Many"), Account Name or ID (target account, required), Return All (fetch all or limit), Limit (maximum to return, default 100), Filters (filter by client, updated date, etc.).

Use cases: Sync Harvest contacts to email marketing platforms, export contacts for CRM import, generate client contact directories.

Fetch details about a specific contact by ID. Use for targeted lookups when you need individual contact information.

Key parameters: Credential to connect with (Harvest credentials, required), Resource (set to "Contact"), Operation (set to "Get"), Account Name or ID (target account, required), Contact ID (the specific contact to retrieve, required).

Use cases: Verify contact details before sending communications, fetch contact info for invoice delivery, check contact existence before updates.

Remove a contact from Harvest. Use for cleanup when contacts leave client organizations or when consolidating duplicate records.

Key parameters: Credential to connect with (Harvest authentication, required), Resource (set to "Contact"), Operation (set to "Delete"), Account Name or ID (target account, required), Contact ID (the contact to delete, required).

Use cases: Remove departed client contacts after notification, delete duplicate contact records, clean up test contacts after development.

Add new contacts to client records in Harvest. Automate contact creation from CRM systems, form submissions, or email parsing.

Key parameters: Credential to connect with (Harvest credentials, required), Resource (set to "Contact"), Operation (set to "Create"), Account Name or ID (target account, required), Client ID (associate with a client, optional), First Name (contact's first name, optional), Additional Fields (last name, title, email, phone, fax, etc.).

Use cases: Auto-create contacts from CRM new contact events, add contacts from client onboarding form submissions, create contacts when new stakeholders are identified in email.

Retrieve your Harvest company/account information. This action provides access to account-level settings, subscription details, and company configuration.

Key parameters: Credential to connect with (Harvest authentication, required), Resource (set to "Company"), Operation (set to "Get"), Account Name or ID (the account to retrieve information about, required).

Use cases: Fetch account settings for configuration verification, check subscription status and limits, retrieve company info for administrative dashboards.

Modify existing client records in Harvest. Keep client information accurate by syncing updates from CRM systems or correcting details as needed.

Key parameters: Credential to connect with (Harvest credentials, required), Resource (set to "Client"), Operation (set to "Update"), Account Name or ID (target account, required), Client ID (the client to modify, required), Update Fields (name, address, currency, active status, etc.).

Use cases: Sync client details from CRM updates, update billing addresses from client requests, toggle client active status based on contract status.

Retrieve a list of clients from Harvest. Essential for syncing client directories, building selection interfaces, or generating client reports.

Key parameters: Credential to connect with (Harvest authentication, required), Resource (set to "Client"), Operation (set to "Get Many"), Account Name or ID (target account, required), Return All (fetch all or limit), Limit (maximum to return, default 100), Filters (filter by active status, updated date, etc.).

Use cases: Sync Harvest clients to CRM systems, populate client selection dropdowns in custom tools, generate client portfolio reports.

Fetch complete details about a specific client. Use for targeted lookups when you need comprehensive client information.

Key parameters: Credential to connect with (Harvest credentials, required), Resource (set to "Client"), Operation (set to "Get"), Account Name or ID (target account, required), Client ID (the specific client to retrieve, required).

Use cases: Verify client details before project creation, fetch client info for invoice delivery, check client settings for billing workflows.

Remove a client from Harvest. Use carefully—this affects all associated projects and historical data. Consider archiving (setting inactive) instead.

Key parameters: Credential to connect with (Harvest authentication, required), Resource (set to "Client"), Operation (set to "Delete"), Account Name or ID (target account, required), Client ID (the client to delete, required).

Use cases: Remove test clients after development cycles, delete duplicate client records from import errors, clean up clients that never materialized (with caution).

Add new clients to Harvest automatically. This action enables automated client setup from CRM deal closures, contract signatures, or onboarding workflows.

Key parameters: Credential to connect with (Harvest credentials, required), Resource (set to "Client"), Operation (set to "Create"), Account Name or ID (target account, required), Name (client name, required), Additional Fields (address, currency, active status, etc.).

Use cases: Auto-create clients when deals close in your CRM, set up clients from contract management system approvals, create clients from onboarding form submissions.