TestingOps.ai

Design tools · Native connection

Miro and TestingOps: test scenarios from your boards

Journey maps, story maps and workshop boards in Miro record how a feature should behave. TestingOps reads them frame by frame so its AI test agents can plan scenarios from them.

  • Native connection
  • Available
Request a demo Miro REST API quickstart
Connection
Native connection
Writes back
Nothing, it only reads
Last checked
7 Nov 2026

In short

Miro and TestingOps in short

The Miro connection reads boards through Miro's REST API with the access token of a Miro app that has the boards:read scope.

Each frame becomes a knowledge-base document with its sticky notes, texts, shapes and cards in reading order, and connectors become flows such as "Cart" → "Checkout", with their captions.

Agents use the frames as context when they plan scenarios and write test cases; the board is only read, and no runnable tests are produced from it.

The Miro app must be installed in the team that owns the board.

What it does

What it does for your testing

  1. 1

    Frames become documents

    Input
    Frames on a board, such as the stages of a journey map
    TestingOps
    Lists each frame's sticky notes, texts, shapes, cards, document and image titles and embed links from top to bottom
    Output
    One knowledge-base document per frame, with a link back to it on the board
  2. 2

    Connectors become flows

    Input
    Connectors between notes or shapes, with their captions
    TestingOps
    Records each as "A" → "B" with the caption, under the frame where it starts
    Output
    Paths and conditions, for example a caption "payment declined", that scenarios can follow
  3. 3

    Loose items stay findable

    Input
    Notes and shapes outside any frame
    TestingOps
    Gathers them into one "Board (outside frames)" document
    Output
    Parking-lot notes and open questions that agents can still search

Step by step

How it works

  1. Create a Miro app tokenIn Miro, create an app with the boards:read scope, install it in the team that owns your boards and copy its access token.
  2. Save the connectionPaste the token under Integrations → Project tools → Design tools → Miro. TestingOps sends it as a Bearer token on each call to Miro.
  3. Link boards to a projectIn the project's Knowledge Base, add a Design tools source: select boards from the list (up to 500, most recently modified first) or paste board links.
  4. Changed boards are re-readTestingOps compares the board's last modification time with the previous sync and reads items and connectors only when the board changed.
  5. Agents plan from the framesAgents search the frame documents when they plan scenarios and write test cases. The documents of frames that were removed are retired.

Board content is often informal. TestingOps keeps it as written; deciding which notes describe agreed behaviour stays with the people who review the cases.

Connect

Setup

  1. In Miro, create an app with the boards:read scope, install it in the team that owns the boards and copy the access token.
  2. In TestingOps, open Integrations → Project tools → Design tools → Miro and save the token.
  3. Open Knowledge Base, pick the project, select Add source on Design tools, choose the Miro connection, select boards or paste board links, then select Link to RAG.
  4. Select Sync now. Later syncs run automatically and skip boards that have not changed.

Documentation: Miro REST API quickstart

Where you connect it in TestingOps: Integrations → Project tools → Design tools → Miro

Use cases

Use cases

Turn a journey-mapping workshop into scenarios

Trigger
A refinement workshop ends with a board of journey frames
Uses
Frames, sticky notes and connector captions
Agent activity
Plans a scenario for each path the connectors draw and uses the captions as conditions
Result
Draft scenarios and test cases for review
Condition
Notes are workshop material; reviewers confirm which ones describe agreed behaviour

Turn open questions into negative cases

Trigger
Stickies such as "what if the voucher has expired?" sit next to a flow
Uses
The notes inside the frame and outside frames
Agent activity
Proposes negative and boundary cases for the situations the notes raise
Result
Edge cases that would otherwise depend on someone remembering the workshop
Condition
A note is a question, not a requirement; the expected result needs confirming with the team

Follow a story map that changes during the sprint

Trigger
The team keeps editing the board while stories move
Uses
Frames re-read after each change; unchanged frames keep their documents
Agent activity
Works from the current frames when it writes or reviews cases
Result
The knowledge base follows the board, and removed frames drop out
Condition
Existing cases are not changed automatically

Capabilities

Capabilities and limits

What is read

  • Board frames: sticky notes, texts, shapes, cards and app cards (title, description, field values), document and image titles, embed links
  • Connectors between items, with their captions
  • Items outside any frame
  • Your boards, for the picker: up to 500, most recently modified first

What is produced

  • One knowledge-base document per frame that has text or connectors, with a link to the frame
  • One document for the items outside frames

Where it can write

Nothing on your boards.

How it connects

Miro REST API with the access token of your Miro app, sent as a Bearer token

Account and permissions

  • A Miro app with the boards:read scope, installed in the team that owns the boards
  • On testingops.ai, use the app's access token: the Connect with Miro sign-in is not offered there

Limits

  • Up to 5,000 items and 5,000 connectors per board, and 200 frame documents per sync
  • Images are read by their title only; text inside an image is not read
  • Frames without text or connectors are skipped
  • Each Miro connection counts toward your package's integration limit
  • No runnable tests or visual checks are generated from boards

Example

Example: how a team uses it

Illustrative scenario, not a customer story.

A team maps its returns process on a Miro board: one frame per stage, stickies for each step and connectors captioned "within 30 days" and "after 30 days".

After the board is linked, an agent drafts a scenario for each captioned branch and a negative case for the sticky that asks about gift returns. The team confirms that case's expected result before it is approved.

Frequently asked questions

Which Miro token does TestingOps need?

The access token of a Miro app with the boards:read scope, installed in the team that owns the boards. On testingops.ai there is no Connect with Miro sign-in, so the app's token is the way to connect.

Why does Miro answer 403 Forbidden for a board?

The app is not installed in the team that owns that board, or it lacks the boards:read scope. Install it in that team and sync again.

Are connectors and arrows read?

Yes. Each connector becomes a flow line such as "Cart" → "Checkout", with its caption, under the frame where the connector starts.

What happens to notes outside frames?

They are collected into one document named "Board (outside frames)", so they remain searchable for agents.

Does TestingOps change my board?

No. It only reads items and connectors; nothing is written back to Miro.

Is the whole board read on every sync?

No. TestingOps first compares the board's last modification time, and when it is unchanged the items are not read again. When the board changed, frames whose content stayed the same keep their existing documents.

Next step

Bring a journey map or story map from your last workshop to a demo and see the scenarios agents plan from it.

Request a demoMore design tools integrations