SNOWFLAKE SPOKE

[k4ktusk1nd]

Hello, 

I tried integrating Snowflake with ServiceNow via the recently released Snowflake Spoke. 
Unfortunately the spoke actions do not load all the dynamic action inputs (like warehouses, database etc) assigned to the user (Screenshot). 

Here, the dynamic action input correctly fetches the Role from the Snowflake Instance for the TEST_SERVICE User. 
But then the Warehouse, Database, Schema and additional Parameters are not fetched. 

When I test the Get Warehouse Spoke Action with the Parameters User ID = TEST_SERVICE and Role = SERVICENOW_TECHNICAL_ROLE I get the following error Message: 

{
    "Action Status": {
        "code": 1,
        "message": "Error:  Bad Request.The request payload is invalid or malformed.\nRole 'SERVICENOW_TECHNICAL_ROLE' specified in the connect string is not granted to this user. Contact your local system administrator, or attempt to login with another role, e.g. PUBLIC. (sys_script_include.f6b59170472b19d0554ab988436d43c7.script; line 249)"
    }
}

 
Secondly, I previously was able to script the inputs to the spoke action (instead of relying on the dynamic action inputs). But now the script option is not available anymore:

Any suggestions on how I can make the spoke work? 

[Dr Atul G- LNG]

Hi @k4ktusk1nd 

Better log a now support case for this.

[Yash Mittal]

Hi
Can anyone confirm whether this spoke can connect with SnowFlake in VPN environment also ? 

[pritesh9131]

k4ktusk1nd
Got any solution on this ?
I am facing exactly same issue. But this issue occurs in QA instance only & working fine in DEV.
I am using exactly same configurations.

[Vikram Reddy]

Hey @k4ktusk1nd,

Both symptoms trace back to one cause: Snowflake itself is rejecting the SERVICENOW_TECHNICAL_ROLE for TEST_SERVICE, and the rest of the dynamic inputs never get a chance to load because of it.

That error text isn't the spoke talking, it's Snowflake's own OAuth error 390186, which fires when the requested role isn't present in the access token, either because the grant genuinely isn't there or because EXTERNAL_OAUTH_BLOCKED_ROLES_LIST or a scope restriction on your security integration is filtering it out before it reaches ServiceNow. The Role dropdown populating fine is a red herring: that field just lists roles associated with the user, it doesn't confirm the role will actually survive into the token. Worth running SHOW GRANTS TO USER TEST_SERVICE and checking the blocked-roles list and scope mapping on the integration.

Warehouse, Database, and Schema all fail together because each is a chained action (get_warehouses feeding get_databases feeding get_schemas). The "verify the output variable is named output" text is just the generic error for when the upstream action returned nothing, since get_warehouses itself never ran.

On scripting: your second screenshot still shows User ID as "Scripted (Expand to edit)", the other fields just show no icon at all while blocked. That reads like Flow Designer withholding the toggle until a field clears its blocked state, not the option being pulled. Fix the role grant and it should reappear on Warehouse once it resolves.

Thank you,
Vikram Karety
Octigo Solutions INC