# Tell Bob what you want automated. Have a working flow in minutes.

> Say the task in your own words. Bob asks a quick question, opens the app, and does each step while Stepwork records it. Then you run a test in your real apps before anything goes live.

Source: https://stepwork.com/chat

## Pick a task. Watch Bob, or take over.

Fifteen tasks across IT, security, MSPs, and finance. Autoplay works through them one after another. Pick a task to take over: send the request, answer Bob, and run the test yourself.

A shortened demo with pre-written replies. Every flow here is one we filmed running in StepDemo, our sandbox copies of these apps, and the run time shown is that run's. In Stepwork, Bob answers your own task in your own apps.

## Call Bob from Claude Code, Codex, or Cursor

Connect Stepwork MCP once, then ask Bob from the AI tool you already have open. One sentence, and Bob records a flow, answers from your apps, or links a whole procedure in Stepwork. The flows still run the way they were recorded, every time.

Lock out a leaver:
- You: Lock a leaver out of Okta
- stepwork.ask("Lock a leaver out of Okta")
- Bob: I can do that in Okta. One quick question so I record the right steps.
- Bob: What should happen to the account? 1. Deactivate it (recommended); 2. Suspend it; 3. Sign them out of every session
- You: Deactivate it
- stepwork.ask("Deactivate it")
- Bob: I recorded all 3 steps in Okta and saved “Deactivate a leaver in Okta”. Run a test when you're ready; it uses your real apps.
- Saved “Deactivate a leaver in Okta” · Runs on its own in 27 s

Find idle Figma seats:
- You: Which Figma seats has nobody used in 90 days?
- stepwork.ask("Which Figma seats has nobody used in 90 days?")
- Bob: 4 seats. Felix Tanaka (172 days), Emeka Castellanos (167), Jonah Sorensen (161), and Elena O'Brien (106). 10 of your 25 Full seats have sat idle 30 days or more.
- From “Read Figma's full seats and when each was last active” in Figma

Automate IT offboarding:
- You: I want to automate IT. Start with offboarding: every leaver, in every app.
- stepwork.ask("I want to automate IT. Start with offboarding: every leaver, in every app.")
- Bob: I can build that from flows your team has already recorded. A few questions first, so I get the apps and the rules right.
- Bob: Where do leavers show up first? You: In Rippling, when HR marks them terminated
- Bob: Should I close out contractors too? You: Yes, everyone who leaves
- Bob: When should I close someone out? You: Once their last day has passed
- Bob: Your leavers can sign in to these 4 apps. Which should I close out? You: Okta, Microsoft Entra ID, Jamf Pro, Zoom
- Bob: Okta signs them in to everything else. Should I deactivate it first? You: Yes, Okta first
- Bob: How should IT hear about each run? You: A reply in the IT Teams thread
- Bob: When should it run? You: Weekdays at 6 PM
- Bob: That's everything I need. Should I link it up and test it once? You: Build it and test it
- Bob: Linked: 6 flows across 6 apps. Schedule: Weekdays at 6 PM. Testing it once now.
- Test passed. From here it runs on its own: the same steps, in the same order, every time.

Check client billing:
- You: Are we billing every client for the seats they bought?
- stepwork.ask("Are we billing every client for the seats they bought?")
- Bob: 2 seats unbilled. Fourth Coffee bought 22 Business Premium seats in Pax8 but is billed for 20 in ConnectWise. Alpine Ski House and Coho Winery match.
- From “Read the seats each client bought in Pax8” in Pax8 and “Read every active agreement in ConnectWise” in ConnectWise PSA

A scripted demo. Every flow, figure, and run time comes from a flow we filmed in StepDemo, our sandbox copies of these apps. From your own tool, Bob works in your apps.

## Let Bob do the clicking

One switch decides who does each step. On, Bob clicks and types in the app himself. Off, he rings the spot and you do it. Stepwork records the step the same way either way.

- **Auto-apply on (Recommended):** His pointer moves to the field and types the value, then goes on to the next step by itself. You watch the flow get recorded, and can stop him at any point.
- **Auto-apply off:** Bob rings the spot for the step and waits. You click it and type, and Stepwork records your step exactly as it would his.
- **The same recording either way:** Whoever does the step, Stepwork records it the same way, ready to test and run.
- **Switch mid-flow:** Take over for a step you'd rather do yourself, then switch Bob back on to finish the rest.
- **Nothing runs until you test it:** Bob only records. The saved flow runs when you start a test in your real apps.

