--- title: Zowie API Integration on Truto slug: zowie category: Helpdesk canonical: "https://truto.one/integrations/detail/zowie/" --- # Zowie API Integration on Truto **Category:** Helpdesk **Status:** Generally available ## How it works 1. **Link your customer's Zowie account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app. 2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request. 3. **Call Truto's API to reach Zowie.** The Proxy API is a 1-to-1 mapping of the Zowie API. 4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field. ## Use cases - **Automate returns directly inside the chat widget** — Returns management platforms can integrate with Zowie so that when a customer initiates a return via chat, the bot checks policy eligibility, generates a return label, and delivers it in-thread — all without human intervention. Offering this as a native integration makes the returns product omnipresent in the merchant's support flow. - **Enrich CRM profiles with support-derived intent and sentiment data** — CRM and marketing automation platforms can listen to Zowie's intent tags and sentiment signals from live conversations. When the bot detects a customer asking about a sold-out product or expressing churn risk, that zero-party data flows into the CRM for segmentation and re-engagement campaigns. - **Unify voice and chat interactions in a single omnichannel view** — Telephony and CCaaS providers can sync call recordings, transcripts, and caller identity into Zowie Inbox, ensuring voice interactions don't live in a silo. This gives agents full conversation history across channels and keeps the voice platform deeply embedded in the merchant's support stack. - **Surface AI-driven revenue attribution in BI dashboards** — Analytics and business intelligence tools can pull Zowie's revenue attribution data to show merchants exactly how much revenue their AI support agent generates. Correlating cost-per-resolution with support-driven sales alongside ad spend gives merchants a holistic profitability picture. - **Trigger downstream actions from bot-resolved conversations** — Billing, subscription, and logistics platforms can expose action endpoints that Zowie calls mid-conversation — pausing a subscription, issuing a refund, or updating a shipping address. Offering this integration lets the SaaS product participate in fully autonomous resolution workflows without requiring agent involvement. ## What you can build - **Real-time conversation and ticket sync** — Pull Zowie ticket objects — including full interaction history, channel type, timestamps, and resolution status — into your product to keep external systems in lockstep with the support queue. - **Intent-based customer tagging pipeline** — Consume Zowie's AI intent classifications (e.g., refund_request, shipping_delay) and automatically tag or segment customer profiles in your platform for targeted follow-up. - **Webhook-driven escalation alerts** — Subscribe to Zowie events like handover.requested or ticket.resolved to trigger workflows in your product the moment a conversation changes state. - **Contextual data injection for bot accuracy** — Push live order status, subscription details, or return eligibility from your backend into Zowie's bot context so it can answer customer questions with real-time data. - **Support-driven revenue reporting** — Ingest Zowie's revenue attribution metrics to display how AI-recommended products convert to sales, giving merchants clear ROI visibility inside your analytics product. - **Customer profile merge and metadata sync** — Sync user metadata captured by Zowie — email, phone, VIP status, sentiment scores — into your CRM or CDP to maintain a single enriched customer record. ## FAQs ### Is the Zowie integration available as a pre-built connector on Truto? The Zowie integration is built on request. Once you signal interest, Truto builds and maintains the connector — including auth, pagination, and error handling — so you don't have to manage Zowie's API quirks yourself. ### What authentication method does Zowie use? Zowie's API typically uses API key-based authentication. Truto handles the credential exchange and token management on behalf of your end users, so they can connect their Zowie accounts through a guided auth flow. ### What types of data can be accessed from Zowie? Zowie exposes ticket and conversation objects (text, email, voice), AI intent and resolution tags, customer metadata, revenue attribution metrics, and webhook events for real-time state changes like conversation starts, handovers, and resolutions. ### Does Zowie support webhooks for real-time sync? Yes. Zowie provides webhooks for key events such as conversation.started, handover.requested, and ticket.resolved. These can be used to keep your system synchronized without polling. ### Can I write data back to Zowie, or is it read-only? Zowie supports bidirectional workflows. You can push contextual data (like order status or return eligibility) into active bot sessions and trigger actions within conversations, not just read ticket data. ### How does Truto handle Zowie-specific API quirks like rate limits and pagination? Truto abstracts away rate limiting, pagination, and retry logic at the connector level. When the Zowie integration is built, these details are handled transparently so your engineers interact with a consistent, predictable API surface.