Smartsheets Connector Failing Authorization

Q&A
, , ,
1

I have a flow that uses a Smartsheet connector to retrieve data from a specific sheet via the Smartsheet API. Every time the connector attempts to access the sheet, it returns a 403 Authorization Error. I am the owner of the sheet and the connector, so my email is authorized to access both. I’ve changed the Smartsheet setting to anyone with a link, this didn’t resolve the issue. I have confirmed the connector is configured and connected, I have tried to reconnect. I’ve ensured the app is created in Smartsheets with the appropriate API configuration. I also tried the Enterprise Smartsheet MCP connector and was met with the same error. How can I get Quick to successfully access Smartsheets?

2

Hi @csmorin,

Welcome to the Quick community!

A 403 that persists after reconnecting, across both the standard and Enterprise MCP connectors, usually points to an authorization issue rather than sheet sharing (since OAuth access scopes don’t override sheet-level permissions).

Here are a few things I’d suggest checking:

  1. Confirm the MCP Clients capability is enabled in your Smartsheet Admin Center. This is a common cause, and even as the sheet owner, access can be blocked if your System Admin hasn’t activated it.

  2. Fully re-authorize the OAuth connection, rather than just reconnecting, try deleting the connection, re-running the consent flow, and approving all requested scopes. A simple reconnect can sometimes retain only limited default scopes, which can lead to a 403.

  3. Verify the OAuth app registration in Smartsheet Developer Tools, the redirect URL should exactly match https://{region}.quicksight.aws.amazon.com/sn/oauthcallback (with your correct AWS region), and the Client ID/Secret and region endpoints should match your connector configuration.

  4. You can safely revert the anyone with the link change, link sharing doesn’t affect API/OAuth access, so it isn’t needed here.

Helpful documentation:

If the issue still persists, I’d recommend filing a case with AWS Support so we can dive into the details and help you further. Here are the steps to open a support case. If someone at your company manages your AWS account, you may not have direct access to AWS Support and might need to raise an internal ticket to your IT team or whoever manages the account, they can open an AWS Support case on your behalf.

3

I’ve re-authorized the OAuth connection and confirmed the configuration is correct. I’ve also confirmed the OAuth app registration in Smartsheets is correct. I was granted Group Admin access, but this isn’t sufficient to check MCP Clients capability. I suspect this is the cause of the problem, how can I have the System Admin activate it?

4

Hi @csmorin

Thank you for confirming all of that. Since you’ve verified the OAuth connection, configuration, and app registration are all correct, the most likely remaining cause is that the Amazon Quick Connector isn’t enabled on the Smartsheet side. This is a setting under AI Management in the Smartsheet Admin Center, and as you noted, only a System Admin can enable it, Group Admin access isn’t sufficient. When this connector is turned off, Smartsheet blocks the connection attempts, which would be consistent with the 403 you’re seeing.

Since this setting lives entirely within the Smartsheet Admin Center, I’d recommend reaching out to the Smartsheet connector support team (or your Smartsheet System Admin) to confirm whether this capability is enabled for your plan and to turn it on if needed.

5

Hi @csmorin,

Just checking back in since we haven’t heard from you in a bit. I wanted to see if the guidance shared earlier helped resolve your question, or if you found a solution in the meantime.

If you still have any additional questions related to your initial post, feel free to share them. Otherwise, any update you’re able to provide within the next 3 business days would be helpful for the community.

Thank you.