Formatting in Slack Messages

Topic Labels: Automations
7156 18
Showing results for 
Search instead for 
Did you mean: 
7 - App Architect
7 - App Architect

I saw elsewhere that Airtable-limited markdown is available for Automations (possibly only for emails? - not clear), but I can’t seem to get the markdown to work for Slack message automations.

:loudspeaker: : The Accounting base in :airtable: has been updated by
[Record (Step 1: Trigger) | Field values | By | Name] with the following release notes:
‏‎[Record (Step 1: Trigger) | Field values | Description ]

So that the message in Slack looks like this:

:loudspeaker: : The Accounting base in :airtable: has been updated by frozenforum with the following release notes:

  1. Created a new Client Companies table
  2. Converted Client Company field to be a link to Client Companies
  3. Moved company groups to Client Companies table

But instead, the Slack message looks like this:

:loudspeaker: : The Accounting base in :airtable: has been updated by frozenforumwith the following release notes: 1. Created a new Client Companies table
2. Converted Client Company field to be a link to Client Companies
3. Moved company groups to Client Companies table

I cannot get the new line (hard return) after the colon in release notes, although it does show up in the subsequent lines of the record field.

I also cannot get a space after the Name record field, so it says [name]with.

Is this a bug or am I doing it wrong (or both!)?

18 Replies 18

Okay, so here’s the deal (I think):

  • Airtable’s rich text field does not support a standard version of Markdown tags, but neither does Slack for that matter.
  • That said, the challenge is transforming whatever it is that Airtable stores as the description content into the format that Slack expects.

My guess is that you’ve probably stumbled upon a bug with Airtable’s Slack integration. When I said that it was working for me, what I failed to mention was that it works for me when “sending an automated email via Airtable’s automations”, not “posting to a Slack channel via Airtable’s automations”. I would email about this situation, and please report back here with what they say!

This is certainly a possibility. But isn’t @egordin simply creating a custom integration using an automation plugin that pulls data from Airtable fields and pushes them into Slack without any presumption of specific formatting? Ergo - aren’t we on our own when we ask Airtable to push data into Slack via an automation plugin?

If my assessment is accurate, it seems that there are two outs for @egordin -

  1. Format the data in the Airtable fields in a way that it creates the desired formatting in Slack;
  2. Use an automation script to read the Airtable data; transform it into the desired Slack markdown format; and write to the target channel using the Slack API.

Neither of these are particularly ideal approaches, but I sort’a get it If Airtable support says -

Hey, we gave you the ability to automate messaging from Airtable to Slack; formatting nuances are your problem.

One test you might want to try -

  1. Create a long text field without rich text formatting enabled.
  2. Populate that field with a sample Slack message marked up using this markdown specification.
  3. Use your automation to push this test into Slack and see what it looks like.

If it works, you could create a formula that uses SUBSTITUTE() functions to create a Slack-ready long text field from your description field.

I’m currently building a massive reflector between a large development team and a giant Insided community (like the community we’re in right now). In the process of doing this, I have learned much about the Slack markdown spec and all of its nuances and I would not blame Airtable for a NY minute for not attempting to create a unified transformation between rich text fields in Airtable and Slack message outcomes. HTML to Slack and back requires a massive number regex transformation possibilities.

Quick update - I spoke with Airtable support and they assured me that everything should be working. I recreated the Slack message in the Automations window and the space after the name works. The hard return also works. The list isnt formatted as a Slack list, but that’s ok for my needs. Thank you everyone!

7 - App Architect
7 - App Architect

One more quick update for anyone’s future reference. I wanted to see how in-line links could be sent to Slack from Airtable automations, and I read that formatting guide for markdown on Slack that @Bill.French recommended. Works perfectly.

I even got Slack to show an attachment photograph from a record by creating a link with a space as the inline text. Slack sowed the photo below the message and I didn’t need to have a link that was visible. Amazing.

Adjust the text that appears as the link from the URL to something else:

<|This message *is* a link>

5 - Automation Enthusiast
5 - Automation Enthusiast

Hi all,

I was reading this thread, and I think it’s tied to my question, but it’s not exactly what I need. (Or I can’t figure out how to apply it to my case. :slightly_smiling_face: )

For my slack name, it’s pretty straightforward: “@nicholas”. But in the case of some of my other colleagues they have a space in their name “@Michael Scott”. I’m trying to write an automation that sends a message to Slack and tags the respective person.

In this example Screenshot 2021-05-10 at 15.21.33 – I get mentioned (because the “@nicholas” matches my Slack name. But Michael wouldn’t get notified.

I have a hunch that it’s probably something in the slack name (like “Michael_Scott” or “Michael-Scott”), but I’m not sure.

Has anyone run into this problem before?

The Slack API requires tagging people by their member ID, not their username.

This is also explained here:

Amazing! Thanks so much @ScottWorld

I’ve been using this like crazy.


I have been having this same problem. I've been using the guide for Markdown in Slack linked in the Airtable automation. The other formatting commands (like *bold* and the hyperlink format) are working but "\n" isn't working - it just translates into \n text in my slack message rather than a line break. You just re-created the automation step and it worked?