Limitations of Unito's Notion Integration

Here's a breakdown of what Unito's Notion integration can't do yet — and a few other considerations.

Unito's Notion integration is designed to get crucial data out of your databases and into other tools. You've seen what Unito can do for Notion users, so this article will cover what it can't do — yet.

What this article covers:

• Unsupported fields
• Other limitations

Unsupported fields

• Sync attachments: You won’t be able to sync attachments to (and from) Notion just yet.
• Rich text: That means no formatted text, no mentions, and no emojis 😞
• Comments: You won't be able to sync comments yet.
• Status: You won't be able to sync this field with Unito's Notion integration.

Other limitations

• Pages and blocks: Currently, our Notion integration can only sync information that comes out of a Notion database. Notion tables can't be used as blocks of work for this integration. If you turn a Notion table into a database, just make sure you give that database a name and it will show up in your flow as a block of work.
• Character limits: Notion's API limits each block to 2000 characters. That means if you sync a work item from another tool that has a field with over 2000 characters, the data in that field will be shortened to 2000 characters. This is a limitation on the Notion side, and unfortunately not something we can control. Note that if your flow is built with two-way updates enabled, the field in the original tool can have its length reduced to 2000 characters to stay synced with Notion, which can result in lost data. The best way to avoid this is to make sure you don't sync a single field with more than 2000 characters to Notion.
• Webhooks: This integration doesn't support webhooks, which means Unito can only sync changes every five minutes.
• Last edited: In order to sync data out of your Notion databases, you need to make sure they have the Last edited property.
• Inviting Unito: For this integration to work properly, you'll have to invite Unito in the databases you're syncing and give it Can Edit permissions.
• Assignees: In order to sync assignees properly, they need to have the exact same email address in Notion as they do in other tools.
• Relation: To be able to map the Relation field in a Unito flow, the link in that field needs to be part of the same database you're syncing data from.
• Subtasks: Since Notion doesn't have a work item hierarchy the way some tools do, you won't be able to sync subtasks and other sub-items (e.g. Trello checklists and Asana subtasks) to Notion.
• Syncing Notion with Google Calendar: Syncing times precisely is hard to accomplish, and due to limitations in Notion's API, Unito isn't able to accurately sync times between Notion and Google Calendar.
• Relation fields: While Unito does support syncing Relation fields, you can only sync them if they're referring to another row in the same Notion database. If they're linked to a different Notion page, you won't be able to sync them.