Define secondary API call in Access token request

Here’s a contrived example. Let’s say, using the GitHub API, we wanted to grab the user’s username and store it in the bundle.authData context to use in URL path params. 

First add a “computed” field to store the value:
 

Next, add an API request to your handler for the access token request. You’ll need to make these API requests serially, as you need to wait for the token request to complete so you have a token to use in the request to the user endpoint. When you get the result from the call to the user endpoint, pull out the “login” field and add it to the result and Zapier will store it the computed field and make it available in the authData context.

the code (think through error handling - this is not necessarily ready for production):

const tokenRequestOptions = {

  url: 'https://github.com/login/oauth/access_token',

  method: 'POST',

  headers: {

    'content-type': 'application/x-www-form-urlencoded',

    'accept': 'application/json'

  },

  params: {

  },

  body: {

    'code': bundle.inputData.code,

    'client_id': process.env.CLIENT_ID,

    'client_secret': process.env.CLIENT_SECRET,

    'grant_type': 'authorization_code',

    'redirect_uri': bundle.inputData.redirect_uri

  }

};

const tokenResponse = await z.request(tokenRequestOptions);

tokenResponse.throwForStatus();

const results = tokenResponse.json;

const userRequestOptions = {

  url: 'https://api.github.com/user',

  method: 'GET',

  headers: {

    'Authorization': `Bearer ${results.access_token}`

  },

  params: {

  }

}

const userResponse = await z.request(userRequestOptions);

results['login'] = userResponse.json.login;

return results;
 

You can reference your computed field like this:

Let us know if that doesn’t get you up and running.