How to Connect Make.com with NetSuite OAuth 2.0 using HTTP module

:bullseye: What is your goal?

I am trying to connect NetSuite OAuth 2.0 using Make.com

:thinking: What is the problem & what have you tried?

I am trying to connect NetSuite OAuth 2.0 using Make.com’s HTTP Module. I have tried the same thing in other iPaaS Platforms and I can able to configure successfully.
I am Passing NetSuite’s Authorize URI, Token URI, Client ID and Client Secret in Make.com

and in NetSuite Integration Record I’m using the Call back url : https://www.integromat.com/oauth/cb/oauth2

:clipboard: Error messages or input/output bundles

Invalid login attempt.

:camera_with_flash: Screenshots (scenario flow, module settings, errors)

You’ll need to check on your NetSuite account.

Have you turned on Rest Web Services & OAuth 2.0 already? You need to enable this feature.

Have you created an Integration Record (OAuth 2.0) already? You need to create one.

Have you created a role already? You need to create one and give it specific permissions. (Web Services)

Note: Please do a test login using the specific user (account/email/password/role) in your NetSuite UI so you’ll know if the login attempt will fail or succeed.

Let me know how it goes!

Thanks @Karmic
I am trying with my Administrator Account. So I will have the permissions by default.
I have created an Integration Record (OAuth 2.0).I tried to test the connection with POSTMAN and It is connecting without any issue.

1 Like

You’re welcome! Postman validates that the API and credentials are correct. The NetSuite error is a different thing. It’s rejecting the interactive login from Make.com using OAuth consent.

Try logging out of NetSuite and logging in at the same URL shown in the OAuth window.

When logging in and it still returns as “Invalid login attempt” then you can check the Login audit trail. You’ll see the specific reason.

When logging in and it succeeds, then all you need to do is to re-try the OAuth connection.

I’ll wait for your reply!

Tried getting same issue am I doing correct way.

Now, this validates that it is a NetSuite login issue. OAuth cannot work until that browser login works with your user & role.

You can try checking in Netsuite to resolve this.

Setup > User/Roles > User Management > View Login Audit Trail (Look at the latest login attempt and why it was rejected)

Thanks for your time @Karmic

In View Login Audit Trail It is Showing Failure but it is not showing the exact reason.

:slightly_smiling_face:.

Stuck in this loop for almost a week.

Hi everyone,

I’m trying to connect NetSuite (Sandbox) to Make using the HTTP module with OAuth 2.0 (Authorization Code flow), but I keep getting an invalid_request / SC424 error after authorization.


Setup

  • Make region: EU

  • NetSuite: Sandbox

  • OAuth flow: Authorization Code

  • Make module: HTTP → OAuth 2.0

Authorize URI

https://<ACCOUNT_ID>.app.netsuite.com/app/login/oauth2/authorize.nl

Token URI

https://<ACCOUNT_ID>.suitetalk.api.netsuite.com/services/rest/auth/oauth2/v1/token

Scope

restlets

Redirect URI (forced by Make)

https://www.integromat.com/oauth/cb/oauth2

This same redirect URI is registered in the NetSuite integration.


What happens

  • NetSuite login + consent works

  • Redirect back to Make happens

  • Make fails with:

{
  "message": "The request failed due to failure of a previous request.",
  "code": "SC424",
  "suberrors": [
    { "message": "invalid_request" }
  ]
}

NetSuite sometimes also reports invalid state.


Already checked

  • Redirect URI matches exactly

  • No manual authorize URL construction (Make generates it)

  • Correct Account ID format

  • Token endpoint uses suitetalk.api.netsuite.com

  • Single tab, incognito, no extensions

  • Scope limited to restlets


Question

Has anyone successfully connected NetSuite OAuth 2.0 via the generic HTTP OAuth 2.0 connector in Make?

Is this a known limitation or is there a required parameter missing for NetSuite?

I can share screenshots if needed.

Thanks!

Open a Make support ticket referencing the SC424 + invalid_request/invalid state behaviour and that login/consent succeed since everything is configured properly already but still throws an error.