Loop Studio is where you build, edit, test, and troubleshoot Caddi automations with Loopy.

On July 31, 2026, building and editing will move fully to Loop Studio, and existing loops will be migrated automatically. Learn more in Loop Studio: what's changing and why.

Caddi automates the repetitive work your team does across the tools you already use — filing documents, triaging email, syncing records between systems, generating reports, and more.

Three words you'll see everywhere:

You don't need any technical skills. You describe (or show) how you work today, and Loopy turns it into a reliable automation.

Open Studio from the left navigation. From the home screen, you can:

To create something new, select Build a new loop or start typing in the message box.
​

Explain the outcome in plain English. You do not need to document the entire process up front. Start with the result you want.

For example:

​I want to build a loop that lists all my meetings for today.

When possible, include:

Attach sample documents, emails, spreadsheets, screenshots, or expected outputs to give Loopy more context.

Focus on the business outcome rather than every click. Loopy will ask for any details it still needs.

Loopy asks targeted questions to understand how the process works, including which systems to use, where results go, how records are selected, and what should happen in different scenarios.

This conversation is also where Loopy gathers everything the loop needs to run — like a date range, a Slack channel, or a folder. There's no separate setup form to fill out: Loopy collects the loop's inputs as part of the chat and confirms them with you before testing.

Loopy also checks whether the required tools are connected. If an integration is missing, connect it from the Integrations page before continuing.

Once Loopy has enough information, it checks whether the process you described (or showed) can be built end to end — the steps, the tools required, and your connected integrations.

Loopy then summarizes how it plans to build the loop. Before approving, confirm that the tools, actions, rules, and expected results are correct. If something is missing or incorrect, describe the change in the chat. When the plan looks right, select Approve.

​
​

If Loopy needs to see part of the process, Loop Studio creates a recording checklist based on your conversation. Recording is the recommended approach because it gives Loopy the most complete context for an accurate first build.

The checklist tells you exactly what to demonstrate and may include:

Select Start Recording and follow the checklist. As you work, explain both what you are doing and why. Narrating your decisions helps Loopy understand the logic behind the process, not just the clicks.
​

After processing the recording, Loopy may identify steps or decisions that were not included in your original request.

For example, you may have asked Caddi to list your meetings but also demonstrated posting them to Slack. Loopy will ask whether that action should be included in the loop.

Answer directly. Loop Studio will recheck feasibility as the scope changes and may ask you to connect another tool. This is also how Loopy identifies different scenarios, so you do not need to map every variation before you begin.

Once Caddi has what it needs, Loop Studio builds the first test version. The diagram shows the major steps, the tools Caddi will use, and the actions it will take.

Review the diagram at the business-process level — confirm it reflects the process and outcome you described. Some steps may look unfamiliar because they represent operations the underlying tool requires (like refreshing data or looking up an ID). Select any step for a plain-English explanation.

See the Loop Studio FAQ for more information.

Testing is how you make sure the loop does exactly what you expect — before it ever runs on its own.

Important: a test runs the real automation. It executes real steps and can create real messages, records, documents, or files. What makes it a test is that Caddi pauses for your careful review instead of running unattended. Use appropriate test data.

When you select Run New Test, you can choose how to move through the loop:

As the test runs, the diagram highlights the active step, and the loop chat reports the outcome of each step.
​
​

Results appear right in the loop chat. For each step, Loopy explains what it expected and what actually happened, so mismatches are easy to spot without interpreting logs.

Then verify the real-world result: open the connected systems the loop touched and check the actual email, document, record, or message it created. A completed test doesn't always mean the business result is correct — confirm Caddi selected the right information, applied the right rules, produced the expected output, and put it in the right place.

If something needs to change, describe it in the chat — for example: The company name should come from HubSpot, not the calendar title. Include what you expected, what happened instead, and what the corrected result should look like. Loopy updates the test version and you can run it again.

When a test produces the correct result, Loop Studio offers to promote that tested version. Select Make it Live to make it your active loop.

This is Caddi's version safety net: every build or edit creates a test version, and nothing you do in Studio affects your live loop until you make a tested version live. If a test result is wrong, don't select Make it Live — tell Loopy what to change and test again. Your current live version keeps running unchanged the whole time.

Before going live, confirm that:

Ask Loopy to run the loop automatically: This loop should run every day at 8 AM. Loopy asks for any missing details (like timezone), summarizes the proposed schedule, and you select Approve. You can change the schedule any time from the chat.

Loop Studio is also where you maintain and troubleshoot your automations.

From a loop's page, select Edit Loop — it opens the loop in Loop Studio. You can also open Studio from the left navigation and select Edit existing loop.

Describe the change in plain English: add or remove a step, change a rule or filter, use a different source of truth, update an output format, add a scenario, or change where results go. Attach a revised template, screenshot, or sample output to show what should change.

Edits create a test version — your active version continues running unchanged until you test the update and select Make it Live.

Loops built before Loop Studio become editable once migrated (automatic, completes by July 31, 2026). If Loopy says it cannot edit a loop yet, it has not been migrated; Caddi will notify you when it is ready. See Loop Studio: what's changing and why.

Open the Run History tab on a loop to review previous runs, or select Ask about a run in Loop Studio for a plain-English explanation. You can ask things like: Why was this document skipped? Which record did Caddi use? Why was no email created?

A successful run may have found nothing to process, so review both the run summary and the result in the destination system. Run history is visible only to the person who ran each run.

Select Fix an error when a run fails or produces an unexpected result. Include what you expected, what happened instead, which run you mean, and any error message. Attach the incorrect output or a screenshot when it helps. Loopy will inspect the run, identify the likely cause, and try to resolve it.

If Loopy cannot resolve the issue, ask to be connected with the Caddi team: "Connect me with the Caddi team," "I need help from a person," or "Please escalate this."

Start with the result. Explain what should be true when the loop finishes before describing every action.

Share examples and files. Attach a sample email, document, spreadsheet, screenshot, or expected output whenever it adds context.

Show, don't just tell. Record the process or share your screen — it gives Loopy the most complete view of steps, decisions, and exceptions.

Name the source of truth. Tell Loopy which system to trust when the same information appears in multiple places.

Explain your decisions while recording. Why you include, exclude, rename, or route something often becomes the loop's rules.

Show materially different scenarios. Record another example when the process takes a meaningfully different path.

Test on a small batch first. Use batch selection to run your first test on one or two safe items before testing the full process.

Check the final destination. Always verify the actual output the test created in the connected system. Do not rely on the completion status alone.

Start with Loopy in Loop Studio for questions, edits, and troubleshooting. If you need help from a person, ask Loopy to connect you with the Caddi team or use the Intercom support icon. Starting July 31, Loopy will only be available in Loop Studio; the support icon connects you directly with the Caddi support team.

Ask for help when an integration or permission blocks you, you cannot complete a recording, the same fix keeps failing, a test reports success but the result is missing, a migrated version needs rollback, or Loopy flags the workflow for review. Include the loop name, the relevant run, what you expected, and what happened.