--- title: "Tookan Integration" description: "Connect AI agents to Tookan, the Jungleworks delivery management platform. Agents create and edit delivery tasks, find available agents, assign work to fleets, track task status, and pull customer records to automate last-mile dispatch end to end." url: https://flowrunner.ai/integrations/tookan date_modified: 2026-08-04T10:04:16-07:00 --- # Tookan [Logistics](https://flowrunner.ai/integrations/category/logistics-fulfillment) Connect AI agents to Tookan, the Jungleworks delivery management platform. Agents create and edit delivery tasks, find available agents, assign work to fleets, track task status, and pull customer records to automate last-mile dispatch end to end. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 9 actions · API key · available [Tookan website](https://tookanapp.com/) · [Platform Documentation](https://tookanapp.com/api-docs/) · Capability data verified 2026-07-28 1. A new order arrives from the storefront or CRM 2. Get All Customers resolves the recipient's saved address and contact details 3. Create Task creates the delivery with coordinates, contact details, and a unique order ID 4. Get Available Agents returns the fleets near the pickup point 5. The dispatcher confirms the proposed agent when the assignment is ambiguous, the address geocodes oddly, or the delivery window is tight 6. Assign Task hands the job to the chosen fleet 7. Get Task Details polls the status until it reports Successful or Failed 8. The outcome posts to the dispatch channel, with failures flagged for follow-up ## What This Integration Enables Last-mile dispatch is a coordination problem wearing a logistics costume: orders arrive in one system, drivers live in another, and the dispatcher is the API between them. Tookan gives that middle layer real structure, and FlowRunner agents operate it end to end. They create and edit pickup and delivery tasks from incoming orders, find available agents near a location, assign work to fleets, track every job to a terminal status, and pull customer records so recipient details are populated instead of retyped. - Turn [Shopify](https://flowrunner.ai/integrations/shopify) orders into dispatched delivery tasks without a human in the retyping loop - Shortlist the nearest available fleets and assign work with a dispatcher's confirmation on edge cases - Reschedule and correct tasks programmatically when customers change plans - Sync task outcomes to [Slack](https://flowrunner.ai/integrations/slack) and [Google Sheets](https://flowrunner.ai/integrations/google-sheets) so ops sees the day's deliveries without opening Tookan - Mirror or migrate jobs between dispatch platforms like [Onfleet](https://flowrunner.ai/integrations/onfleet) during transitions The point is not removing the dispatcher. It is removing the data entry and the tab-switching so the dispatcher's judgment lands only where judgment is needed: the ambiguous address, the tight window, the driver trade-off. ### Without FlowRunner **Orders wait for a dispatcher**: Every incoming order sits in a queue until someone retypes it into Tookan **Assignment by gut and memory**: Whoever seems free gets the job, and nobody checks who is actually closest **Status lives in the app**: The ops team learns about a failed delivery when the customer calls ### With FlowRunner **Orders become tasks on arrival**: E-commerce and CRM orders create pickup and delivery tasks with clean data, immediately **Assignment starts with proximity**: The agent shortlists nearby fleets and a person rules on the edge cases **Failures are routed, not discovered**: Task status syncs back to your systems and failed jobs open follow-ups automatically ## Use Case Scenarios ### Order to doorstep without a copy-paste A [Shopify](https://flowrunner.ai/integrations/shopify) order fires On New Order. The agent checks Get All Customers for a saved address, creates the delivery with Create Task including coordinates and the order ID, then calls Get Available Agents for the pickup location. The nearest fleet with availability gets the job through Assign Task. From order placed to driver assigned, no human touched a keyboard, and the dispatcher's queue holds only the orders the agent flagged as ambiguous. ### The delivery day, visible Each morning, Get All Tasks pulls everything created in the last 24 hours, filtered by status. Unassigned tasks post to the dispatch channel in [Slack](https://flowrunner.ai/integrations/slack) for triage. Every task logs a row in [Google Sheets](https://flowrunner.ai/integrations/google-sheets) with status, agent, and timestamps. Through the day, Get Task Details polls active jobs; a Failed status opens an exception with the customer's contact details attached, so the follow-up call happens while the driver is still nearby, not tomorrow. ### The reschedule that does not cascade A customer replies to the confirmation message asking to move delivery to Thursday. The agent pulls the job with Get Task Details, drafts the change, and calls Edit Task with only the new delivery datetime, leaving every other field untouched. If the new window collides with the assigned fleet's schedule, the agent re-runs Get Available Agents and proposes a reassignment to the dispatcher rather than silently swapping drivers. The change lands in Tookan, the driver's app, and the tracking sheet in one pass. ## Human-in-Loop Highlight Delete Task permanently removes a delivery job from the account, and Tookan cannot restore it. A deleted task takes its status history, its customer details, and its place in the day's route math with it, so an agent that deletes the wrong job ID has not made a reversible mistake, it has erased the record of a delivery that may already have a driver en route. FlowRunner flows therefore treat deletion as a proposal: the agent identifies the duplicate or cancelled job, pulls its full record with Get Task Details, and presents it to the dispatcher with the evidence, "Task 8834412 duplicates 8834409: same order ID, same address, created 40 seconds apart. Delete the newer one?" Only a yes runs the delete. Assign Task gets a lighter version of the same gate, because assigning a fleet sends a real person driving to a real address, and the agent's proximity math should be confirmed by someone who knows that Route 9 is closed this week. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 9 actions ### Tasks 5 - **Create Task** Creates a pickup and/or delivery task with the matching datetimes, coordinates, customer contact details, and a unique order ID so the job can be located, tracked, and auto-assigned. The entry point for every dispatch flow. - **Get Task Details** Retrieves a single task by job ID: status, assigned agent, timestamps, customer information, and geo-coordinates. The polling step behind status tracking and the evidence-gathering step before any edit or delete. - **Get All Tasks** Lists tasks with optional status and creation date filters, such as Successful, Failed, or Unassigned. The read behind daily dispatch digests and exception sweeps. - **Edit Task** Updates an existing task by job ID, sending only the fields that change. The reschedule and correction tool: new delivery windows, fixed addresses, updated contact details. - **Delete Task** Permanently deletes a task by job ID. Cannot be undone, which is why this connector's flows put a dispatcher between the agent and this call. ### Agents 3 - **Get Available Agents** Returns the delivery agents available near a given latitude and longitude. The shortlist step before assignment. - **View All Fleets** Retrieves every registered delivery agent with IDs, names, contact details, and availability. The roster read for assignment, coverage checks, and reporting. - **Assign Task** Assigns an existing task to a specific fleet by ID. The action that puts a driver on the road, confirmed by a dispatcher whenever the choice is not obvious. ### Customers 1 - **Get All Customers** Retrieves all stored customers with names, phone numbers, emails, and saved addresses. The lookup that populates recipient details so nobody retypes them. ## Frequently Asked Questions ### What can FlowRunner do with Tookan? FlowRunner agents can run Create Task, Get Task Details, and Get All Tasks in Tookan, plus 6 more actions. ### Does connecting Tookan to FlowRunner require OAuth? No. Tookan connects to FlowRunner with an API key, no OAuth flow required. ### Can Tookan trigger a FlowRunner workflow automatically? Tookan doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Tookan?** This integration exposes Tookan to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/tookan. Site index: https://flowrunner.ai/llms.txt