## Say the goal. Bob links the apps.

You don't need to know the steps. Tell Bob what you want, like automating IT, hitting a KPI, or a report every morning. He asks one thing at a time: which apps, what the rule is, who hears about it, and when it runs. Then he links flows your team recorded once, tests the procedure, and it runs the same way every time.

Automate IT offboarding: “I want to automate IT. Start with offboarding: every leaver, in every app.”:
- I can build that from flows your team has already recorded. A few questions first, so I get the apps and the rules right.
- Where do leavers show up first? In Rippling, when HR marks them terminated
- Should I close out contractors too? Yes, everyone who leaves
- When should I close someone out? Once their last day has passed
- Your leavers can sign in to these 4 apps. Which should I close out? Okta, Microsoft Entra ID, Jamf Pro, Zoom
- Okta signs them in to everything else. Should I deactivate it first? Yes, Okta first
- How should IT hear about each run? A reply in the IT Teams thread
- When should it run? Weekdays at 6 PM
- Find the leavers: Read terminated employees in Rippling (Rippling)
- Check each one: Who to close out (Employees and contractors; Last day has passed)
- Close their access: Deactivate a leaver in Okta (Okta); Revoke a leaver's sessions in Entra ID (Microsoft Entra ID); Lock a leaver's Mac in Jamf Pro (Jamf); Look up a leaver in Zoom (Zoom)
- Tell the team: Reply in the Teams thread (Microsoft Teams)
- Runs Weekdays at 6 PM. Filmed run time: 3 min 4 s.
- First run: 9 leavers in Rippling to close out.
- Recorded once. Every run plays the same steps in the same order.

Hit a SaaS spend target: “I want to hit a KPI: idle software seats under 10% by the end of the quarter.”:
- Good target. I need to know which apps to count and when a seat counts as idle. Then I'll link the flows that read and reclaim seats.
- These 4 apps have paid seats. Which should I count? Figma, ChatGPT, Cursor, Microsoft 365
- When does a seat count as idle? No activity in 30 days
- You pay for 10 Microsoft 365 licenses no one has. Count those as idle too? Yes, count them
- What should I do with an idle Figma seat? Move it to a free Viewer seat
- Where should I post the numbers? The IT Teams thread
- How often should I check? Mondays at 8 AM
- Read seat activity: Read Figma's full seats and when each was last active (Figma); Read every ChatGPT seat and when it was last active (ChatGPT); Read last month's Cursor usage (Cursor); Count free licenses in Microsoft 365 (Microsoft 365)
- Find idle seats: Idle seat (No activity in 30 days; Unassigned licenses count)
- Reclaim them: Downgrade an idle Figma seat to Viewer (Figma)
- Report the KPI: Reply in the Teams thread (Microsoft Teams)
- Runs Mondays at 8 AM. Filmed run time: 2 min.
- First run: 10 of 25 Figma seats idle 30 days or more, and 10 Microsoft 365 licenses paid for but unassigned.
- Recorded once. Every run plays the same steps in the same order.

Pull an access report every day: “I want to pull an access report every day and send it to the team.”:
- I can do that. I'll check who should have access against who does. First, which apps to compare and what counts as a problem.
- Which system says who works here? Rippling
- Which apps should I check against Rippling? Okta, GitHub, Microsoft Entra ID
- What should count as a problem? Access for someone not in Rippling, GitHub two-factor off, GitHub Owners to review
- Where should the report go? The IT Teams thread
- When should it run? Weekdays at 7 AM
- Who works here: Read active employees in Rippling (Rippling)
- Who has access: Read Okta's users and their last sign-in (Okta); Read every GitHub member and their role (GitHub); Find a role's groups in Entra ID (Microsoft Entra ID)
- Flag problems: Access problem (Not an active employee; Two-factor off; GitHub Owner)
- Send the report: Reply in the Teams thread (Microsoft Teams)
- Runs Weekdays at 7 AM. Filmed run time: 2 min 7 s.
- First run: 1 GitHub member with two-factor off, and 1 Owner to review.
- Recorded once. Every run plays the same steps in the same order.

