Skip to main content

Hey all,

 

I’m trying to connect a glide app to OneSignal via Zapier so I can send out push notifications to my IOS users. I can send the push to devices with no issue from the OneSignal dashboard, however whenever i try to trigger a zap to complete the task, it fails with this error “Message Notifications must have Any/English language content”. 

Anyone with any ideas or experience with OneSignal i would be so greatly appreciative of some help.

It's probably something super trivial as i don’t have heaps of experience with OneSignal. 

 

Thanks so much,

James :)

Hi @jamesmctaggart 

Good question.

To help give us more context, please post screenshots with how your Zap steps are configured along with the encountered error.


Hey @Troy Tessalone!!

Thanks for the prompt reply. Really appreciate it. 

 

Please see the attachments of Zap Steps and Error Page. 

This screenshot was too big to attach: https://ibb.co/g4K3qp2

 

Fields 1 = Link to Screen in Glide

Field 2 = Username from Glide

Field 3 = text from Glide

Field 4 = text from Glide

Field 7 = text from Glide 

 

Can see in run details that the information is being correctly sent from Glide to Zapier, as per the screenshot of the error. If you look at the Contents line, the data from glide is correct. Sounds like OneSignal isn’t accepting it :(


@jamesmctaggart 

Check the Troubleshoot tab.

 

Wondering if it’s related to the emoji.

 


@Troy Tessalone 

Please see attachment from Troubleshoot tab.

Will remove the emoji from the data now and re-test.


@Troy Tessalone 

Unfortunately i just received the same error.  

 


@jamesmctaggart 

Can you show screenshots with the (more) expanded for both?

 


@Troy Tessalone 

 

Sure! 

 


@jamesmctaggart 

Maybe try this:

Change “English” to “Any/English”

 


@jamesmctaggart

Otherwise try just “en” w/o the double quotes.

How can I change the default language to not use English?

"Any/English" (or "en" with the API) is the Default language.

 


@jamesmctaggart 

Make sure to reference the links provided in the field descriptions.


@jamesmctaggart 

OneSignal help article about language and localization: https://documentation.onesignal.com/docs/language-localization


Thanks so much @Troy Tessalone!!

The “Any/English” errored but “en” worked straight away.

 

You’re a legend!! 

Thank you

 

 


Thank you for following up here to let us know what solved it @jamesmctaggart! So glad Troy was able to hop in here and point you towards a solution. Awesome work! 🙌⚡️


Reply