Skip to main content

June 2026: Your loops just got a lot more reach

This month is all about loops doing more inside the tools you already use — plus a big batch of fixes for things you told us about.

This month is all about loops doing more inside the tools you already use — plus a big batch of fixes for things you told us about.

🚀 Loops can now act across far more of your tools

Until now, a loop could often read from a tool but stop short of doing the thing you actually wanted. We spent June closing those gaps across nearly every integration we support. Loops can now create, update, move, and manage the things they previously could only look at — across Clio, iManage, NetDocuments, QuickBooks, LawPay, Salesforce, HubSpot, Google Workspace, Microsoft 365, Slack, Asana, Box, GitHub, and more.

The practical version: if you ever hit a wall where a loop almost did what you needed in one of your tools, there's a good chance it can now go the rest of the way. For example, a billing loop in LawPay can create and apply a payment end to end — not just look one up, and a loop in Box can now upload a file into a folder, not just read what's already there.

✨ New features

  • Schedule a loop just by describing it — type the schedule you want in plain English — "the third day of each month at 1pm and 5pm" — and Caddi turns it into a recurring schedule, with a preview of the next three runs before you save. Any cadence you can put into words now works, from twice an hour to specific days and times each month, as long as runs are at least 30 minutes apart. No more bending what you need to fit a fixed set of options.

🔌 New integrations

  • RelativityOne — now connect RelativityOne so loops can work with your eDiscovery data.

  • Toggl — connect Toggl Track and Toggl Focus to bring time data into your loops.

🔧 Improved

  • iManage — loops now walk subfolder trees and scope searches to a specific workspace, so steps on big workspaces need a lot less manual setup.

  • Clearer run summaries — the summary you see after a loop runs is now built from exactly what happened during that run, so it reflects reality more closely.

  • Smoother on big runs — very large batch runs now stay readable (long lists collapse on their own), and a loop's live progress keeps updating even if your connection briefly drops.

🐛 Fixed

We squashed a batch of bugs this month, including files failing to upload to Box, copied loops losing their saved documentation, and loop input dates drifting to a different time zone than the one shown on screen, a run occasionally showing as "Success" when a step had actually failed, and screen recordings sometimes capturing the wrong length. The inputs screen also now warns you before you navigate away with unsaved changes.

Did this answer your question?