# Tookan integrations: tasks, agents and customers

> Create a task, add an agent and add a customer in Tookan, and start a workflow when Tookan sends “Task status updated”.

**Canonical page:** https://tray.ai/connectors/tookan-integrations/
**Categories:** Supply chain
**Connects through:** HTTP Connector

## Overview

Tookan is a delivery and field workforce management tool from Jungleworks for creating tasks, dispatching agents, tracking routes and managing customers and merchants. Tray.ai connects to Tookan through the HTTP Connector, so your workflows can call the Tookan API alongside the rest of your stack.

## Use cases

### Tasks

Read, create, update, and delete tasks in Tookan from any Tray.ai workflow. The Tookan API covers calls such as create a task and get task details.

- Create a task
- Get task details
- Edit a task

### Agents

Read, create, update, and delete agents in Tookan from any Tray.ai workflow. The Tookan API covers calls such as list agents and add an agent.

- List agents
- Add an agent
- Edit an agent

### Customers

Read, create, update, and delete customers in Tookan from any Tray.ai workflow. The Tookan API covers calls such as list customers and add a customer.

- List customers
- Add a customer
- Edit a customer

### Teams

Read, create, update, and delete teams in Tookan from any Tray.ai workflow. The Tookan API covers calls such as create a team and update a team.

- Create a team
- Update a team
- Delete a team

### Merchants

Read, create, update, and delete merchants in Tookan from any Tray.ai workflow. The Tookan API covers calls such as create a merchant and view merchants.

- Create a merchant
- View merchants
- Edit a merchant

## Challenges Tray.ai solves

### Keeping Tookan credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Tookan credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Tookan API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Tookan API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Tookan?

Yes. Tray.ai connects to Tookan through the HTTP Connector, which calls the Tookan API directly. Any call the Tookan API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Tookan?

The Tookan API uses an API key in the request body. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Tookan connector?

Tookan runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Tookan connector from the Tookan API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/