Appearance
Miro
undefined
| Detail | Value |
|---|---|
| Category | Design |
| Base URL | https://api.miro.com/v2 |
| Authentication | OAuth2 |
| Endpoints | 7 |
| Connector key | miro |
Using Miro in a workflow
- Go to Connections and click New Connection.
- Pick Miro from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET | List Boards |
GET | Create Board |
GET | List Items |
GET | Create Sticky Note |
GET | Create Shape |
GET | Create Connector |
GET | List Frames |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET
List Boards
| Detail | Value |
|---|---|
| Operation ID | list_boards_0 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Miro connection from the Connection dropdown.
- In the Operation dropdown, select
list_boards_0. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Miro API reference.
GET
Create Board
| Detail | Value |
|---|---|
| Operation ID | create_board_1 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Miro connection from the Connection dropdown.
- In the Operation dropdown, select
create_board_1. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Miro API reference.
GET
List Items
| Detail | Value |
|---|---|
| Operation ID | list_items_2 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Miro connection from the Connection dropdown.
- In the Operation dropdown, select
list_items_2. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Miro API reference.
GET
Create Sticky Note
| Detail | Value |
|---|---|
| Operation ID | create_sticky_note_3 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Miro connection from the Connection dropdown.
- In the Operation dropdown, select
create_sticky_note_3. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Miro API reference.
GET
Create Shape
| Detail | Value |
|---|---|
| Operation ID | create_shape_4 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Miro connection from the Connection dropdown.
- In the Operation dropdown, select
create_shape_4. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Miro API reference.
GET
Create Connector
| Detail | Value |
|---|---|
| Operation ID | create_connector_5 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Miro connection from the Connection dropdown.
- In the Operation dropdown, select
create_connector_5. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Miro API reference.
GET
List Frames
| Detail | Value |
|---|---|
| Operation ID | list_frames_6 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Miro connection from the Connection dropdown.
- In the Operation dropdown, select
list_frames_6. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Miro API reference.