@OliveiraHero Hmm, I’d like to take a closer look at your overall set up before diagnosing. Can you please provide some screenshots, similar to this, of your Zap set up? This helps us get a better idea of the “full picture”, and at times can lead to easier diagnoses. 

I am facing the same problem. I’d love to know the solution to this. I’ve attached a screenshot of my setup.

Hi @Vadiraja,

Looking at the screenshot, it seems like the issue here is in the “Content Format” field. Could you please try changing that to “Plain Text”?

(view larger)

Please keep us posted! 

Thank you so much for the reply @ken.a!

However, I dropped this Zap because I found a better way to optimize my workflow. 

Hi @Vadiraja,

Gotcha, thanks for letting us know! 

@OliveiraHero, have you resolved this issue? If not, please let us know. We’re happy to troubleshoot further! 

Hi @ken.a 

I encountered a similar error again: 

body failed validation: body.children.length should be ≤ `100`, instead was `105`.

Not exactly sure what “100” or “105” means - since probably they don’t mean number of characters.

Do you know what this types of error mean? Is there a length limit for the “markdown” too?

Hi @OliveiraHero,

I’m not really an expert when is comes to markdown, but have you tried changing the “Content Format” field to “Plain text”? My hunch here is that the “Content” field of the Notion step only allows a maximum of 100 characters when set to Markdown.

Please keep us posted! 

Thank for your help, Ken!

Plain text also has a limit of 2000 character so it wouldn’t work for my use case.

Just frustrated with the unclear error message returned from the Notion flow in this case : )

Hi @OliveiraHero,

Thanks for the update.

I did some additional digging into the error of "body failed validation..." for "Create Database Item". This is often caused by invalid markdown was passed to the "Content" field. This can often be fixed by selecting "Plain Text" for the "Content Format" field. Because of backwards compatibility, we parse the "Content" field as markdown by default.

Regarding the 2,000 character limit. We do have an open feature request to remove the character limit when creating a database item. Please let me know if you’d like to get added to that.

Thanks!

@ken.a yes, can you please let me know. I’d like to overpass that limitation. 

Hi @Antoine L.!

Happy to confirm that I’ve added your vote to the feature request Ken mentioned. @OliveiraHero - I’ve also added your vote for it too, as increasing that limit for the Create Database Item action would resolve those errors you’re seeing.
 
Can’t make any promises as to when or if the character limit would removed by but we’ll definitely send you both an email once it is. I don’t know of any workarounds at present but if we come across any in the meantime we’ll be sure to share details of them here. 

@SamB  I’d love to upvote this one too! In the meantime… would it be possible to send information to the content area in successive batches?

Thanks for letting us know @calalouf! I’ve added your vote as well.

Great idea! The Notion API has a 2,000 character limit per block so that may very well work. I say may as I’ve not tested that out myself. But if you’re able to split up the content (could try a Formatter (Text > Split Text) action perhaps?), then you could potentially use another Notion action to insert the additional content that way. 

If you do give that a try and are able it working please let us know! 

Hi @SamB, well I tried it! And I *almost* got it working.

I used Split Text, segment index All as Separate fields.

Then I had to create two different consecutive actions to update Notion, each with only half my content. (This was the only way to get around my character limit.)

I was about to do my happy dance, when I realized: the second action had REPLACED (rather than appended) the content added by the first.

(I thought I had read that it would append, not replace.)

Then I found this article, which seems to suggest that I’d have to create two completely separate zaps? Is that still the best I can do? 

https://community.zapier.com/troubleshooting-99/updating-notion-item-content-is-not-appending-text-but-replacing-it-with-new-one-16525

Thank you!

Thanks for the update @calalouf. Ah, in that case I don’t think that would work as with that approach you’d be updating the block with the existing text and the additional text that was split so you’d run into the initial issue of the 2,000 character limit. 

I’ve been doing some testing and it looks like it’s possible to get around this sort of limitation by using Notion’s API request (Beta) action to append new blocks (see https://developers.notion.com/reference/patch-block-children).

You’d need to have separate actions for each section of text you want to add. I was able to successfully add the split text using the following setup: 

In the URL field I selected the ID for the page I wanted to add a block to. And in the Body field I selected the content that I split using a formatter action. Then I duplicated that action and selected the section field that was output by the formatter action which it appended the text instead of replacing it. 

One thing I should note on this is that it appears to not like any return or newline characters in the content. So those would need to be removed. Not ideal I know, but hopefully it helps as a temporary workaround for now? 

Hey folks,

Just circling back in here to share that the feature request to remove the 2,000 character limit has been implemented!  

In case you missed the email notification about this here’s the key information from that email:

That said, if you’re still experiencing issues with this please do reach out in the Community or get in touch with our Support team. 

In the meantime, happy Zapping!