Skip to main content
Dooap Studio

What’s new

Shipping, month by month.

A monthly look at what shipped in Dooap Studio — the features that matter most, and a note on everything else. Curated from the same release notes customers see in the product.

September 2026· 2 releases

Actions answer back.

Two releases that make Dooap Studio easier to call and easier to question: Actions that respond over HTTP in real time, Dooap Shepherd working whole runs end to end, and failed Runs that show exactly what never happened.

Call an Action like an API

API Endpoints now support synchronous runs: a connected system calls the endpoint, the Action runs, and a custom HTTP response comes back in real time. Endpoints can publish and enforce response body schemas, and each one gets its own standalone API documentation page — so the team consuming your Action knows exactly what to send and what they’ll get back.

API Endpoints guide

Dooap Shepherd works the whole loop

Dooap Shepherd can now design, run, verify, preview, and approve partial Action runs — useful mid-build, when you want to prove one stretch of a flow before wiring the rest. It also works with mailboxes (email-received Actions, sending, approval-aware archiving), opens Data Files and Data Tables as chat context, and picks up slash commands and clearer progress feedback in chat.

Dooap Shepherd guide

See exactly what ran — and what didn’t

Failed Runs now render the full Action Flow with never-executed Steps dimmed, so where a Run stopped is visible at a glance instead of inferred. The step panel gained partial execution — re-run previous Steps or just the current one while troubleshooting — and version rollback was hardened, with individual versions exportable as an extra safety net.

Runs guide

Also this month: tenant-configurable SFTP connections with built-in file tools, Word and Excel to PDF conversion as a built-in tool, fallback models on Agent steps, the Templates area is now the Library, breadcrumb navigation with an Action switcher, friendlier on mobile, higher execution budgets for Code steps — and 30 more improvements and fixes across 2 releases.

August 2026· 4 releases

New ways in.

Three releases about how work reaches Dooap Studio: email addresses Studio provisions itself, webhooks as first-class Gateways — and Dooap Shepherd settling into its own home in the product.

Gateway Mailboxes: email addresses Studio owns

Create real email addresses that belong to your tenant — as many as you need, no mailbox infrastructure of your own. Email sent to one is received by Studio, scanned for malware, stored with its attachments, and can start an Action Flow automatically: vendors email invoices in, Runs begin. Every email-triggered Run links back to the original message, and quarantine keeps the junk out of your queue.

Gateway Mailboxes guide
Gateway Mailboxes: tenant-owned addresses and the emails they have received.

Webhook Gateways, first-class

Webhooks are now a dedicated Gateway type — set up and manage webhook Triggers in one place instead of per Action. Run details gained a clearer Trigger Details section showing what started the Run and the original Trigger data, and webhook events capture caller details for the audit trail.

Webhook Gateways guide
Webhook Gateways: external systems start Actions through managed endpoints.

Dooap Shepherd moved in

Dooap Shepherd now has its own tab in the left panel — a permanent home rather than a summonable side pane. It also writes Action descriptions on request, so what an automation does is documented at a glance, and it sees both Run input and Step input while helping, so its suggestions come with fuller context.

Dooap Shepherd guide

Also this month: the audit log is now backed by SQL Server ledger tables — append-only and cryptographically verifiable (shipped early August), fractional Work Unit credits, copy and paste Steps in the Action editor, faster structured PDF extraction with better table recognition, “last” as a page selection in OCR and PDF steps, a SharePoint integration guide in the docs — and 34 more improvements and fixes across 4 releases.

July 2026· 2 releases

Ready to roll out.

Two releases aimed at the moment a pilot becomes a rollout: users who provision themselves, and promotions that move as one package.

Sign-in that provisions itself

Connect your Microsoft Entra directory, verify it once, and map Entra groups to Studio roles. From then on, access is managed in your directory: users in a mapped group are provisioned at sign-in with the right role, and anyone removed from the groups loses access the next time they sign in. No hand-managed user list — and offboarding follows your directory automatically.

Identity Provider guide

UAT to production in one package

Action exports now include the App definitions used by assigned tools and inputs. Build custom OpenAPI tools in UAT, export the Action, and import everything into production together — credentials and secrets stay put, and the imported Action arrives disabled until you enable it.

Promotion guide
A custom OpenAPI App — its definition now travels inside the Action export.

Also this month: a built-in Extract PDF Pages Action for big documents, larger uploads with clearer limits, branded Human Task emails and inline file previews, a secret-bindings editor for Code Steps — and 12 more improvements and fixes across 2 releases.

June 2026· 10 releases

Dooap Shepherd learned to build.

Ten releases, most of them about Dooap Shepherd: it now builds and refines Actions on its own, tests tools while designing, and keeps more context between sessions.

Auto-build: describe it, let it iterate

Turn on auto-build and Dooap Shepherd loops build → dry-run → check on its own, refining the Action against real-shaped data until it works or hits the cap you set. You can stop it at any point. Everything it produces is a draft in your UAT tenant — nothing runs in production until you publish it.

Dooap Shepherd guide

Less re-briefing, earlier feedback

Shepherd keeps more context between sessions — conventions, feedback, and each Action’s own history — so a new conversation doesn’t start from zero. And a new tool-testing view lets it try a tool call while designing, so problems surface before a run, not during one.

Also this month: structured output for Agent Steps, a timeline view for Runs, read-only access roles, failure email notifications — and 30 more improvements and fixes across 10 releases.

May 2026· 5 releases

People joined the loop.

May’s releases centered on one idea: a person as part of a Run — starting it, approving inside it, and giving it the data it needs.

Human Tasks: start a Run, pause a Run

A Human Task can now trigger an Action — a submitted form starts the Run. Agents can also pause a task and resume it when new information arrives. Approvals, intake forms, and clarifications happen inside the Run, on the record, instead of around it in email.

Human Tasks guide
Human Tasks in the product: the task list, and a form a Run is waiting on.

Data Tables and Loop Over

Actions get typed tables to search, write, and read — reference data, lookups, working state — with no external system to wire up. The new Loop Over step runs a sub-route over rows or any JSON array, and new Excel tools read, write, and convert spreadsheets to CSV.

Data Tables guide
A Data Table: typed columns, rows an Action can read and write.

Also this month: evaluation datasets created straight from past runs, Azure Communication Services and expanded Azure Storage apps, a Dooap invoice helper for manual runs — and 25 more improvements and fixes across 5 releases.

See the newest capabilities live.

Book a demo and we’ll show this month’s features on your own processes.

Book a demoSee how it works