Skip to main content

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

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions 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.

Hi,

I am new to Zapier and try to make a Zapier CLI integration work.

I have created an integration with Zapier UI, converted it with zapier convert, and I can successfully “zappier push” it back.

However I have issues when doing “zapier test”:

  • I receive a 401 error from my server when each unit test is run
  • In fact, it is normal, because the unit test passes “Authorization: Bearer {{bundle.authData.access_token}}” litterally, without replacing the access_token with its actual value
  • And the session authentication (which should return an access_token from the email/password) is not even called from the tests.

So I have 2 questions:

  • how to manage the tests so that it uses a valid access_token?
  • how to make sure that {{bundle.authData.access_token}} is replaced with its value?

These are probably dummy questions, but I could not find any answer in the documentation. 

Many thanks!

Hi @bfredo123 - Just use normal ES6 string interpolation because the double curly braces string interpolation won’t work inside functions. In your case, it should look like the following:

{

  //...

  headers: {

    Authorization: `Bearer ${bundle.authData.access_token}`

  }

}

Also, in your unit tests, the authentication won’t happen automatically, you should actually define the access_token in your bundle.authData. You can use this example as a reference.

 

Many thanks, it works!

What I did into more details, if it may help others:

  1. I created a 0_auth folder in the test folder (‘0’ to make sure it’s invoked at first, with alphabetical order).
  1. In this folder, I do like the provided example, in a ‘testAuth.js’ test module, and I store the access_token received from the server in a variable exported by this test module (in the example, the ‘secret’ token does not work in my case, as the server returns a token which I cannot control on the client side)
  1. In any other test, I set the bundle.authData.access_token to this testAuth.access_token 
  2. Actually, leaving the simple quotes as ‘Bearer {{bundle.authData.access_token}}’ does the job (otherwise, I guss that the headers would be initialized at the test startup, even before the access_token has been retrieved from the server

Thanks again, I was really wondering how to properly organize my test bench.

Terms & Conditions