Best answer

Error connecting learnworlds with errorUnexpected token < in JSON at position 0


Userlevel 1

Hello, I am trying to zap learnworlds with Octopus. 

 

I receive the following error; Unexpected token < in JSON at position 0

 

Can you please help? 

 

thank you,

Evdokia

icon

Best answer by Salvus Funds 18 May 2021, 08:42

View original

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

12 replies

Userlevel 7
Badge +14

Hi @Salvus Funds 

Please provide screenshots of how your Zap steps are configured, thanks.

Userlevel 1

Please find attached the screenshot.

Userlevel 1

Please note that the trial on the zap works. When I turn on to complete the step i receive this error. 

Userlevel 7
Badge +14

@Salvus Funds 

Have you checked the available help articles for each app?

LearnWorlds: https://zapier.com/apps/learnworlds/help

EmailOctopus: https://zapier.com/apps/emailoctopus/help

 

If you still have an issue, you can open a ticket with Zapier Support here: https://zapier.com/app/get-help

Userlevel 1

Hi Troy,

I checked these articles and also contacted their support. Both of them said that the error is from your end. 

Userlevel 7
Badge +14

@Salvus Funds 

Try using a different browser or a private browser.

Userlevel 1

the error is the same. The test contact is created and when I try to 'turn on zap' the error stops the zap. 

Userlevel 1

Hello Troy,

any updates with this request? can we resolve this error? 

 

thanks,

Evdokia

Userlevel 1

Salvus and Troy, I am getting the same error with a different set of apps. Was this ever resolved?

Userlevel 1

Hello Troy, the issue is resolved. With some apps you need to connect with the master admin account and not with any admin account. This is the case with learnworlds app. 

I hope my response to helpyou resolve the issue. 

Userlevel 7
Badge +11

Hi @Salvus Funds!

Thanks for sharing that you got that sorted out, and the method you used :)

Userlevel 1

Thank you both. For Gravity form it was a domain mismatch issue in the Connector configuration itself (separate from any one Zap). We pointed at the root domain, where it expected the www subdomain. Oddly, this was no issue during all tests (data pulled and passed on successfully when testing each trigger and step)---only when trying to turn the Zap on did it error out and prevent activation. Hope this helps future people who encounter this issue!