How to Fix the “Incompatible Text Formats” Error
This error usually happens when you sync work items that have rich text. Here’s how to fix it.
What does this error mean?
Section titled “What does this error mean?”
This error happens when you try to sync specific fields from work items with rich text to a tool that doesn’t support rich text (think bold or italics). In these situations, your Unito flow won’t sync fields with rich text.
Here’s a full list of Unito connectors and which ones support rich text.
| Connector | Does it support rich text? |
|---|---|
| Airtable | ❌ |
| Asana | ✅ |
| Azure DevOps | ❌ |
| Basecamp | ✅ |
| Bitbucket | ✅ |
| ClickUp | ❌ |
| Confluence | ❌ |
| Eloqua | ❌ |
| Facebook Ads Manager | ❌ |
| Facebook Insights | ❌ |
| Favro | ❌ |
| GitHub | ❌ |
| GitLab | ❌ |
| Google Ads | ❌ |
| Google Analytics 4 | ❌ |
| Google Calendar | ❌ |
| Google Contacts | ❌ |
| Google Forms | ❌ |
| Google Sheets | ❌ |
| HubSpot | ❌ |
| Intercom | ❌ |
| Jira | ✅ |
| Jira Data Center | ✅ |
| Jira Service Management | ✅ |
| Jotform | ❌ |
| Mailchimp | ❌ |
| MeisterTask | ❌ |
| Microsoft Excel | ❌ |
| Microsoft Outlook | ❌ |
| Miro | ❌ |
| monday.com | ❌ |
| Notion | ❌ |
| Pipedrive | ❌ |
| PostgreSQL | ❌ |
| Salesforce | ❌ |
| ServiceNow | ❌ |
| Slack | ✅* |
| Smartsheet | ❌ |
| Snowflake | ❌ |
| Stripe | ❌ |
| SurveyMonkey | ❌ |
| Teamwork | ❌ |
| Trello | ✅ |
| Typeform | ❌ |
| Wrike | ❌ |
| Xero | ❌ |
| Zendesk | ✅** |
| Zoho Projects | ✅ |
*These connectors only support markdown-style rich text, which isn’t compatible with all tools.
**These connectors only support basic text formatting, like bold, italics, and titles.
How to solve this error
Section titled “How to solve this error”You can troubleshoot this error in one of two ways:
-
Remove rich text from your tools: If your use of rich text isn’t essential to your workflows, you can remove rich text to ensure your data syncs without any issues.
-
Switch affected field mappings to one-way: This error is typically triggered when your Unito flow tries to sync data from the connector that doesn’t support rich text to the one that does. To fix this, you can change the field mapping for the affected field so changes are only synced from the tool that supports rich text to the one that doesn’t.
-
For example, if you’re syncing data from an Asana project to a Google Sheets spreadsheet, the description field in Asana might have rich text in it, causing this error. You can fix this by mapping the description field so changes are only synced from Asana to Google Sheets.
-
Not sure how to do this? Check out our guide on field mappings.