Text Parser Not Showing Pattern Options + Gmail Error 403

Post:

Hey everyone,

I’m currently building an automation in Make.com and I’ve run into two issues. Maybe someone here can help me out.


:one: Issue – Text Parser shows no Pattern options

I have a Slack trigger that captures messages.

After that, I want to use the Text Parser to structure the incoming data and then send it back to Slack — basically:

Airtable → Text Parser → Slack.

The problem:

When I click on the “Pattern” field in the Text Parser module, no options appear.

I can’t select or map anything — it looks like the parser doesn’t recognize any data or doesn’t display any input.

I’ve already mapped most of the Slack data correctly (as far as I can tell).

Does anyone know why the Pattern field stays empty?

Do I need to define something in the input first, or could it be an issue with how Slack sends the data?


:two: Issue – Gmail connection (Error 403)

I actually wanted to use Gmail instead of Outlook in this automation.

However, when I try to connect my Gmail account, I keep getting Error 403.

I followed the tutorial from Liam Ottley (the 2-hour video where he explains the whole automation setup) and did everything exactly as shown — but the error still appears.

Does anyone know what’s causing this 403 error with Gmail?

Could it be due to recent changes in Make or Google’s API permissions?


Thanks a lot in advance :folded_hands:

I’ll also attach screenshots so you can better see what’s happening.

Hey there,

you write a regex pattern inside the Pattern field. Its not a selection field.

Try this for the gmail connection.

The Text Parser only allows you to EXTRACT data, not STRUCTURE the data into a different format.

If you would like to structure the data, the simplest way is to use an AI module like the Make AI Toolkit “Extract information from text” module —

Retrieves information that you specify from a text.

For more information about the Extract information from text module and Make AI Toolkit app, see the corresponding Integrations page and the Help Centre documentation.

Hope this helps! If that is not quite right, we can try exploring other options.

@samliew