Mural
ProductivityPut agent output onto Mural whiteboards: navigate the workspace, room, and mural hierarchy, create new murals, read a board's widgets, and post sticky notes so AI brainstorms land on a shared canvas.
What This Integration Enables
Whiteboards are where teams think together, and the expensive part of that thinking is everything around it: assembling the inputs beforehand and transcribing the outputs afterward. FlowRunner agents take both ends. They navigate Mural's workspace, room, and mural hierarchy, create boards for projects, sprints, and workshops, post sticky notes at explicit canvas coordinates so content arrives organized rather than piled, and read a board's widgets back out so what the team decided actually leaves the room. - Create a fresh mural in the right room at the start of every project, sprint, or workshop - Have an AI agent brainstorm and post each idea as a placed sticky note for the team to react to - Sync open action items from [Notion](/integrations/notion) onto a triage board, one note each - Export a completed brainstorm's widgets into [Google Sheets](/integrations/google-sheets) for follow-through - Share new boards to [Slack](/integrations/slack) with an invitation to contribute before the session The coordinate system is the quiet differentiator. Because Create Sticky Note places each note at explicit x and y positions, an agent can build structure, columns for Went Well and Needs Work, clusters by theme, instead of dumping text into a corner for a human to arrange. And because Get Mural returns the canvas dimensions, the layout math adapts to the board rather than assuming one size.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The retro that starts at minute zero
The sprint ends Friday. The agent creates the retro board with Create Mural, pulls the sprint's shipped items and incident list, and lays them down with Create Sticky Note in three labeled columns. [Slack](/integrations/slack) shares the link Friday afternoon so the team adds their own notes over coffee Monday. The facilitator starts the session with a board that already tells the sprint's story, and the meeting spends its hour on discussion instead of data entry.
The triage wall fed by the backlog
Open action items accumulate in [Notion](/integrations/notion). Each week, the agent queries the database for unresolved items, then posts each one as a sticky on the team's triage mural, positioned by age: fresh items on the left, aging ones drifting right. The team walks the wall in their weekly sync, and what they see is the actual backlog, not a remembered approximation of it.
The brainstorm that survives the meeting
After a workshop wraps, List Widgets reads every sticky, shape, and text object off the board. The agent writes each widget's text and position to [Google Sheets](/integrations/google-sheets), clusters notes by proximity into candidate themes, and posts the summary to the project channel. The wall of stickies becomes a tracked list the same afternoon, while the context is still warm.
Human-in-Loop Highlight
Create Sticky Note writes onto a canvas that people, not systems, are looking at, and this connector has no delete: a note posted is a note someone must remove by hand, one drag at a time. That asymmetry is why bulk seeding gets a gate. An agent syncing a backlog can cheerfully post two hundred stickies onto the workshop board an hour before the session, and the facilitator's carefully framed exercise drowns in noise that takes twenty minutes of manual cleanup to undo, in front of everyone. So FlowRunner flows cap and confirm: past a threshold, the agent presents what it intends to post, "47 open items from the Ops backlog onto Q3 Triage, three columns by age," and the board's owner approves, trims, or points it at a fresh mural instead. Boards are shared thinking space. Agents should set the table, and only a person should decide how much lands on it.
Agent Capabilities
8 actionsWorkspaces
2- List Workspaces Retrieves all workspaces the connected account belongs to, paginated via the next token. The discovery step that anchors the workspace, room, and mural hierarchy.
- Get Workspace Retrieves one workspace by ID with its name and organization membership. The confirmation read before working with a workspace's rooms.
Rooms
1- List Rooms Retrieves the rooms in a workspace. Rooms group related murals and control member access, which makes them the routing layer for board creation.
Murals
3- List Murals Retrieves the murals in a room, paginated. The lookup behind finding the right board or checking whether one already exists.
- Get Mural Retrieves one mural's full details: title, room and workspace, visitor settings, and canvas dimensions. The inspection step before reading or adding widgets, and the source of the dimensions that make coordinate math sane.
- Create Mural Creates a new, empty whiteboard in a room with an optional title, returning the ID that widget operations need. The starting gun for every project, sprint, and workshop flow.
Widgets
2- List Widgets Retrieves the widgets on a mural: sticky notes, shapes, text, images, and other objects, paginated. The export read that turns a finished board into structured data.
- Create Sticky Note Creates a sticky note on a mural at explicit x and y coordinates, rectangle or circle, with the given text. The write that puts agent output in front of human eyes, capped and confirmed in bulk because there is no bulk undo.
Frequently Asked Questions
What can FlowRunner do with Mural?
FlowRunner agents can run List Workspaces, Get Workspace, and List Rooms in Mural, plus 5 more actions.
Does connecting Mural to FlowRunner require OAuth?
Yes. Mural connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.
Can Mural trigger a FlowRunner workflow automatically?
Mural doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Mural
$100 in credits. No card required. Connect in minutes.