Monthly client reports for an MSP: “Every month, build each client's health report and check we billed them right.”:
- I can build that for all your clients at once. Let me confirm where health and billing live, then what to flag.
- Where does each client's health live? I found these 3. NinjaOne, SentinelOne, KnowBe4
- What should each health report flag? Devices offline, Unhealthy agents, Training under 60%
- Should I check what each client bought against what you bill them? Yes, Pax8 against ConnectWise
- Where should each client's report go? A note on their ConnectWise ticket
- When should it run? The first Monday of the month
- Read health and billing: Read devices under management by client in NinjaOne (NinjaOne); Read agent health across every SentinelOne site (SentinelOne); Read training completion by client in KnowBe4 (KnowBe4); Read the seats each client bought in Pax8 (Pax8); Read every active agreement in ConnectWise (ConnectWise PSA)
- Check each client: Client check (Devices offline; Agent unhealthy; Training under 60%; Bought differs from billed)
- Log it for the client: Note a ticket and log the time in ConnectWise (ConnectWise PSA)
- Runs First Monday of the month. Filmed run time: 2 min 4 s.
- First run: Fourth Coffee bought 22 Business Premium seats in Pax8 but is billed for 20 in ConnectWise.
- Recorded once. Every run plays the same steps in the same order.

Every card is a flow we filmed in StepDemo, with that film's run time, and Bob's counts come from what those flows pulled. The goals and replies are written for this page.

## Ask Bob what's going on in your apps

Bob is on the Stepwork home screen, so you can ask him anything about your apps, not just to build a flow. He answers from what your flows pull, and any answer can become a flow that runs every day.

