Login credential verification issue in Zapier integration

Other Questions Zapier
1

I’m having trouble with my Zapier integration. The authentication process isn’t working as expected. When I try to set up an account in the action block, it’s accepting random strings for the username and password, which causes the validation to fail.

Here’s a revised version of my authentication code:

const checkCredentials = (z, bundle) => {
  return z.request({
    url: 'https://example.api.com/login',
    method: 'POST',
    body: JSON.stringify({
      requestData: {
        credentials: {
          apiToken: 'SECRET_TOKEN',
          login: bundle.authData.login,
          secret: bundle.authData.secret
        }
      }
    })
  }).then((response) => {
    if (response.status !== 200) {
      throw new Error('Invalid credentials provided');
    }
    return response.data;
  });
};

module.exports = {
  type: 'custom',
  fields: [
    { key: 'login', label: 'Login', required: true, type: 'string' },
    { key: 'secret', label: 'Secret', required: true, type: 'password' }
  ],
  test: checkCredentials,
  connectionLabel: '{{bundle.authData.login}}'
};

Could anyone help me understand why the validation might be failing here? I’m not entirely sure if the issue lies in my code or the Zapier setup.

2

I’ve dealt with similar authentication issues in Zapier. One thing that stands out is the error handling. Instead of just throwing a generic error, try to parse the response body for more specific error messages. Something like this:

if (response.status !== 200) {
  const errorMsg = response.json.error || 'Invalid credentials';
  throw new Error(`Authentication failed: ${errorMsg}`);
}

This way, you’ll get more detailed feedback on what’s going wrong. Also, double-check that your API is actually returning a 200 status for successful logins. Some APIs use 204 or even 201 for successful auth. Lastly, make sure you’re not hitting any rate limits on your API – that can cause unexpected authentication failures too.

If all else fails, try using Zapier’s built-in HTTP request action to test the API directly. It can help isolate whether the issue is with your code or the API itself.

3

hey jess, i had a similar issue. check if ur api endpoint is correct and accessible. also, make sure the data format matches what the api expects. double-check that ‘SECRET_TOKEN’ is replaced with ur actual token. if it still fails, try logging the full response for more info. zapier support might be able to help if nothing else works

4

I’ve encountered similar issues with Zapier authentication before. The code structure looks correct overall, but there are several aspects you might want to verify. First, check that your API endpoint at https://example.api.com/login is both correct and accessible. Next, confirm that the API is expecting the data format you’re sending, as some APIs require specific key names or organization. Also, ensure that ‘SECRET_TOKEN’ has been replaced with your actual API token. Additionally, improving error handling to log full responses can offer more insights. If the issue continues, contacting Zapier support for integration-specific guidance could be beneficial.