What does Zatanna do?

Zatanna maps human-only software workflows and exposes them as reliable APIs. Instead of building brittle browser automation scripts, you show the task once and Zatanna reconstructs the underlying request flow into a stable endpoint your AI agents and internal tools can call in production.

How is Zatanna different from web scraping or RPA?

Traditional web scraping replays clicks and waits on page elements, which breaks whenever the UI changes. RPA tools automate screen-level interactions but require constant maintenance. Zatanna reconstructs the actual HTTP request behavior behind a workflow, producing a stable API that doesn't depend on the UI layer at all.

How does Zatanna handle anti-bot detection?

Zatanna manages TLS fingerprinting, proxy rotation, and detection-sensitive request behavior below the API layer. Sessions, cookies, retries, re-authentication, and error recovery are all handled automatically so your integration stays reliable.

What types of workflows does Zatanna support?

Zatanna works best for workflows that are important, repetitive, and stuck behind a UI — including back-office systems with no API, document and record workflows involving uploads, claim forms, and status checks, and AI agent actions in external third-party software.

How do I integrate with Zatanna?

Integration is a three-step process: (1) A human runs the workflow once while Zatanna observes the real behavior, (2) Zatanna builds a request model that reconstructs the calls, state transitions, and recovery logic, (3) Your systems call a single stable API endpoint while Zatanna manages the fragile workflow underneath.

← All articles2026-05-11 · 6 min read

iSolve Produce API Integration: Turning iSolve Pro, iSolvePti, and DoorWiz Workflows Into a Stable API

iSolve is the produce industry's emerging ERP, traceability, and warehouse stack — iSolve Pro, iSolvePti, DoorWiz.ai, tdLoop. Here's how to expose every iSolve workflow as a callable API without browser scripts or waiting on vendor integrations.

TL;DR

iSolve (isolveproduce.com) ships a suite of produce-industry software: iSolve Pro (next-generation produce ERP, 2025), iSolvePti (PTI label printing for FSMA 204 traceability), DoorWiz.ai (AI warehouse door monitoring), and tdLoop (truck driver check-in). Each of these has a web, desktop, or mobile interface — and like most vertical industry software, the official integration surface is narrower than the actual workflows operators run every day. Zatanna captures the real HTTP request behavior behind iSolve's interfaces and turns each workflow into a stable, callable API endpoint.

Why integrating with iSolve is hard

iSolve plays in the same category as Famous Software, Produce Pro, and similar industry-specific ERPs: deeply specialized for fresh produce, packing, traceability, and perishable supply chain. That specialization is exactly why integrating with it is painful:

Vertical software, narrow public surface. Produce ERPs prioritize depth of features over breadth of API coverage. Most operational workflows live in the desktop, web, or mobile client — not in a documented REST API.
Multi-product stack. iSolve Pro, iSolvePti, DoorWiz.ai, and tdLoop are separate products that need to talk to each other and to your TMS, WMS, customer portal, and EDI systems. Each new product adds another integration surface.
Compliance workflows can't be skipped. PTI labeling and FSMA 204 traceability aren't optional — they're regulatory. If a workflow only exists in the iSolvePti UI, you're either doing it by hand or wiring up brittle automation.
Vendor integration roadmaps move slowly. Asking iSolve to build the exact integration you need can take quarters. Workflow APIs give you a path that doesn't depend on the vendor's roadmap.

The practical result: produce operators on iSolve typically have humans re-keying orders between iSolve and their TMS, manually printing PTI labels, watching DoorWiz alerts in a separate window, and reconciling warehouse activity across systems.

How a Zatanna iSolve integration works

Zatanna sits below the iSolve clients. Instead of automating the browser or desktop UI, it captures the actual HTTP requests iSolve's frontends send to their backend when a human performs a workflow. Each captured workflow becomes a stable API endpoint.

The flow:

1. A human runs the iSolve workflow once. Log into iSolve Pro and create an order, print a PTI label in iSolvePti, pull a DoorWiz activity report — Zatanna observes the real network behavior.

2. The request flow is modeled. Authentication, session state, validation calls, and multi-step submissions across desktop, web, and mobile clients are reconstructed.

3. You call one endpoint. Your TMS, WMS, customer portal, AI agent, or internal tool POSTs to a stable URL and gets a structured response.

iSolve workflows commonly exposed as APIs

Produce operators use Zatanna to expose iSolve workflows like:

iSolve Pro: order entry and edits — push orders from a TMS, customer portal, or AI sales agent directly into iSolve Pro without re-keying
iSolve Pro: inventory adjustments and lot tracking — keep iSolve in sync with warehouse scans, repacks, and shrink
iSolve Pro: grower advances and statements — generate and distribute grower payments on a schedule
iSolvePti: PTI label generation — programmatically request and print PTI-compliant labels for FSMA 204 traceability
iSolvePti: traceability event capture — push critical tracking events from your WMS into iSolvePti
DoorWiz.ai: warehouse door activity — pull DoorWiz event streams into your operational dashboards or alerting
tdLoop: driver check-in events — surface check-in status into your TMS in real time
Reporting exports — pull any iSolve report on a schedule and into Snowflake, S3, or BI tools

Migrating from manual entry or in-house scripts

If you have humans re-keying data between iSolve and your other systems, the first endpoint replaces the highest-volume workflow they do. Order entry is usually #1.

If you've built browser or desktop automation against iSolve and it breaks whenever iSolve ships a UI update, each broken script becomes one Zatanna endpoint. The maintenance moves from your team to Zatanna's observability layer, which detects when iSolve's underlying request behavior changes and repairs the integration automatically.

Why workflow APIs beat waiting for vendor integrations

Even if iSolve published an official REST API for every product tomorrow, you'd still face the same gap: official APIs only ever cover the workflows the vendor prioritizes. Workflow APIs cover the workflows *you* care about. The two approaches coexist cleanly — use any official iSolve integration where it works, and Zatanna for everything else.

Getting started with an iSolve integration

Pick the highest-volume iSolve workflow your team performs manually or in scripts — usually order entry, PTI label generation, or a daily reporting export. That's the first endpoint. Once it's live, the second and third workflows take a fraction of the time because authentication and session handling are already in place.

Zatanna's workflow API platform was built specifically for vertical industry software like iSolve, Famous Software, Produce Pro, AppFolio, Yardi, Epicor, and Infor — where the public API can't keep pace with the operational reality. The reliability layer (anti-bot handling, session management, auto-repair) is the same regardless of the target system, so you get production-grade API surface across every iSolve workflow.