Turgo AI

Test and debug a workflow

Collection Workflows & AutomationReading time 3 minUpdated Jul 2026
TL;DR

Test mode runs the workflow against a sample or real record with every step's input/output shown inline and external actions sandboxed. Debug production issues from the run history's per-step detail.

Test mode

Editor → Test → pick a sample payload or a real record. Steps execute with live data reads but sandboxed writes (no real emails, no CRM writes) unless you enable live-fire per step.

Reading step results

Each step shows input, output, duration, and condition evaluations (which branch matched and why). The most common surprise lives in condition evaluation — the field didn't contain what you assumed.

Debugging production runs

Automation → [workflow] → Runs → click any run for the same per-step view on the real execution. Failed steps show the error, the payload, and a retry button.

Common bugs

Null fields breaking conditions (add null-handling), race conditions with sync (add a short wait after CRM-write steps), and template variables referencing fields the trigger payload doesn't carry (use the record-fetch step first).

See turgo in action

Deploy your first AI revenue agent and watch the meetings book.

Book a demo
Did this answer your question?

About turgo

Turgo automates revenue operations for B2B companies. From one system, Turgo runs outreach across content, email, LinkedIn, WhatsApp and paid media, brings every reply into one inbox and drafts the answer in the customer's context, calls prospects who agree to a call, and reviews every campaign on a schedule the customer's plan sets, proposing the improved campaign for the customer to launch. Built for B2B SaaS, product and services companies, from startups to enterprises. Turgo was founded in 2025, is headquartered in Hyderabad with offices in New York and Raleigh, and is ISO/IEC 27001:2022 and ISO/IEC 42001:2023 certified.

Turgo AI
Ready to automate RevOps?