Skip to main content

How To Record a Loop

How to record a walkthrough with the Caddi Recorder.

Recording is how you show Loopy a process instead of describing it. You start a recording from a conversation in Loop Studio, work through your process as you normally would while narrating, and stop. Caddi turns what it saw into the first version of your loop.

Before you start

  • Install the Caddi Recorder. It is a Chrome extension, and recording works in Google Chrome only. See Installing Caddi Recorder Chrome Extension.

  • Recording starts in Caddi, not in the extension. If you open the extension on its own it shows a single Create Loop button, which opens a new Loop Studio session for you. Everything below starts from that session.

  • Connect a microphone. Caddi records your narration alongside your screen, and the recorder will not start without working audio.

1. Get to the recording card in Studio

  1. Open Studio from the left navigation.

  2. Choose Build a new loop (or Edit existing loop to change one you already have) and describe the process in plain English.

  3. When Loopy needs to watch you work, it posts a Record this walkthrough card in the chat. The card lists the numbered steps it wants to see and the app each step touches.

Read the card before you start. It is the script you are going to follow, and it is also what the recorder shows you while you record.

2. Start the recording

  1. Select Start Recording on the card.

  2. The Caddi Recorder opens. If you have not granted microphone access yet, select Grant Microphone Access and allow it on the page that opens, then choose your microphone from the list.

  3. Check the Audio Level meter. If the button reads No Microphone, Detecting Audio... or No Audio Detected rather than Start Recording, Caddi cannot hear you yet and the button stays disabled until it can.

  4. Select Continue. The recorder's side panel opens beside your work, showing the same numbered script from the card. Select Start Recording in the panel.

  5. Chrome asks what you want to share. You can pick a single browser tab, an application window, or an entire screen.

If the Chrome sharing dialog does not appear, the recorder shows a Select a Screen button. The dialog is usually hidden behind another window — select the button to bring it forward.

3. While you record

  • The side panel stays open next to your work with your script, a timer, and an Audio Input meter. Steps tick off as Caddi recognises them, so you can see what it has and has not picked up while you still have time to redo a step.

  • Narrate as you go. Saying why you do each step is what lets Loopy capture the logic rather than just the clicks.

  • Back in Studio, the card follows along: Preparing to record, then Recording in progress, then Review & save in the recorder.

  • To abandon a recording part-way, use Discard recording in the panel.

  • When you have finished the process, select Stop Recording.

4. After you stop

  • Stopping is what sends the recording. The recorder uploads straight to Caddi.

  • The upload runs in the background with a progress bar. You can close the recorder window; keep Chrome open until the upload finishes.

  • In Studio, the card moves to Analyzing recording while Caddi detects the steps, tools and branches in your walkthrough, then to Recording analyzed.

  • Loopy then asks about anything it saw that you had not mentioned, and carries on building from there. See Getting Started with Loop Studio for what happens next.

Best practices

  • Follow the script on the card. It was written from your conversation, and it is what Loopy is expecting to see.

  • Work inside Chrome wherever you can. Inside a Chrome tab, Caddi captures your actions and the page itself. For a window or a whole screen outside Chrome it falls back to periodically sampled screenshots, which carry far less detail. For Outlook, Slack and similar tools, use the web version rather than the desktop app.

  • Record the process from start to finish, including the clicks and form fills you would normally do on autopilot.

  • Explain what you are doing and why, as though you were training a new colleague. The reasons behind what you include, exclude, rename or route usually become the loop's rules.

  • Show Caddi where things live — the folder, the matter, the client record — so it can find them too.

  • Close unrelated applications and tabs before you begin.

  • Do not record logins. Caddi signs in through the connections on the Integrations page, so recording a login only adds steps.

  • Small mistakes are fine. Narrate the slip and pick up from the last correct step.

  • Move slowly and deliberately through each action.

  • Keep it under about 20 minutes. Shorter recordings are easier for Caddi to read accurately.

  • For PDFs: open the file in place in Box, OneDrive or Google Drive where you can. If you have to download it, right-click and choose Open with Google Chrome rather than a desktop app such as Adobe or Preview.

  • Record again for a materially different case. If the process takes a genuinely different path, show that path in its own recording rather than describing it.

If something goes wrong

  • "Your Caddi recorder is out of date — update it to record." Update the extension from the Chrome Web Store, then select Try again on the card.

  • "You need the Caddi recorder (Chrome only) to record this walkthrough." The extension is not installed in this browser, or you are not in Chrome.

  • "Something went wrong starting the recording — try again." A network or service problem, not an extension problem. Select Try again.

  • The upload failed. Your recording is kept on your device, not lost. The recorder retries automatically for a few minutes and then shows a banner so you can retry it yourself. Unsent recordings accumulate up to a limit; past that, starting a new recording asks you to Discard & start and drops the oldest one, so clear the backlog first if you still want it.

  • You cannot finish the recording at all. Tell Loopy in the Studio chat, or ask it to connect you with the Caddi team.

Related

Did this answer your question?