Integrations · Projects & issues

Mural in the conversation.

Mural is a digital whiteboard platform enabling distributed teams to visually brainstorm, map ideas, and collaborate in real time with sticky notes and diagrams. Connect it once and your copilot works in it directly without leaving the thread — and your workflows can act on it while the customer is still typing.

No credit card required · 7-day free trial

Mural
Projects & issues
01 · COPILOT

Ask for it in plain language. It does the Mural part.

Copilot rides inside the inbox. With Mural connected it works there from the same panel as the conversation — no second tab, no copying an order number across.

  • Get room by ID
  • Get workspaces
  • Get current user
  • Get Mural Widgets
  • Create sticky note
  • List users in room

What a specific connection exposes is decided by Mural, not by us: Settings → Apps lists the real tools your connection carries, each with its own switch.

02 · WORKFLOWS

Read Mural from inside a workflow.

Mural is a place a workflow looks things up rather than one that starts it. Trigger on a conversation, a schedule or another app's event, then use an AI Agent step to work in Mural and hand the answer to the steps that follow — a message, a CRM update, an escalation.

If Mural does publish events to your workspace, they appear in the trigger picker the moment the connection is made.

03 · THE AI AGENT STEP

One step that decides which Mural tools to call.

A workflow's AI Agent step runs a bounded tool-calling loop over the apps you have connected and returns an object whose fields you declared. So "find the record, check the status, and give me status and owner" is one step rather than four — and the fields it returns are available to every step after it.

You declare the output

The rows you name become the variables downstream steps read, so a branch can test what Mural said.

You cap the effort

A step budget and a model tier per node — the loop stops where you told it to.

Only what you switched on

The loop can call the Mural tools you left enabled and nothing else.

Setup

Connect Mural in about a minute.

  1. 1

    Open Settings → Apps

    It is open to everyone in your organization, not just admins — which apps your copilot can reach is part of doing the job.

  2. 2

    Find Mural in Browse

    The catalogue runs to hundreds of apps and is searchable. Connect Mural from its card.

  3. 3

    Authorize with your own Mural account

    You sign in on Mural's own screen and approve the access. The connection carries that account's permissions — no API keys are pasted into Cloodot.

  4. 4

    Choose the tools it may call

    Open the connection and switch off anything you would rather it never touched. A tool you switch off is out of reach from the next question onward.

Mural questions.

How do I connect Mural to Cloodot?
Open Settings → Apps in Cloodot, switch to Browse, and search for Mural. Connecting it opens Mural's own sign-in and consent screen; when you come back, the app is listed as Connected and your copilot can use it. Nothing is installed and no keys are pasted into Cloodot.
What can Cloodot do in Mural?
Work of this kind: get room by id; get workspaces; get current user; get mural widgets; create sticky note; list users in room. The exact list depends on what your Mural account is allowed to do — Settings → Apps shows every tool the connection actually exposes.
Can I limit which Mural tools Cloodot may use?
Yes. Open the connection and every tool it exposes is a switch, searchable by name. A tool you switch off is out of reach from the next question onward, so a read-only Mural connection is a matter of leaving the writes off.
Can a workflow use Mural without a trigger from it?
Yes. Mural is read from inside a workflow rather than starting one: a workflow triggered by a conversation, a schedule or another app's event uses an AI Agent step to work in Mural and hand its answer to the steps that follow.
Who in my team can connect Mural?
Anyone in the organization — Apps is not restricted to admins and owners, because which apps a copilot can reach is part of doing the job. The connection carries the permissions of the Mural account that authorized it, so a projects & issues connection is only ever as broad as the account behind it.
See it on your own inbox

Try the whole thing, today.

Start free. Connect a channel, train an agent on your own content, and you'll have a working deployment in your inbox the same afternoon.