-
Get Started With Unito
-
Using Unito
-
Items in Sync, Account Management, and Billing
-
Troubleshooting and FAQs
-
Data Privacy & Security
-
Integration Documentation
- Airtable
- Azure DevOps
- Basecamp
- Bitbucket
- ClickUp
- Confluence
- Eloqua
- Favro
- GitLab
- Google Ads
- HubSpot
- Intercom
- Jotform
- Mailchimp
- MeisterTask
- Microsoft Excel
- Microsoft Outlook
- Miro
- monday.com
- Notion
- Pipedrive
- PostgreSQL
- Slack
- Snowflake
- Stripe
- SurveyMonkey
- Teamwork
- Typeform
- Xero
- Zendesk
- Zoho Projects
- MySQL
-
Atlassian Jira Integration Docs
-
Trello Power-Up Docs
-
2-Way ServiceNow Integration
-
Asana Integration Docs
-
Flows, Features and FAQs
-
Google Integration Docs
-
Salesforce Integration Docs
-
Wrike Integration Docs
-
Azure DevOps Integration Docs
-
Smartsheet Integration Docs
-
GitHub Integration Docs
An Overview of Unito's Miro Integration
Connecting Miro with Unito? Here’s what you can expect from this integration.
In this article:
What Unito syncs from Miro
Unito syncs cards from Miro boards by linking individual fields from these cards to items in other tools (e.g., Trello cards, Jira issues, ServiceNow records).
Supported fields for Miro cards
Unito supports eight fields for Miro. Here's a list of these fields as well as supported sync directions and rules.
Quick definitions:
- One-way: Changes in this field can be synced to the tool it’s integrated with, but changes in the other tool can’t be synced back.
- Two-way: Changes to this field will be synced to the tool it’s integrated with, and changes in the other tool will be synced back.
- Rules: This field can be used to build rules.
Miro Card fields | One-way | Two-way | Rules |
Assignee | ✔ | ✔ | ✔ |
Card color* | ✔ | ✔ | ✔ |
Card ID | ✔ | ||
Description | ✔ | ✔ | |
Due date | ✔ | ✔ | |
Frame | ✔ | ✔ | ✔ |
Link to card | ✔ | ||
Title | ✔ | ✔ |
*Custom colors aren't yet supported.
Other documentation
Need to know more about this integration? Check out our documentation on: