ONFLEET n8n INTEGRATION: AUTOMATE ONFLEET WITH N8N
Looking to automate your delivery operations with Onfleet and n8n? You're in the right place. The Onfleet n8n integration gives you access to 17 triggers and 37 actions to build powerful automations that streamline your last-mile delivery workflows without writing a single line of code.
With this native integration, you can automatically react to task completions, driver status changes, SMS responses, and much more. Whether you're syncing delivery data with your CRM, sending real-time notifications to customers, or automating driver assignments, the Onfleet n8n connection handles the heavy lifting so your team can focus on what matters: getting deliveries done efficiently.
Discover how to connect Onfleet to n8n, explore every available trigger and action, and start building automations that save hours of manual work every week. If you're new to n8n, check out our n8n training to get started quickly.
Need help automating Onfleet with n8n?
Our team will get back to you in minutes.
Why automate Onfleet with n8n?
The Onfleet n8n integration opens up 17 triggers and 37 actions that cover virtually every aspect of delivery management. From the moment a task is created to its final completion (or failure), you can automate responses, updates, and data flows across your entire tech stack. This means no more jumping between dashboards, no more copy-pasting driver information, and no more missed updates.
The concrete benefits are significant. First, you save considerable time by eliminating manual data entry—when a task is completed in Onfleet, n8n can automatically update your order management system, notify your customer via email or SMS, and log the delivery in your analytics platform. Second, you gain instant responsiveness: triggers fire the moment something happens in Onfleet, whether it's a driver going on duty, a task being assigned, or a recipient opting out of SMS notifications. Third, you achieve zero oversight: with webhooks monitoring your Onfleet account 24/7, every critical event immediately triggers the appropriate workflow.
Typical workflows you can build include: automatically creating tasks in Onfleet when new orders arrive from your e-commerce platform; syncing completed deliveries to your invoicing system; sending proactive delay notifications when tasks are marked as delayed; updating your customer database when recipients respond to SMS messages; and alerting your operations team in Slack when tasks fail. You can also connect Onfleet to your HubSpot CRM via n8n for seamless customer data synchronization. The possibilities extend across your entire delivery operation.
How to connect Onfleet to n8n?
! 1 stepHow to connect Onfleet to n8n?
- 01
Add the node
Search and add the node in your workflow.
TIP💡 TIP: Create a dedicated API key specifically for n8n integrations rather than using your main account key. This way, if you ever need to revoke access, you won't disrupt other integrations, and you'll have clearer audit trails in your Onfleet account.- 01
Need help automating Onfleet with n8n?
Our team will get back to you in minutes.
Onfleet triggers available in n8n
01 Trigger 01Worker Duty
This trigger activates your workflow whenever a driver's duty status changes in Onfleet—meaning when they clock in to start their shift or clock out at the end of the day. It's essential for workforce management automations where you need to track driver availability in real-time.
Configuration parameters: The "Credential to connect with" is a required dropdown to select your authenticated Onfleet account. "Trigger On" must be set to "Worker Duty" to listen specifically for duty status changes. The "Additional Fields" section is optional and allows you to add extra filters or parameters to refine when the trigger fires.
Typical use cases: Automatically update a scheduling spreadsheet when drivers start or end their shifts; send a morning summary to operations managers listing all drivers currently on duty; trigger payroll calculations when a driver clocks out; update a real-time dashboard showing available driver capacity.
When to use it: Perfect for operations teams that need visibility into driver availability, HR departments tracking work hours, or any workflow where knowing exactly when drivers are active is critical.
02 Trigger 02Worker Deleted
This trigger fires every time a worker profile is removed from your Onfleet account. Whether a driver leaves the company, gets reassigned, or their profile is cleaned up, this trigger ensures you can respond immediately to maintain data consistency across your systems.
Configuration parameters: "Credential to connect with" is a required dropdown to select your Onfleet account credentials for authentication. "Trigger On" must be set to "Worker Deleted" to activate the workflow when any worker is removed. "Additional Fields" is optional and allows you to add filtering conditions or capture extra data with the event.
Typical use cases: Automatically remove the worker from your HR system or payroll platform; revoke access credentials across other tools (Slack, email, fleet management systems); archive the driver's performance data before deletion; notify managers when team members are removed.
When to use it: Essential for maintaining synchronized records across multiple platforms and ensuring clean offboarding processes when drivers leave your organization.
03 Trigger 03Worker Created
When a new driver is added to your Onfleet account, this trigger immediately fires to kick off your onboarding workflows. It eliminates the delay between adding a worker in Onfleet and updating your other business systems.
Configuration parameters: "Credential to connect with" is a required dropdown to select the Onfleet account for authentication. "Trigger On" must be set to "Worker Created" to listen for new worker profiles. "Additional Fields" is an optional section for adding custom parameters or filters.
Typical use cases: Automatically create the driver's profile in your HR system; send welcome emails with onboarding instructions and training materials; add the new worker to team communication channels (Slack, Teams); provision access to additional tools and systems they'll need.
When to use it: Ideal for companies that want to automate driver onboarding and ensure new team members are set up across all systems within minutes of being added to Onfleet.
04 Trigger 04Task Updated
This trigger monitors all changes to existing tasks in Onfleet. Any modification—whether it's a status change, a new note added, a time window adjustment, or an assignment update—will fire this trigger and pass the updated task data to your workflow.
Configuration parameters: "Credential to connect with" is a required dropdown for selecting your authenticated Onfleet connection. "Trigger On" must be set to "Task Updated" to capture all task modifications—this is a required field with options for Fixed value or Expression mode. "Additional Fields" is an optional area for adding filters to narrow down which updates trigger the workflow.
Typical use cases: Sync task changes to your order management system in real-time; update customer-facing tracking pages when delivery ETAs change; alert dispatchers when high-priority tasks are modified; log all task changes to an audit trail for compliance.
When to use it: Use this trigger when you need comprehensive visibility into task modifications, whether for real-time syncing, audit purposes, or keeping customers informed about their deliveries.
05 Trigger 05Task Unassigned
When a task is removed from a driver's assignment—whether manually by a dispatcher or automatically by Onfleet's routing engine—this trigger fires. It's crucial for workflows that need to respond to reassignment situations or identify tasks that need attention.
Configuration parameters: "Credential to connect with" is a required field to select your Onfleet credentials. "Trigger On" must be set to "Task Unassigned" to monitor for unassignment events—this is a required dropdown. "Additional Fields" is optional and allows for filters or additional parameters.
Typical use cases: Automatically reassign unassigned tasks to available drivers; alert dispatchers about tasks that need immediate attention; update customer notifications when their assigned driver changes; track unassignment patterns for operational analysis.
When to use it: Critical for operations teams that need to ensure no task falls through the cracks and that reassignments are handled smoothly without manual monitoring.
06 Trigger 06Task Started
This trigger activates the moment a driver begins working on a task—typically when they tap "Start" in the Onfleet driver app. It marks the transition from an assigned task to an in-progress delivery.
Configuration parameters: "Credential to connect with" is a required dropdown to authenticate with your Onfleet account. "Trigger On" must be set to "Task Started" to capture when drivers begin tasks—this is required. "Additional Fields" is an optional section for additional filtering criteria.
Typical use cases: Send customers a real-time "Your driver is on the way" notification; update order status in your e-commerce platform to "Out for Delivery"; start a timer for delivery SLA tracking; log the exact start time for performance analytics.
When to use it: Perfect for customer communication workflows and any process where knowing the precise moment a delivery attempt begins is valuable.
07 Trigger 07Task Failed
When a delivery cannot be completed—whether due to customer unavailable, incorrect address, or other issues—this trigger fires. It's essential for exception handling and ensuring failed deliveries receive immediate attention.
Configuration parameters: "Credential to connect with" is a required Onfleet credential selection. "Trigger On" must be set to "Task Failed" to listen for failed delivery events—this is a required dropdown supporting Fixed or Expression modes. "Additional Fields" is optional and allows for parameters for additional conditions.
Typical use cases: Immediately notify customers about failed delivery attempts with rescheduling options; alert customer service teams to proactively reach out; create tickets in your helpdesk system for follow-up; trigger automatic rescheduling workflows.
When to use it: Essential for any delivery operation that prioritizes customer experience and wants to minimize the impact of failed deliveries through quick response.
08 Trigger 08Task ETA
This trigger fires when there are updates to a task's Estimated Time of Arrival. Whether the ETA moves earlier or later, you can automatically react to keep customers informed and internal teams prepared.
Configuration parameters: "Credential to connect with" is a required dropdown for Onfleet authentication. "Trigger On" must be set to "Task ETA" to monitor ETA changes—this is a required field with Fixed/Expression options. "Additional Fields" is optional and allows for filters and parameters.
Typical use cases: Send customers updated ETA notifications in real-time; adjust warehouse or dock scheduling based on arrival estimates; update delivery tracking pages with current timing; alert operations when ETAs deviate significantly from planned windows.
When to use it: Ideal for customer-facing workflows where delivery timing matters, or internal operations that need to coordinate resources based on driver arrival times.
09 Trigger 09Task Deleted
When a task is permanently removed from Onfleet—not just cancelled but deleted—this trigger captures that event. It ensures your connected systems stay synchronized even when tasks are removed.
Configuration parameters: "Credential to connect with" is a required Onfleet account selection. "Trigger On" must be set to "Task Deleted" to monitor task deletions—this is required. "Additional Fields" is optional and allows for additional parameters.
Typical use cases: Remove the corresponding order from pending delivery reports; update inventory systems if the delivery is no longer happening; log deletions for audit and reconciliation purposes; clean up related records in connected systems.
When to use it: Important for maintaining data integrity across systems and ensuring deleted tasks don't create orphaned records elsewhere in your tech stack.
10 Trigger 10Task Delayed
This trigger fires when Onfleet marks a task as delayed—meaning it won't be completed within the originally scheduled time window. It's your early warning system for delivery issues.
Configuration parameters: "Credential to connect with" is a required dropdown for selecting your Onfleet credentials. "Trigger On" must be set to "Task Delayed" to capture delay events—this is required. "Additional Fields" is an optional section for custom parameters.
Typical use cases: Proactively notify customers that their delivery will be late; alert dispatchers to consider reassigning the task; log delays for performance tracking and route optimization; trigger escalation workflows for time-sensitive deliveries.
When to use it: Critical for maintaining customer satisfaction by communicating delays before they become complaints, and for operations teams monitoring delivery performance.
11 Trigger 11Task Created
Every time a new task is added to Onfleet—whether through the dashboard, API, or another integration—this trigger fires. It's the foundation for any workflow that needs to react to new delivery requests.
Configuration parameters: "Credential to connect with" is a required dropdown for Onfleet authentication. "Trigger On" must be set to "Task Created" to listen for new tasks—this is required. "Additional Fields" is optional and allows for filtering parameters.
Typical use cases: Automatically assign new tasks to the optimal driver based on custom logic; send confirmation emails to customers when their delivery is scheduled; create corresponding records in your CRM or order management system; trigger route optimization recalculations.
When to use it: Essential starting point for any delivery workflow—use this trigger whenever you need to respond to new delivery requests entering your Onfleet system.
12 Trigger 12Task Completed
This trigger activates when a task is successfully finished—the driver has made the delivery and marked it complete. It's the endpoint for most delivery workflows and the trigger for post-delivery processes.
Configuration parameters: "Credential to connect with" is a required Onfleet credential dropdown. "Trigger On" must be set to "Task Completed" to capture successful completions—this is a required field with Fixed/Expression toggle. "Additional Fields" is optional and allows for additional parameters.
Typical use cases: Send customers a "Your delivery is complete" confirmation with proof of delivery; update your order management system to mark the order as delivered; trigger invoicing or billing processes; request customer feedback or reviews; update inventory and fulfillment records.
When to use it: The most commonly used trigger—perfect for closing the loop on deliveries and initiating any post-delivery processes in your business.
13 Trigger 13Task Cloned
When an existing task is duplicated in Onfleet—often used for rescheduling failed deliveries or creating recurring routes—this trigger fires with the new cloned task data.
Configuration parameters: "Credential to connect with" is a required Onfleet account dropdown. "Trigger On" must be set to "Task Cloned" to monitor cloning events—this is required. "Additional Fields" is optional and allows for parameters for filtering.
Typical use cases: Automatically update customer records with new task information; track rescheduled deliveries separately from originals; ensure cloned tasks are properly categorized in your systems; maintain delivery attempt history.
When to use it: Useful for workflows that need to distinguish between original and rescheduled deliveries, or when you want to track delivery attempts across multiple tries.
14 Trigger 14Task Assigned
This trigger fires the moment a task is assigned to a driver—whether through auto-dispatch, manual assignment, or routing optimization. It captures the critical transition from unassigned to assigned.
Configuration parameters: "Credential to connect with" is a required dropdown for Onfleet credentials. "Trigger On" must be set to "Task Assigned" to listen for assignment events—this is a required field supporting Fixed/Expression modes. "Additional Fields" is optional and allows for additional filters.
Typical use cases: Notify customers that a driver has been assigned and provide driver details; update internal dashboards with assignment status; trigger preparation workflows at the pickup location; send assignment confirmations to drivers via additional channels.
When to use it: Perfect for customer communication workflows and internal operations that need visibility into the assignment process.
15 Trigger 15Task Arrival
When a driver arrives at the task destination—as detected by Onfleet's geofencing—this trigger fires. It's the moment between "on the way" and "delivered," crucial for time-sensitive operations.
Configuration parameters: "Credential to connect with" is a required Onfleet credential selection. "Trigger On" must be set to "Task Arrival" to capture driver arrival events—this is required. "Additional Fields" is optional and allows for parameters.
Typical use cases: Send "Your driver has arrived" notifications to customers; alert dock workers or receiving staff that a driver is at the location; start unloading or service timers for performance tracking; update customer tracking pages in real-time.
When to use it: Ideal for last-moment customer notifications and any workflow where knowing the exact arrival time is operationally important.
16 Trigger 16SMS Recipient Response Missed
When a customer fails to respond to an SMS notification within the expected timeframe, this trigger fires. It helps you identify and follow up with unresponsive recipients.
Configuration parameters: "Credential to connect with" is a required Onfleet account selection. "Trigger On" must be set to "SMS Recipient Response Missed" to capture missed responses—this is required. "Additional Fields" is optional and allows for additional parameters.
Typical use cases: Trigger follow-up communication through alternative channels (email, phone call); alert customer service to reach out proactively; update task notes with communication status; adjust delivery instructions based on non-response.
When to use it: Important for delivery operations that rely on customer confirmation or response, ensuring no missed communication leads to failed deliveries.
17 Trigger 17SMS Recipient Opt Out
This trigger fires when a customer opts out of receiving SMS notifications from your delivery operations. It's essential for compliance and maintaining accurate communication preferences.
Configuration parameters: "Credential to connect with" is a required Onfleet credential dropdown. "Trigger On" must be set to "SMS Recipient Opt Out" to capture opt-out events—this is a required field with Fixed/Expression options. "Additional Fields" is optional and allows for filtering parameters.
Typical use cases: Update customer preferences in your CRM immediately; switch to alternative communication channels (email, app notifications); maintain compliance with SMS marketing regulations; log opt-out events for audit purposes.
When to use it: Critical for compliance-focused operations and ensuring customer communication preferences are respected across all your systems.
Onfleet actions available in n8n
01 Action 01Update Worker
This action allows you to modify any existing driver profile in Onfleet. Whether you need to update contact information, change capacity settings, or adjust team assignments, this action handles it all programmatically.
Key parameters: "Credential to connect with" is a required dropdown to select your Onfleet account. "Resource" must be set to "Worker"—required. "Operation" must be set to "Update"—required. "Worker ID" is a required text field for the unique identifier of the worker to update. "Update Fields" is an optional section to specify which properties to change and their new values.
Use cases: Automatically update driver phone numbers from HR system changes; adjust worker capacity based on vehicle assignments; sync team changes across platforms.
02 Action 02Get Schedule
Retrieve the schedule for a specific worker, including their assigned shifts and availability windows. This action is essential for workforce planning and schedule management.
Key parameters: "Credential to connect with" is a required Onfleet account dropdown. "Resource" must be set to "Worker"—required. "Operation" must be set to "Get Schedule"—required. "Worker ID" is a text field to specify which worker's schedule to retrieve.
Use cases: Display driver schedules in custom dashboards; validate availability before task assignments; sync schedules with external workforce management tools.
03 Action 03Get Many Workers
Retrieve multiple worker profiles in a single request, with options for filtering by location and limiting results. Perfect for bulk operations and reporting.
Key parameters: "Credential to connect with" is required Onfleet credentials. "Resource" must be set to "Worker"—required. "Operation" must be set to "Get Many"—required. "Search by Location" is an optional toggle to filter workers by geographical area. "Return All" is an optional toggle to fetch all records, overriding the limit. "Limit" is an optional number field (default 64) to cap the number of results. "Filters" is an optional section for additional filtering criteria.
Use cases: Generate daily driver rosters; find available drivers in a specific area; export worker data for reporting.
04 Action 04Get Worker
Retrieve detailed information about a specific driver by their unique ID. Returns complete worker data including contact info, teams, schedule, and current status.
Key parameters: "Credential to connect with" is a required Onfleet account. "Resource" must be set to "Worker"—required. "Operation" must be set to "Get"—required. "Worker ID" is a required text field for the worker's unique identifier. "Options" is optional for additional query parameters.
Use cases: Look up driver details for customer service inquiries; verify driver information before task assignments; fetch current driver status for dashboards.
05 Action 05Delete Worker
Permanently remove a worker profile from your Onfleet account. Use with caution—this action cannot be undone.
Key parameters: "Credential to connect with" is required Onfleet credentials. "Resource" must be set to "Worker"—required. "Operation" must be set to "Delete"—required. "Worker ID" is a required text field specifying which worker to remove.
Use cases: Automate offboarding when drivers leave the company; clean up test or duplicate worker profiles; sync deletions from your HR system.
06 Action 06Create Worker
Add a new driver to your Onfleet account with all necessary profile information. This action provisions the worker and can assign them to teams immediately.
Key parameters: "Credential to connect with" is a required Onfleet account. "Resource" must be set to "Worker"—required. "Operation" must be set to "Create"—required. "Name" is the driver's full name. "Phone" is the driver's phone number for the Onfleet app. "Team Names or IDs" is a dropdown to assign the new worker to existing teams. "Additional Fields" is optional properties like vehicle details or metadata.
Use cases: Automate driver onboarding from HR system triggers; create workers from recruitment platform approvals; bulk import new drivers from spreadsheets.
07 Action 07Update Team
Modify an existing team's properties, including name, managers, hub assignments, and worker membership.
Key parameters: "Credential to connect with" is required Onfleet credentials. "Resource" must be set to "Team"—required. "Operation" must be set to "Update"—required. "Team ID" is a required text field for the team's unique identifier. "Update Fields" is an optional section to specify which team properties to modify.
Use cases: Automatically rotate team managers; update hub assignments based on operational changes; modify team names for seasonal campaigns.
08 Action 08Get Time Estimates
Retrieve estimated delivery times for tasks within a specific team's operating area. Essential for capacity planning and customer communication.
Key parameters: "Credential to connect with" is a required Onfleet account. "Resource" must be set to "Team"—required. "Operation" must be set to "Get Time Estimates"—required. "Team ID" is an optional text field to specify which team's estimates to retrieve. "Filters" is optional filtering criteria for the estimates.
Use cases: Provide accurate ETAs to customers at checkout; plan capacity based on estimated completion times; optimize scheduling based on time windows.
09 Action 09Get Many Teams
Retrieve multiple team records from your Onfleet account, useful for reporting and multi-team management.
Key parameters: "Credential to connect with" is required Onfleet credentials. "Resource" must be set to "Team"—required. "Operation" must be set to "Get Many"—required. "Return All" is an optional toggle to fetch all teams. "Limit" is an optional number field to cap results (default 64).
Use cases: Generate reports across all teams; populate team selection dropdowns; audit team configurations.
10 Action 10Get Team
Retrieve detailed information about a specific team by its unique identifier.
Key parameters: "Credential to connect with" is a required Onfleet account. "Resource" must be set to "Team"—required. "Operation" must be set to "Get"—required. "Team ID" is a required text field for the team's unique ID.
Use cases: Look up team details for operational decisions; verify team configuration; fetch team data for custom dashboards.
11 Action 11Delete Team
Permanently remove a team from your Onfleet account.
Key parameters: "Credential to connect with" is required Onfleet credentials. "Resource" must be set to "Team"—required. "Operation" must be set to "Delete"—required. "Team ID" is a required text field specifying which team to remove.
Use cases: Clean up inactive teams; automate team removal when regions close; sync organizational changes.
12 Action 12Create Team
Set up a new team in Onfleet with designated workers and administrators.
Key parameters: "Credential to connect with" is a required Onfleet account. "Resource" must be set to "Team"—required. "Operation" must be set to "Create"—required. "Name" is a required text field for the team name. "Worker Names or IDs" is optional selection to assign existing workers. "Administrator Names or IDs" is optional selection to assign team administrators. "Additional Fields" is optional properties like hub assignment.
Use cases: Automate team creation when expanding to new regions; set up temporary teams for events; create teams from operational planning tools.
13 Action 13Team Auto-Dispatch
Trigger Onfleet's auto-dispatch algorithm for a specific team, automatically assigning unassigned tasks to available drivers based on optimization rules.
Key parameters: "Credential to connect with" is required Onfleet credentials. "Resource" must be set to "Team"—required. "Operation" must be set to "Auto-Dispatch"—required. "Team ID" is a required text field specifying which team to auto-dispatch. "Additional Fields" is optional parameters for dispatch settings.
Use cases: Trigger dispatch at scheduled intervals; run auto-dispatch when new tasks are added; optimize assignments before shift starts.
14 Action 14Update Task
Modify any property of an existing task, from recipient details to delivery windows to custom metadata.
Key parameters: "Credential to connect with" is a required Onfleet account. "Resource" must be set to "Task"—required. "Operation" must be set to "Update"—required. "Task ID" is a required text field for the task's unique identifier. "Update Fields" is an optional section to specify which properties to change.
Use cases: Update delivery instructions from customer service changes; modify time windows based on customer requests; add notes from external systems.
15 Action 15Get Many Tasks
Retrieve multiple tasks with filtering options for efficient bulk operations and reporting.
Key parameters: "Credential to connect with" is required Onfleet credentials. "Resource" must be set to "Task"—required. "Operation" must be set to "Get Many"—required. "Return All" is an optional toggle to fetch all matching tasks. "Limit" is an optional number field to cap results (default 64). "Filters" is optional criteria to narrow down results.
Use cases: Generate daily delivery reports; export completed tasks for billing; monitor pending tasks across teams.
16 Action 16Get Task
Retrieve complete details about a specific task by its unique identifier.
Key parameters: "Credential to connect with" is a required Onfleet account. "Resource" must be set to "Task"—required. "Operation" must be set to "Get"—required. "Task ID" is a required text field for the task's unique ID.
Use cases: Look up task details for customer inquiries; fetch current task status; verify delivery information.
17 Action 17Delete Task
Permanently remove a task from Onfleet.
Key parameters: "Credential to connect with" is required Onfleet credentials. "Resource" must be set to "Task"—required. "Operation" must be set to "Delete"—required. "Task ID" is a required text field specifying which task to delete.
Use cases: Cancel orders synced from e-commerce platforms; clean up test tasks; remove duplicate entries.
18 Action 18Create Task
Add a new delivery task to Onfleet with full destination, recipient, and configuration details.
Key parameters: "Credential to connect with" is a required Onfleet account. "Resource" must be set to "Task"—required. "Operation" must be set to "Create"—required. "Destination" is a section to add one or more delivery destinations with address details. "Additional Fields" is optional properties like time windows, notes, or metadata.
Use cases: Create tasks from e-commerce orders; add deliveries from CRM opportunities; import tasks from external scheduling systems. You can also combine this with WooCommerce n8n integration to automatically create delivery tasks from online orders.
19 Action 19Complete Task
Programmatically mark a task as complete, with the option to specify whether it was successful or failed.
Key parameters: "Credential to connect with" is required Onfleet credentials. "Resource" must be set to "Task"—required. "Operation" must be set to "Complete"—required. "Task ID" is a required text field for the task to complete. "Complete as a Success" is an optional toggle (default on) to mark as successful completion. "Additional Fields" is optional completion notes or data.
Use cases: Complete tasks from external confirmation systems; batch-close tasks at end of day; integrate with proof-of-delivery systems.
20 Action 20Clone Task
Duplicate an existing task, useful for rescheduling failed deliveries or creating recurring routes.
Key parameters: "Credential to connect with" is a required Onfleet account. "Resource" must be set to "Task"—required. "Operation" must be set to "Clone"—required. "Task ID" is a required text field for the task to duplicate. "Override Fields" is an optional section to modify specific properties in the cloned task.
Use cases: Reschedule failed deliveries automatically; create recurring tasks from templates; duplicate tasks with modified dates.
21 Action 21Update Recipient
Modify recipient information for improved delivery accuracy and communication.
Key parameters: "Credential to connect with" is required Onfleet credentials. "Resource" must be set to "Recipient"—required. "Operation" must be set to "Update"—required. "Recipient ID" is a required text field for the recipient's unique identifier. "Update Fields" is an optional section for properties to modify (name, phone, notes).
Use cases: Sync customer information changes from CRM; update contact details from customer service interactions; correct recipient data.
22 Action 22Get Recipient
Retrieve detailed information about a specific recipient by ID.
Key parameters: "Credential to connect with" is a required Onfleet account. "Resource" must be set to "Recipient"—required. "Operation" must be set to "Get"—required. "Get By" is a required dropdown (typically "ID"). "Recipient ID" is a required text field for the recipient's identifier.
Use cases: Look up customer history; verify recipient details; fetch recipient data for reporting.
23 Action 23Create Recipient
Add a new recipient to Onfleet's database for future task assignments.
Key parameters: "Credential to connect with" is required Onfleet credentials. "Resource" must be set to "Recipient"—required. "Operation" must be set to "Create"—required. "Recipient Name" is a text field for the recipient's name. "Recipient Phone" is a text field for contact number. "Additional Fields" is optional properties like notes or metadata. "Options" is optional configuration settings.
Use cases: Pre-create recipients from customer database; set up recipients from order imports; sync recipients from CRM.
24 Action 24Get Delegatee Details
Retrieve information about organizations that have been delegated access to your Onfleet account.
Key parameters: "Credential to connect with" is a required Onfleet account. "Resource" must be set to "Organization"—required. "Operation" must be set to "Get Delegatee Details"—required. "Organization ID" is a required text field for the organization identifier.
Use cases: Audit delegated access; verify third-party integrations; manage partner relationships.
25 Action 25Get My Organization
Retrieve complete details about your connected Onfleet organization, including settings and configuration.
Key parameters: "Credential to connect with" is required Onfleet credentials. "Resource" must be set to "Organization"—required. "Operation" must be set to "Get My Organization"—required.
Use cases: Verify account configuration; fetch organization settings for dashboards; audit account details.
26 Action 26Update Hub
Modify properties of an existing hub location in your Onfleet account.
Key parameters: "Credential to connect with" is a required Onfleet account. "Resource" must be set to "Hub"—required. "Operation" must be set to "Update"—required. "Hub ID" is a required text field for the hub's unique identifier. "Update Fields" is an optional section for properties to modify.
Use cases: Update hub addresses when locations change; modify hub names; adjust hub configurations.
27 Action 27Get Many Hubs
Retrieve multiple hub records from your Onfleet account.
Key parameters: "Credential to connect with" is required Onfleet credentials. "Resource" must be set to "Hub"—required. "Operation" must be set to "Get Many"—required. "Return All" is an optional toggle to fetch all hubs. "Limit" is an optional number field to cap results (default 64).
Use cases: Generate hub reports; populate hub selection dropdowns; audit hub configurations.
28 Action 28Create Hub
Set up a new hub location in Onfleet with address and configuration details.
Key parameters: "Credential to connect with" is a required Onfleet account. "Resource" must be set to "Hub"—required. "Operation" must be set to "Create"—required. "Name" is a required text field for the hub name. "Destination" is a section for adding the hub's physical address. "Additional Fields" is optional properties.
Use cases: Automate hub creation when opening new locations; set up temporary hubs for events; sync locations from facility management systems.
29 Action 29Get Destination
Retrieve details about a specific delivery destination by its unique identifier.
Key parameters: "Credential to connect with" is required Onfleet credentials. "Resource" must be set to "Destination"—required. "Operation" must be set to "Get"—required. "Destination ID" is a required text field for the destination's identifier.
Use cases: Verify address details; look up destination information for customer inquiries; fetch destination data for reporting.
30 Action 30Create Destination
Add a new destination record to Onfleet with full address details.
Key parameters: "Credential to connect with" is a required Onfleet account. "Resource" must be set to "Destination"—required. "Operation" must be set to "Create"—required. "Unparsed Address" is an optional toggle to provide a single address string for parsing. "Number, Street, City, Country" are optional text fields for structured address input. "Additional Fields" is optional properties like notes or metadata.
Use cases: Pre-create destinations from address databases; set up destinations for recurring deliveries; import locations from external systems.
31 Action 31Update Tasks in Container
Modify tasks within a specific container (worker, team, or organization).
Key parameters: "Credential to connect with" is required Onfleet credentials. "Resource" must be set to "Container"—required. "Operation" must be set to "Update Tasks"—required. "Container ID" is a required text field for the container's identifier. "Task IDs" is a section to specify which tasks to update. "Options" is optional additional parameters.
Use cases: Batch update tasks assigned to a driver; modify task order within a container; manage task properties in bulk.
32 Action 32Get Container
Retrieve information about a container (worker, team, or organization) and its contents.
Key parameters: "Credential to connect with" is a required Onfleet account. "Resource" must be set to "Container"—required. "Operation" must be set to "Get"—required. "Container Type" is a required dropdown to specify the container type. "Container ID" is a required text field for the container's identifier.
Use cases: View all tasks assigned to a driver; check team workload; audit container contents.
33 Action 33Add Tasks to Container
Assign one or more tasks to a container (typically a worker or team) with control over insertion position.
Key parameters: "Credential to connect with" is required Onfleet credentials. "Resource" must be set to "Container"—required. "Operation" must be set to "Add Tasks"—required. "Container Type" is a required dropdown for the target container type. "Container ID" is a required text field for the container's identifier. "Insert Type" is a required dropdown for where to add tasks (beginning, end, specific index). "Task IDs" is a section to specify which tasks to add. "Options" is optional additional parameters.
Use cases: Assign tasks to drivers programmatically; bulk-assign tasks to teams; insert priority tasks at specific positions.
34 Action 34Update Admin
Modify properties of an existing administrator account in Onfleet.
Key parameters: "Credential to connect with" is a required Onfleet account. "Resource" must be set to "Admin"—required. "Operation" must be set to "Update"—required. "Admin ID" is a required text field for the admin's unique identifier. "Update Fields" is an optional section for properties to modify.
Use cases: Update admin email addresses; change admin permissions; sync admin details from HR systems.
35 Action 35Get Many Admins
Retrieve multiple administrator records from your Onfleet account.
Key parameters: "Credential to connect with" is required Onfleet credentials. "Resource" must be set to "Admin"—required. "Operation" must be set to "Get Many"—required. "Return All" is an optional toggle to fetch all admins. "Limit" is an optional number field to cap results (default 64).
Use cases: Generate admin audit reports; verify admin access levels; export admin list for compliance.
36 Action 36Delete Admin
Remove an administrator account from Onfleet.
Key parameters: "Credential to connect with" is a required Onfleet account. "Resource" must be set to "Admin"—required. "Operation" must be set to "Delete"—required. "Admin ID" is a required text field specifying which admin to remove.
Use cases: Automate admin offboarding; revoke access when roles change; clean up inactive accounts.
37 Action 37Create Admin
Add a new administrator to your Onfleet account with specified permissions and access.
Key parameters: "Credential to connect with" is required Onfleet credentials. "Resource" must be set to "Admin"—required. "Operation" must be set to "Create"—required. "Name" is a required text field for the admin's name. "Email" is a required text field for the admin's email address. "Additional Fields" is optional properties like phone number or permissions.
Use cases: Automate admin onboarding; create admins from HR system triggers; provision accounts for new managers.
Build your first workflow with our team
Drop your email and we'll send you the catalog of automations you can ship today.
- Free n8n & Make scenarios to import
- Step-by-step setup docs
- Live cohort + community support
Frequently asked questions
Is the Onfleet n8n integration free to use?
The integration itself is completely free—n8n is open-source and you can self-host it at no cost, or use n8n cloud which has a free tier. However, you do need an active Onfleet account with API access, which depends on your Onfleet subscription plan. Most Onfleet plans include API access, but it's worth confirming with Onfleet if you're on a basic plan. Once you have both n8n and Onfleet API access, there are no additional fees for the integration—you can create unlimited workflows connecting the two platforms. Learn more about n8n capabilities in our comprehensive n8n review.What data can I sync between Onfleet and n8n?
You can sync virtually all Onfleet data through n8n. This includes complete task information (destinations, recipients, timing, status, proof of delivery), worker details (contact info, schedules, teams, current location), team configurations, hub locations, and administrative accounts. With 17 triggers capturing real-time events and 37 actions for reading and writing data, you can build bidirectional syncs with your CRM, e-commerce platform, warehouse management system, or any other tool in your stack. The integration supports both polling for data and instant webhooks for real-time event capture. For storing delivery data, consider integrating with Airtable via n8n or Google Sheets.How long does it take to set up the Onfleet n8n integration?
The basic connection takes about 5 minutes—you just need to grab your API key from Onfleet and paste it into n8n. Building your first simple workflow (like sending a notification when a task completes) can be done in another 10-15 minutes. More complex workflows involving multiple triggers, conditional logic, and connections to other platforms might take an hour or two to build and test properly. The n8n visual interface makes it easy to iterate quickly, and you can test each step as you go. Most users have a functional Onfleet automation running within their first hour of setup. For notifications, you can easily connect to Discord or Twilio for SMS alerts.
