Help

Welcome to the Airtable Community! If you're new here, check out our Getting Started area to get the most out of your community experience.

Downsides to using rich text?

Topic Labels: Base design
Solved
Jump to Solution
572 3
cancel
Showing results for 
Search instead for 
Did you mean: 

Are there any downside to enabling rich text in the long text field? Any implications for Zapier or Integromat integrations?

1 Solution

Accepted Solutions

Hello good friend!

The main thing you need to worry is compability with markdown. If you have an existing long text field that doesn’t have rich text field enabled you won’t see any impact.

If you do turn on rich text and start adding markup, you’ll have to check that the applications you’re sending that rich text use the same type of markup. In some cases you may have to go from markdown to html (see Zapier formatter guide)

Good to hear from you Max :slightly_smiling_face:

Best
Aron

Want to learn Airtable? Join me for a webinar at airtable.com/webinar

See Solution in Thread

3 Replies 3

Hello good friend!

The main thing you need to worry is compability with markdown. If you have an existing long text field that doesn’t have rich text field enabled you won’t see any impact.

If you do turn on rich text and start adding markup, you’ll have to check that the applications you’re sending that rich text use the same type of markup. In some cases you may have to go from markdown to html (see Zapier formatter guide)

Good to hear from you Max :slightly_smiling_face:

Best
Aron

Want to learn Airtable? Join me for a webinar at airtable.com/webinar

This was a pleasant surprise. Hey Aron! That last bit about converting the markdown to HTML is exactly what I needed to hear.

Thanks for that tip.

  • Max

If you want to convert a rich text field into HTML, we’ve built an extension that allows you to do that.