--- title: "Thiio Integration" description: "Thiio is a MarTech platform for direct response commerce with leads, orders, subscriptions and fulfillment. Agents create and enrich leads, read and fulfill orders, manage subscriptions, and react to order and subscription events through a realtime trigger." url: https://flowrunner.ai/integrations/thiio date_modified: 2026-09-04T19:08:45-07:00 --- # Thiio [E-commerce](https://flowrunner.ai/integrations/category/e-commerce) Thiio is a MarTech platform for direct response commerce with leads, orders, subscriptions and fulfillment. Agents create and enrich leads, read and fulfill orders, manage subscriptions, and react to order and subscription events through a realtime trigger. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 1 trigger · 11 actions · Session · available [Thiio website](https://thiio.com/) · [Platform Documentation](https://thiio.com/) · Capability data verified 2026-08-26 1. On Thiio Event reports a failed subscription payment 2. Agent reads the subscription, its contact and its transaction history through List Records 3. Agent confirms the delivery matches a subscription that actually exists on the instance 4. Agent counts the previous failures on the same subscription and the contact's order history 5. Create Cart builds a recovery cart and returns a secure checkout URL for that contact 6. Agent posts the case, the recurring amount at risk and the recovery link to the retention channel 7. The retention owner chooses between sending the recovery link and calling Cancel Subscription ## What This Integration Enables Thiio is built around the lead rather than the order, which is what makes it a direct response platform rather than a storefront. The contact exists before the sale does, so the connector's shape follows: Create Lead captures the contact on its own, Create Lead With Order captures the contact and the purchase in a single call, and Create Cart hands back a secure checkout URL when the sale needs to be finished by the buyer. Seven collections, from customers and orders through subscriptions and transactions, come from one route, so List Records is a single operation with a picker instead of seven near-identical ones. Two facts shape how these flows should be built. Every Thiio customer runs on their own instance domain, so the connection points at your host rather than at a shared API. And the trigger's deliveries carry no signature, which is a design constraint worth respecting rather than routing around: it is the reason the consequential calls on this connector belong behind [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) rather than behind an event handler. ### Without FlowRunner **Leads and orders live apart**: The contact is captured in one tool and the sale in another, so attribution is reassembled by hand **Failed payments surface late**: A declined rebill is noticed on a report rather than on the day it happens **Cancellations by inbox**: Retention decisions arrive as forwarded emails with no record of who decided ### With FlowRunner **One call captures both**: The lead and its order are written together, so the contact and the sale share a record from the start **Declines open a case**: A failed rebill produces a case with the amount, the history and a working recovery link attached **The ending is a decision**: Cancelling a paying subscriber is an explicit human call with the evidence beside it ## Use Case Scenarios ### A lead and its order captured in the same breath An inbound response arrives from a landing page or a call center handoff. The agent normalizes the contact, resolves the offer against List Products and List Categories so the identifiers are real ones, and calls Create Lead With Order. Where the buyer still has to pay, it calls Create Cart instead and returns the secure checkout URL, which then goes out through [Gmail](https://flowrunner.ai/integrations/gmail-service) or an SMS step. The contact and the purchase enter Thiio together, so nobody has to reconcile a lead list against an order list afterward. ### Fulfillment writes tracking back where support looks for it The warehouse or the 3PL confirms a shipment. The agent matches it to the Thiio order through List Records, then calls Update Shipping Tracking Info to set the carrier and the tracking number on the shipment itself. A row lands in [Google Sheets](https://flowrunner.ai/integrations/google-sheets) for the daily fulfillment view, and a summary posts to [Slack](https://flowrunner.ai/integrations/slack). When a customer asks where their order is, the answer is already on the record the support agent has open. ### Dunning that ends with a person, not a rule The trigger reports a failed subscription payment. The agent assembles the case: how many times this subscription has failed, what the contact has bought before, and what the recurring amount is. It builds a recovery cart so the retention owner has a working link in hand, and posts the whole thing to the retention channel. The agent does not cancel anything. It prepares the two options and waits, because on this connector one of those options cannot be taken back. ## Human-in-Loop Highlight Cancel Subscription is where this connector earns a gate, for two reasons that compound. Thiio's webhook deliveries are unsigned, so the callback URL is the only secret protecting them, and an agent cannot prove that a "payment failed" event came from Thiio rather than from anyone who learned the URL. And this connector has no resume, reactivate or reinstate operation, because Thiio does not offer one: a cancellation is an ending, not a pause. So the retention agent posts into the channel instead: "An unsigned event reports the third failed payment on subscription 88213, recurring at 49 a month, customer has four completed orders. I have verified the subscription through List Records and built a recovery cart. Send the recovery link, or cancel?" The owner picks. What made this safe was not the agent's judgment about the customer. It was that the one call with no way back was never the agent's to make on the word of an event it could not authenticate. 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 11 actions ### Connection and Records 2 - **Test Connection** Logs in, validates the token and returns the integration identifier that webhook subscriptions are keyed on. The connection test, and the only source of that identifier. - **List Records** Reads customers, orders, shipments, subscriptions, surveys, transactions or transaction histories with paging. One operation with a picker, because Thiio serves all seven from the same route. ### Leads and Orders 5 - **Create Lead** Creates a lead from a contact on the shared ingest route. The capture step for a response that has not become a sale yet. - **Create Lead With Order** Creates a lead and its order in one call, and raises when the vendor reports a failure inside an otherwise successful response. Used when the response and the purchase arrive together. - **Update Shipping Tracking Info** Sets the carrier and tracking number on a shipment. The write that closes the loop back from a warehouse or a 3PL to the record support reads from. - **Cancel Subscription** Cancels a subscription, using the route that actually exists rather than the one the vendor documents. There is no reinstate counterpart, which is why this page puts a person in front of it. - **Create Cart** Creates a cart from a contact and its items and returns a secure checkout URL. The recovery and finish-the-sale step, since the buyer completes payment themselves. ### Catalog 3 - **List Products** Lists the instance products, which supply the identifiers a cart item has to refer to. Used to resolve an offer name into something Thiio will accept. - **List Categories** Lists the instance product categories. Used to route an offer or to filter a catalog sync. - **List Tags** Lists the instance tags. Used to segment contacts and orders consistently with how the marketing team already labels them. ### Direct API Access 1 - **Make API Call** Calls any path on your Thiio instance directly, for the undocumented collections this connector does not name. ## Triggers 1 triggers ### Event Triggers 1 - **On Thiio Event** Fires when Thiio reports an order or subscription event on your instance. Deliveries are unsigned, so the callback URL is the only secret protecting them: treat an event as a reason to look, verify what it claims through List Records, and keep the irreversible calls behind a person. ## Frequently Asked Questions ### What can FlowRunner do with Thiio? FlowRunner agents can run Test Connection, List Records, and Create Lead in Thiio, plus 8 more actions. ### Does connecting Thiio to FlowRunner require OAuth? No. Thiio connects to FlowRunner with session-based authentication, no OAuth flow required. ### Can Thiio trigger a FlowRunner workflow automatically? Yes. Thiio supports 1 trigger that can start a FlowRunner workflow automatically. **Work at Thiio?** This integration exposes Thiio 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/thiio. Site index: https://flowrunner.ai/llms.txt