Airtable to Onfleet, dispatch tasks created for you
Dispatch gets messy when Airtable is “the plan” and Onfleet is “the truth.” Someone has to copy addresses, time windows, notes, and customer details over by hand. And that’s where mistakes sneak in.
Operations managers feel it first. Then dispatch leads and small business owners get pulled in to double-check details. This Airtable Onfleet tasks automation keeps tasks current without constant admin work.
You’ll set up an n8n workflow that watches for new Airtable rows and turns them into Onfleet delivery tasks automatically, so your team can focus on actually moving orders.
How This Automation Works
Here’s the complete workflow you’ll be setting up:
n8n Workflow Template: Airtable to Onfleet, dispatch tasks created for you
flowchart LR
subgraph sg0["Airtable Poll Flow"]
direction LR
n0["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/airtable.svg' width='40' height='40' /></div><br/>Airtable Poll Trigger"]
n1["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/Onfleet.svg' width='40' height='40' /></div><br/>Onfleet Task Creator"]
n0 --> n1
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n0 trigger
classDef customIcon fill:none,stroke:none
class n0,n1 customIcon
Why This Matters: Dispatch Breaks When Data Lives in Two Places
If your “order list” lives in Airtable but your drivers live in Onfleet, you’re stuck doing the same translation all day. A new delivery comes in, someone opens the base, copies the customer name, pastes the address, retypes the phone number, and tries to squeeze notes into the right spot. Then you do it again for the next row. It’s not hard work. It’s fragile work. One missed apartment number or a swapped phone digit can mean a late delivery, a driver call you didn’t need, and a customer who doesn’t trust your ETA anymore.
The friction compounds. Here’s where it breaks down in real teams.
- Copying fields from Airtable into Onfleet invites small errors that turn into big reroutes.
- Dispatch gets out of date fast when new rows appear but tasks don’t, so drivers are looking at the wrong workload.
- People create their own “quick fix” process, which means every shift does it differently.
- When volume spikes, the backlog is manual entry, not deliveries.
What You’ll Build: Airtable Rows That Become Onfleet Tasks
This workflow connects Airtable and Onfleet so your dispatch system stays in sync with the moment a delivery record is created. It starts by polling Airtable on a schedule (the template defaults to every 10 minutes). When a new row appears, n8n grabs the fields you care about, like recipient name, address, phone, and delivery notes, then sends them into Onfleet’s “create task” action. A fresh Onfleet task is created automatically, ready for dispatch and route planning. No extra tabs, no “did anyone enter this one yet?” messages, and far fewer typos.
The workflow starts in Airtable, where your team adds one record. n8n turns that record into a structured Onfleet task. From there, dispatch runs the day inside Onfleet like normal.
What You’re Building
| What Gets Automated | What You’ll Achieve |
|---|---|
|
|
Expected Results
Say you create 25 delivery records a day in Airtable. Manually building an Onfleet task usually takes about 3 minutes once you include checking the address, copying notes, and fixing formatting, which is roughly 75 minutes daily. With this workflow, you add the Airtable record (you’re doing that anyway) and wait for the next poll cycle, which is up to 10 minutes. You get back about an hour a day, and the tasks are more consistent.
Before You Start
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Airtable for the source delivery/order table.
- Onfleet to create and manage delivery tasks.
- Onfleet API key (get it from your Onfleet account after signup).
Skill level: Beginner. You’ll connect Airtable and Onfleet, then map a few fields.
Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).
Step by Step
Airtable triggers the workflow. n8n checks your chosen base and table for new rows on a schedule (the template uses a 10-minute polling interval, but you can change it).
Row data is collected and prepared. The workflow reads the new record’s fields and lines them up with what Onfleet needs to create a task, so addresses and notes land in the right places.
Onfleet creates the delivery task. n8n uses your Onfleet credentials and API key to create a task automatically, using the mapped Airtable values.
Your dispatch view stays clean. Tasks show up in Onfleet ready to assign, route, and communicate with drivers, without a second data entry step.
You can easily modify the Airtable field mapping to include more task details (like time windows or special instructions) based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Airtable Trigger
Set up the workflow to poll Airtable for new or updated records and use a specific field to detect changes.
- Add the Airtable Poll Trigger node as your trigger.
- Set Poll Times to run every
10minutes. - Set Trigger Field to
Address_Line1. - Credential Required: Connect your airtableApi credentials.
Address_Line1, City/Town, State/Province) to avoid missing data.Step 2: Connect Airtable Data Source
Validate that your Airtable schema provides all delivery details used downstream.
- Ensure your Airtable table includes the fields
Address_Line1,City/Town,State/Province,Country,Postal_Code,Task_Details,Recipient_Name,Recipient_Notes,Recipient_Phone,completeAfter, andcompleteBefore. - Keep Flowpast Branding as a documentation-only node if you want the in-workflow tutorial reference; it does not affect execution.
Step 3: Configure Onfleet Task Creation
Create a delivery task in Onfleet using the Airtable record details pulled by the trigger.
- Add the Onfleet Task Creator node and connect it to Airtable Poll Trigger.
- Set Operation to
create. - In Destination → Address, use the expression:
={{$node["Airtable Poll Trigger"].json["fields"]["Address_Line1"]}}, {{$node["Airtable Poll Trigger"].json["fields"]["City/Town"]}}, {{$node["Airtable Poll Trigger"].json["fields"]["State/Province"]}}, {{$node["Airtable Poll Trigger"].json["fields"]["Country"]}}, {{$node["Airtable Poll Trigger"].json["fields"]["Postal_Code"]}} - In Additional Fields → Notes, use:
={{$node["Airtable Poll Trigger"].json["fields"]["Task_Details"][1]}} {{$node["Airtable Poll Trigger"].json["fields"]["Task_Details"][0]}} - In Additional Fields → Recipient, set:
Recipient Name to={{$node["Airtable Poll Trigger"].json["fields"]["Recipient_Name"]}}
Recipient Notes to={{$node["Airtable Poll Trigger"].json["fields"]["Recipient_Notes"]}}
Recipient Phone to=+1{{$node["Airtable Poll Trigger"].json["fields"]["Recipient_Phone"]}} - Set Complete After to
= {{$node["Airtable Poll Trigger"].json["fields"]["completeAfter"]}}and Complete Before to= {{$node["Airtable Poll Trigger"].json["fields"]["completeBefore"]}}. - Credential Required: Connect your onfleetApi credentials.
Task_Details field is not an array, the index-based expressions ([1] and [0]) will fail. Ensure the Airtable field type matches the expected structure.Step 4: Test and Activate Your Workflow
Run a manual test to confirm tasks are created in Onfleet and then activate the workflow for continuous polling.
- Click Execute Workflow and add or update a record in Airtable that changes
Address_Line1. - Verify the Onfleet Task Creator node succeeds and a new task appears in Onfleet with the correct address and recipient details.
- If the output is correct, toggle the workflow to Active to begin polling every 10 minutes.
Troubleshooting Tips
- Onfleet credentials can expire or lack the right permissions. If task creation fails, check your API key in the Onfleet dashboard first, then re-save credentials in n8n.
- Airtable polling depends on the table and view setup. If you’re not seeing new rows picked up, confirm the Base ID and table name match exactly and that the trigger is looking at the right place.
- Field mapping issues are the sneaky ones. If addresses are malformed or notes are missing, verify the Airtable columns aren’t empty, and make sure the Onfleet task fields are mapped to the right Airtable properties.
Quick Answers
About 30 minutes if your Airtable base and Onfleet account are ready.
No. You’ll mainly connect accounts and map Airtable columns to Onfleet task fields.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Onfleet costs based on your Onfleet plan (the workflow uses your Onfleet API key).
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, and you probably should. The main customization is in the Onfleet Task Creator mapping, where you can pass additional Airtable fields like delivery time windows, driver notes, or recipient phone numbers. If your Airtable has multiple “task types,” you can also add an If step before task creation to route records to different settings. The template is simple by design, so extending it is straightforward.
Usually it’s an API key issue. Regenerate or re-copy your Onfleet API key and update the credentials in n8n, then run the workflow once to confirm it can create a test task. If that still fails, check that your Onfleet account has access to task creation and that you’re not hitting rate limits during bulk runs.
A lot for a workflow this small, honestly. On n8n Cloud, your limit is mostly your plan’s monthly executions, because each new Airtable row typically equals one execution. If you self-host, there’s no execution cap, but your server and Airtable/Onfleet API limits become the bottleneck. Practically, most teams can process dozens to hundreds of tasks a day without thinking about it, as long as the polling interval and API limits are sensible.
Often, yes, especially once you add branching rules or extra validation. n8n is flexible when you want conditional logic (like “only create tasks when status = Ready”) and it won’t punish you for more complex flows. Zapier and Make are still fine if you want a very simple two-step setup and don’t expect to customize much. If you’re unsure, Talk to an automation expert and we’ll point you in the right direction.
Once this is running, Airtable becomes the only place your team has to “enter” delivery data. Onfleet stays current automatically, which means fewer errors and a calmer dispatch board.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