- **Which Figma seats has nobody used in 90 days?:** 4 seats. Felix Tanaka (172 days), Emeka Castellanos (167), Jonah Sorensen (161), and Elena O'Brien (106). 10 of your 25 Full seats have sat idle 30 days or more. (From: Read Figma's full seats and when each was last active)
- **How many Microsoft 365 licenses are we paying for but not using?:** 10 licenses. Most are Teams Phone Standard (4) and Business Premium (3). The rest are Power BI Pro (2) and Project Plan 3 (1). (From: Count free licenses in Microsoft 365)
- **Who in GitHub has two-factor turned off?:** 1 member. Hiro Castellanos has two-factor disabled. Alex Morgan is your only Owner. (From: Read every GitHub member and their role)
- **Are we billing every client for the seats they bought?:** 2 seats unbilled. Fourth Coffee bought 22 Business Premium seats in Pax8 but is billed for 20 in ConnectWise. Alpine Ski House and Coho Winery match. (From: Read the seats each client bought in Pax8; Read every active agreement in ConnectWise)
- **Which endpoints need attention?:** 7 unhealthy. 7 of 50 SentinelOne endpoints are unhealthy: 4 at Alpine Ski House and 3 at Fourth Coffee. 5 agents are out of date. (From: Read agent health across every SentinelOne site)
- **Which Macs haven't checked in for a month?:** 2 Macs. James Kim's (47 days) and Sam Lee's (39 days). Every other Mac checked in within the last 2 days. (From: Read every managed Mac in Jamf Pro)
- **How much is overdue, and what's the oldest?:** $353,595.00. Across 15 overdue invoices. The oldest is INV-1013 for Olympia Logistics, due Jul 1. (From: Read overdue invoices for collections)
- **Does Zoom make everyone sign in with SSO?:** No. Okta SSO is set up as a way to sign in, but Require SSO is off, and only admins have to use two-factor. (From: Capture Zoom's sign-in settings)

Each answer comes from the rows a filmed flow pulled from StepDemo, our sandbox copies of these apps.

## From one sentence to a tested flow

Bob asks what he needs, opens the app, and does each step for you while Stepwork records it. You see every step before it's saved.

- **Describe it:** Type the task the way you'd explain it to a coworker, or press the mic and talk it out. Name the apps if you know them. If you don't, say what's slowing you down.
- **Answer a few questions:** Bob asks one question at a time and recommends an answer, with the reason in a line. Click to answer. The meter shows how sure he is, and he stops asking once he knows what to build.
- **Watch Bob do each step:** Bob opens the app and marks each step with a ring around what to click. With “Bob applies steps” on, he clicks and types each one for you. Switch it off to click through them yourself. Stepwork records each step either way.
- **Run it:** You record a flow once. Bob saves it, you test it in your real apps, and from then on every run plays the same steps in the same order, whether it's on a schedule or your team runs it.

## Every flow here, filmed in a real app

Each of these is a flow we recorded and ran in StepDemo. Ask Bob for any of them, or for your own version in your apps.

IT:
- Create a new hire's account in Entra ID with their groups (Microsoft Entra ID, Execution, runs in 28 s)
- Read upcoming new hires in Rippling (Rippling, Extraction, runs in 18 s)
- Add a user to a group in Entra ID (Microsoft Entra ID, Execution, runs in 27 s)
- Assign a license in Microsoft 365 (Microsoft 365, Execution, runs in 26 s)
- Add mailbox delegate (Microsoft 365, Execution, runs in 26 s)
- Find the mailbox in Microsoft 365 (Microsoft 365, Extraction, runs in 25 s)
- Count free licenses in Microsoft 365 (Microsoft 365, Extraction, runs in 18 s)
- Find a role's groups in Entra ID (Microsoft Entra ID, Extraction, runs in 24 s)
- Look up a user in Entra ID (Microsoft Entra ID, Extraction, runs in 26 s)
- Reset a user's password in Entra ID (Microsoft Entra ID, Execution, runs in 55 s)
- Make a user register MFA again in Entra ID (Microsoft Entra ID, Execution, runs in 29 s)
- Close a license ticket with a note (Freshservice, Execution, runs in 56 s)
- Create ticket (StepDemo, Execution, runs in 62 s)
- Reply in the Teams thread (Microsoft Teams, Execution, runs in 26 s)
- Read Figma's full seats and when each was last active (Figma, Extraction, runs in 18 s)
- Downgrade an idle Figma seat to Viewer (Figma, Execution, runs in 22 s)
- Read every ChatGPT seat and when it was last active (ChatGPT, Extraction, runs in 18 s)
- Read last month's Cursor usage (Cursor, Extraction, runs in 18 s)
- Revoke a leaver's sessions in Entra ID (Microsoft Entra ID, Execution, runs in 56 s)
- Lock a leaver's Mac in Jamf Pro (Jamf, Execution, runs in 29 s)

Security:
- Read terminated employees in Rippling (Rippling, Extraction, runs in 22 s)
- Read active employees in Rippling (Rippling, Extraction, runs in 21 s)
- Deactivate a leaver in Okta (Okta, Execution, runs in 27 s)
- Read Okta's users and their last sign-in (Okta, Extraction, runs in 21 s)
- Read every GitHub member and their role (GitHub, Extraction, runs in 35 s)
- Look up a leaver in Zoom (Zoom, Extraction, runs in 24 s)
- Look up a user in Okta (Okta, Extraction, runs in 21 s)
- Suspend a user in Okta (Okta, Execution, runs in 27 s)
- Sign a user out of every Okta session (Okta, Execution, runs in 44 s)
- Reset a user's authenticators in Okta (Okta, Execution, runs in 26 s)
- Read agent health across every SentinelOne site (SentinelOne, Extraction, runs in 19 s)
- Read every managed Mac in Jamf Pro (Jamf, Extraction, runs in 20 s)
- Read the controls that need evidence in Vanta (Vanta, Extraction, runs in 19 s)
- Capture Zoom's sign-in settings (Zoom, Extraction, runs in 23 s)

MSPs:
- Read the seats each client bought in Pax8 (Pax8, Extraction, runs in 21 s)
- Read every active agreement in ConnectWise (ConnectWise PSA, Extraction, runs in 22 s)
- Note a ticket and log the time in ConnectWise (ConnectWise PSA, Execution, runs in 26 s)
- Count free licenses in a client's Microsoft 365 tenant (Microsoft 365, Extraction, runs in 20 s)
- Look up a client's new user standard in IT Glue (IT Glue, Extraction, runs in 23 s)
- Read devices under management by client in NinjaOne (NinjaOne, Extraction, runs in 18 s)
- Read training completion by client in KnowBe4 (KnowBe4, Extraction, runs in 18 s)

Finance and ops:
- Read overdue invoices for collections (StepDemo Billing, Extraction, runs in 23 s)
- Read closed deals for a product (Southridge CRM, Extraction, runs in 23 s)
- Pull a supplier's open POs due this month (Lucerne Business Suite, Extraction, runs in 26 s)
- Acknowledge a customer PO with promise dates (Fabrikam Supplier Network, Execution, runs in 134 s)
- Check a SKU's stock (Olympia WMS, Extraction, runs in 22 s)
- Export a client's shipped orders (Olympia WMS, Extraction, runs in 31 s)
- Receive a shipment on the RF screen (Olympia WMS, Execution, runs in 33 s)
- Get an LTL rate quote (CM Freight Online, Extraction, runs in 31 s)

Industries:
- Pull tomorrow's appointments (Lamna Practice Manager, Extraction, runs in 71 s)
- Attach a faxed referral to the chart (Lamna Practice Manager, Execution, runs in 25 s)
- Check a patient's coverage (HI Provider Connect, Extraction, runs in 27 s)
- Add a store manager's login in PDI (PDI Enterprise, Execution, runs in 28 s)
- Close a new hire ticket with the details (Freshservice, Execution, runs in 58 s)
- Create a store employee's account in Entra ID (Microsoft Entra ID, Execution, runs in 26 s)
- Create a cashier's POS ID in Verifone Commander (Verifone Commander, Execution, runs in 26 s)
- Remove a leaver's POS ID in Verifone Commander (Verifone Commander, Execution, runs in 55 s)

## Quick to build, careful to run

Chatting makes setup fast. The guardrails that keep your systems safe stay on.

- **Passwords stay out of chat:** Bob never asks for credentials. If you paste one, he leaves it out of the chat and points you to save the login in 1Password, where your flows can sign in with it.
- **Tested before it goes live:** Every flow gets a test run in your real apps first. If a step fails, Bob shows where and why, and you can ask him how to fix it.
- **Runs the same way every time:** Bob helps you build the flow. Once it's built, Stepwork does the task exactly the way it was recorded, every run, instead of choosing its own steps.

## Questions about Ask Bob

**Q:** What is Ask Bob?

Bob is the assistant on the Stepwork home screen. Tell him what you want to automate, and he asks a quick question or two, opens the app, and records the flow with you step by step.

**Q:** Do I need to know how to build automations?

No. Describe the task in your own words, or say what's slowing you down. Bob asks the questions he needs and recommends an answer for each one.

**Q:** What kinds of questions does Bob ask?

One at a time, usually with three choices and a recommended pick, about the apps, the steps, and the data involved. He stops once he's sure what to build. He doesn't ask how often the task runs; you set a schedule separately.

**Q:** What does “Bob applies steps” do?

It's auto-apply. While it's on, Bob clicks and types each step in the app himself, and Stepwork records it as he goes. It's on by default because it's the fastest way to build a flow.

**Q:** Can I do the steps myself?

Yes. Switch off “Bob applies steps” and click through each step yourself, with Bob pointing to what's next. Stepwork records it the same way.

**Q:** Can I start with a big goal instead of one task?

Yes. Say something like “automate IT offboarding” or “pull an access report every morning.” Bob asks a few questions, then links flows across your apps into one procedure that you can put on a schedule.

**Q:** Can I ask Bob questions about my apps?

Yes. Ask things like which seats sit idle or which devices haven't checked in. Bob answers from what your flows pull, and any answer can become a flow that runs every day.

**Q:** Can I ask Bob from Claude Code, Codex, or Cursor?

Yes. Connect Stepwork MCP once, and you can ask Bob from the AI tool you already use. He asks the same questions, records the flow in Stepwork, and you test it before it runs. Stepwork still runs every flow the way it was recorded.

**Q:** Does Bob need my passwords?

No. Bob never asks for credentials, and if you paste one, he leaves it out of the chat. Save logins in 1Password, and your flows can sign in with them.

**Q:** Does AI run my flows?

Bob uses AI to help you build the flow. Once it's built, Stepwork does the task exactly the way it was recorded, every run, instead of choosing its own steps.

## See Bob build one of your flows

Bring a task your team repeats. We'll show you how Bob turns it into a tested flow.

---

This is the Markdown version of https://stepwork.com/chat, built from the same copy as the page. Everything about Stepwork for AI tools: https://stepwork.com/llms.txt. Book a demo: https://calendly.com/shaun-maclellan/1-1-w-shaun-stepwork
