# Mural integrations: murals, rooms and templates

> Create a mural, create a room and create a template from a mural in Mural. Connect Mural to the rest of your operations stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/mural-integrations/
**Categories:** Operations
**Connects through:** HTTP Connector

## Overview

Mural is a digital whiteboard where teams run workshops, brainstorms and planning sessions on shared murals organized into rooms and workspaces. Tray.ai connects to Mural through the HTTP Connector, so your workflows can call the Mural API alongside the rest of your stack.

## Use cases

### Murals

Read, create, and update murals in Mural from any Tray.ai workflow. The Mural API covers calls such as get murals and create a mural.

- Get murals
- Create a mural
- Create a mural from a template

### Rooms

Read, create, update, and delete rooms in Mural from any Tray.ai workflow. The Mural API covers calls such as list rooms and create a room.

- List rooms
- Create a room
- Update a room

### Templates

Read, create, and delete templates in Mural from any Tray.ai workflow. The Mural API covers calls such as list templates and create a template from a mural.

- List templates
- Create a template from a mural
- Delete a template

### Workspaces

Read workspaces in Mural from any Tray.ai workflow. The Mural API covers calls such as list workspaces and get a workspace.

- List workspaces
- Get a workspace

## Challenges Tray.ai solves

### Keeping Mural credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Mural credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Mural API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Mural API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Mural?

Yes. Tray.ai connects to Mural through the HTTP Connector, which calls the Mural API directly. Any call the Mural API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Mural?

The Mural API uses OAuth 2.0. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Mural connector?

Mural runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Mural connector from the Mural API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/