Unable to connect to Netsuite using TBA credential for the community node "@drowl87/n8n-nodes-netsuite"

Describe the problem/error/question

When attempting to use the community node n8n-nodes-netsuite to connect our self-hosted n8n instance (running in Docker) to NetSuite via SuiteTalk REST Web Services, the connection fails due to a permissions issue. Even with token-based authentication set up correctly and the NetSuite role assigned to the token, the node returns an error indicating insufficient permissions or a bad request. Reviewing both the workflow and the Netsuite role settings, the integration should have the correct permissions, but the error persists.

What is the error message (if any)?

Your current role does not have permission to perform this action.
Bad Request
(NetSuite error code: 400)

Please share your workflow/screenshots/recording

I am using the Netsuite node and the Token Based Authentication to setup the credential to connect to Netsuite

Share the output returned by the last node

Error: Request failed with status code 400
{
  "error": {
    "type": "INSUFFICIENT_PERMISSION",
    "message": "Your current role does not have permission to perform this action."
  }
}
  • The error is consistently returned when executing any action requiring NetSuite API access from the node, including listing or retrieving records.

Debug info

core

  • n8nVersion: 1.105.3
  • platform: docker (self-hosted)
  • nodeJsVersion: 22.17.0
  • database: postgres
  • executionMode: regular
  • concurrency: -1
  • license: enterprise (production)

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: memory

pruning

  • enabled: true
  • maxAge: 336 hours
  • maxCount: 10000 executions

client

  • userAgent: mozilla/5.0 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/ safari/
  • isTouchDevice: false

Additional context:

  • All NetSuite permissions as documented (REST Web Services, Access Token login, and permissions for relevant record types) have been assigned to the role used by the integration.
  • The access token is valid and generated with the correct user and role.
  • Authenticating with the same role in the NetSuite UI allows the same actions without issue.
  • This appears to be either a specific integration/node bug or an undocumented API requirement.
  • Error code 400 from NetSuite indicates a “Bad Request,” often due to malformed requests or insufficient role permissions, but workflow and permissions seem correct based on all available NetSuite and n8n documentation.

If the error is happening even when the credentials are correctly configured, it could be a problem with the community node, and if so, you could try to get help from the package maintainer here:

Thank you for the response. I was able to figure out the solution to the issue. I was using the incorrect ID when trying to fetch the records and that is giving me the permission error. Once I realized I have to use the Internal ID instead of the actual Sales Order number, I am able to retrieve the transaction records.

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.