Skip to content
English
  • There are no suggestions because the search field is empty.

CloneOps Integration Setup Guide

The CloneOps integration connects your Tai TMS to CloneOps, enabling AI agents to complete automated tasks. 

Full Logo Color B

Overview

The CloneOps integration connects your Tai TMS to CloneOps AI agents, enabling automated ai calls for any shipment. When triggered — either on a schedule or manually — Tai sends the full shipment payload to the designated CloneOps agent. 

This guide covers the four steps required to configure the integration:

  1. Generate a Tai API key for CloneOps
  2. (Tai Support Task) hires CloneOps Marketplace Agent 
  3. Create the Workflow External Action Integration
  4. Configure Workflow Automations to trigger the agent
  5. Use manual check call options (optional)

Prerequisites

Before beginning setup, obtain the following from your Tai Support Member account representative:

Value Description
Agent ID Identifies which CloneOps agent to invoke (e.g., the Check Call agent). Provided by Tai Support Member.
Account Number Your organization's sub-account number within CloneOps. Provided by Tai Support Member.

You will also need TMS Site Admin rights in Tai to complete setup.


Step 1 — Generate a Tai API Key for CloneOps

CloneOps uses a Tai-issued API key to write data back into your TMS (location updates, tracking statuses, activity logs, resolved alerts). You must generate this key and provide it to CloneOps.

  1. Log in to Tai TMS and navigate to the Back Office environment.
  2. Click the LSP tab in the left-hand menu.
  3. Select Public Authentication Keys from the dropdown.
  4. Click Add Public Authentication Key (top right).
  5. In the Organization field, select the relevant organization.
  6. Select the appropriate staff user — a dedicated service account is recommended (e.g., "CloneOps Agent" or "AI Agent").
  7. Click Save. The generated key will appear in the Authentication Key column.
  8. Copy this key and provide it to Tai Support.

Note: The staff account selected here will be recorded as the author of any activity logs or alert resolutions CloneOps writes back into Tai. Using a named service account (rather than a personal user account) keeps your audit trail clean.


Step 2 — Contact Tai Support to Add CloneOps Agent from Marketplace

In CloneOps Marketplace, there's a wide variety of Agents that could be hired and added to your account. 

  1. Reach out to support@tai-software.com to request the CloneOps Agent
  2. Support will provide back an AgentId and AccountNumber

Note:  Currently only CheckCall Agent is available from CloneOps Marketplace


Step 3 — Create the CloneOps Integration Source

The Integration Source tells Tai where to send shipment data and how to authenticate with CloneOps.

  1. In Tai TMS, navigate to Settings > Integrations > Integration Sources.
  2. Click Add Integration Source.
  3. Configure the following fields:
Field Value
Name A descriptive label, e.g., CloneOps Check Call
Source Type Workflow External Action
License Key Your CloneOps Agent ID
Account Number Your CloneOps Account Number
Linked Organization Select the broker organization this integration applies to
  1. Under Integration Source Parameters, add the following Parameters:
Name Value
url This will be added by the Tai IT Support Team
Header_x-api-code This will be added by the Tai IT Support Team
agentType Basic Description of Agent, e.g. CheckCall


  1. Click Save.

Step 4 — Configure Workflow Automations

Once the Integration Source is saved, you can configure two Workflow Automation schedules to control when check calls are triggered. Two schedules are needed: one for shipments that have never had a check call, and one for shipments where a prior check call has already been completed.

Navigate to Settings > Workflow Automations and create the following:


Schedule A — Initial Check Call (No Prior Alert)

This schedule triggers a check call for any active shipment that has not yet had an AI Agent Call alert.

Setting Value
Trigger Type Shipment Scheduler
Frequency Daily — e.g., 9:00 AM
Filter: Alert Does Not Contain → AI Agent Call
Filter: Resolved Alert Does Not Contain → AI Agent Call
Action Type Call AI Agent Action - Select your CloneOps Integration Source (e.g., CloneOps Check Call)

Note: Add any additional shipment filters as needed — for example, limiting to Truckload shipments only, or filtering by status prior to the Action Type.


Schedule B — Recurring Check Call (Prior Alert Resolved)

This schedule re-triggers the check call for shipments where a previous AI Agent Call alert was resolved at least one day ago, preventing duplicate same-day calls.

Setting Value
Trigger Type Shipment Scheduler
Frequency Daily — e.g., 9:00 AM
Filter: Resolved Alert AI Agent Call — Resolved Date ≤ Yesterday
Action Type Call AI Agent Action - Select your CloneOps Integration Source (e.g., CloneOps Check Call)

Note: Add any additional shipment filters as needed — for example, limiting to Truckload shipments only, or filtering by status prior to the Action Type.


Step 5 — Confirm Setup with Support

After the initial setup has been completed, Tai Support Team will need to validate the setup, and add the final fields to enable the AI Agent.


How the Alert Cycle Works

When a check call is triggered:

  1. Tai sends the shipment payload to CloneOps.
  2. An AI Agent Call alert is added to the shipment (unresolved).
  3. CloneOps contacts the Call Recipient and captures any updates.
  4. CloneOps pushes results back to Tai via the API key generated in Step 1.
  5. CloneOps resolves the AI Agent Call alert.
  6. On the next scheduled run, Schedule B detects the resolved alert and re-triggers the process.

This cycle can repeat until the shipment is delivered. ADD Shipment Status  Dispatched --> Out for delivery. 


Step 4 — Manual Check Call Options (Optional)

In addition to automated scheduling, users can trigger a CloneOps check call manually. Manual options are only available on shipments whose organization is linked to a CloneOps Integration Source.


Option A — From the Check Call Modal

  1. Open the shipment and open the Check Call panel.
  2. Click Call AI Agent at the bottom of the modal.
  3. The API call fires and the AI Agent Call alert is added to the shipment.

Option B — From Shipment Search (Bulk)

  1. Navigate to Shipment Search and select one or more shipments.
  2. Open Bulk Operations.
  3. Select Call AI Agent.
  4. The API call fires for all selected shipments.

Option C — From Company Loadboard (Bulk)

  1. Navigate to the Company Loadboard.
  2. Select one or more shipments via Bulk Operations > Check Call.
  3. Select  Request AI Agent Call.
  4. The API call fires for all selected shipments.

Note: When a check call is triggered manually, Tai also passes the Staff ID of the user who initiated it, which is recorded in the activity log.


Troubleshooting

Symptom Likely Cause Action
"Request AI Check Call" option not visible Organization is not linked to a CloneOps Integration Source Verify the Linked Organization field in the Integration Source
Alert is added but never resolves CloneOps does not have the correct Tai API key Confirm the key provided in Step 1 is active and associated with the correct organization
Duplicate check calls firing Schedule B filter is misconfigured Confirm the Resolved Alert filter is set to ≤ Yesterday, not Today
API call fails at trigger Header parameter name is incorrect Confirm the header name format with your CloneOps representative

Summary of Credentials

Credential Source Where It Goes in Tai
CloneOps Agent ID CloneOps Integration Source → License Key field
CloneOps Account Number CloneOps Integration Source → Account Number field
Tai API Key Generated in Tai (Step 1) Provided to Tai Support by you