About Zapier Community
New to our Community? Get to know more about our space and how to make the most of your time here.

Code of Conduct Community FAQ's Zapier Common Questions What to Expect

Get Started With Zapier
New to Zapier? We have got you covered with our Zapier 101 Resources.

Zapier Essentials

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Zapier Products
Learn more about Zapier's new products.

Zapier Tables Zapier Interfaces

Zapier Reading
All of our best learning resources can be found here.

Featured Articles Show & Tell AI Hub Zapier Tools Hub

Learning Groups
Excited to meet other builders? Check out our interest areas full of doers, dreamers, and in-betweeners.

User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Best answer

Getting “authentication failed: Cannot find module” error when authenticating

  • 12 June 2023
  • 1 reply
  • 127 views
sb89
Badge

Hi,

I’m fairly new to zapier and I am trying to do some investigation of what would be required for our company to integrate with Zapier.

I’m using the CLI to set up an integrations and I have managed to add authentication and an instant trigger. However, when I go to test a Zap using that trigger, I'm presented with the following when trying to log in:

 

Any idea what I’m doing wrong? The code passes test locally and deploys without any issue

icon

Best answer by sb89 12 June 2023, 15:24

View original

1 reply

sb89
Badge

I think I figured this out. The scaffolding for the trigger added the following to the index.js file:

 

 

changing it to the following has fixed the issue:

 

Reply


Terms & Conditions