Smartsuite API Fail

#rookieuser
#likelydumbmistake

I have added My Workspace Token and workspace ID,

System Bardeen did not give me any warnings that the connection failed and we have way to double check contect after the connection is done.

In trying to create a scrape with Tbales I ran into an API error when trying to deploy a scrape.

The error was saying API triggering Error.

Any help would be appreciacted.

1 Like

Hi Cameron! Welcome to Bardeen community :smile:

Guessing you joined us yesterday on the event.

We might need some details to understand this issue!

Doesn’t sound like a dumb mistake :sweat_smile:

Seems like you connected to Smartsuite and used both the token and workspace id.

When exactly did you get the error? After connecting?

Or after running an automation? (If so please share the automation)

Can you share the error you ran into? Here’s how:

Share the error

In your case I would try the following and see if it fixes it:

  1. Remove the integration and add it again

RESTARTING BARDEEN INTEGRATION

  1. Make sure you’re on the latest version of Bardeen
    Version of the app

Sorry for delay responce,

Life is busy in Startup world :slight_smile:

Here is the Error

{
“clientErrorCode”: “SmartSuite list records: UnexpectedErrorPayload (400)”,
“message”: “SmartSuite failed to list records: (400)”,
“userHint”: “A request to the service API failed. Please check the error details”,
“trackError”: “default”,
“stack”: “Error: SmartSuite failed to list records: (400)\n at i.fromSerialized (chrome-extension://ihhkmalpkhkoedlmcnilbbhhbhnicjga/background.js:88:14484)\n at Object.from (chrome-extension://ihhkmalpkhkoedlmcnilbbhhbhnicjga/background.js:95:1090)\n at Object.Vq [as listRecords] (chrome-extension://ihhkmalpkhkoedlmcnilbbhhbhnicjga/348.js:1605:7212)\n at async rD.handle (chrome-extension://ihhkmalpkhkoedlmcnilbbhhbhnicjga/348.js:1605:9801)\n at async chrome-extension://ihhkmalpkhkoedlmcnilbbhhbhnicjga/348.js:1676:91554\n at async Fy.guard (chrome-extension://ihhkmalpkhkoedlmcnilbbhhbhnicjga/348.js:1676:72451)\n at async jy.invokeFunction (chrome-extension://ihhkmalpkhkoedlmcnilbbhhbhnicjga/348.js:1676:91512)\n at async jy.invokeSequence (chrome-extension://ihhkmalpkhkoedlmcnilbbhhbhnicjga/348.js:1676:82470)\n at async jy.invokePlaybook (chrome-extension://ihhkmalpkhkoedlmcnilbbhhbhnicjga/348.js:1676:84052)\n at async Wy.execute (chrome-extension://ihhkmalpkhkoedlmcnilbbhhbhnicjga/348.js:1676:101408)\n at async Wy.executeWithResult (chrome-extension://ihhkmalpkhkoedlmcnilbbhhbhnicjga/348.js:1676:101853)”,
“clientErrorHistory”: [
{
“clientErrorCode”: “SmartSuite list records: UnexpectedErrorPayload (400)”,
“clientErrorDetails”: {
“type”: “ApiError”,
“module”: “SmartSuite”,
“operation”: “list records”,
“status”: 400,
“headers”: {
“access-control-allow-credentials”: “true”,
“allow”: “POST, OPTIONS”,
“alt-svc”: “h3=":443"; ma=86400”,
“cache-control”: “no-cache”,
“content-language”: “en”,
“content-length”: “180”,
“content-security-policy”: “style-src ‘self’ ‘unsafe-inline’ cdnjs.cloudflare.com; script-src ‘self’ ajax.googleapis.com cdnjs.cloudflare.com ‘unsafe-inline’; default-src ‘self’; font-src ‘self’; img-src ‘self’ data: *.nasa.gov”,
“content-type”: “application/json”,
“date”: “Tue, 14 Nov 2023 04:24:16 GMT”,
“referrer-policy”: “same-origin”,
“server”: “Caddy, gunicorn”,
“vary”: “Accept, Accept-Language, Cookie, Origin”,
“via”: “1.1 34a9164f42ba6fa44b5d26746860cf6e.cloudfront.net (CloudFront)”,
“x-amz-cf-id”: “jrFGho1EAGQOOcDJCQRic1tbC9cIzF_gLFkM0F5piXSozOM7E5Z-kw==”,
“x-amz-cf-pop”: “BNE50-P2”,
“x-cache”: “Error from cloudfront”,
“x-content-type-options”: “nosniff”,
“x-frame-options”: “DENY”,
“x-xss-protection”: “1; mode=block”
},
“message”: “SmartSuite failed to list records: (400)”,
“code”: “UnexpectedErrorPayload”
},
“fingerprint”: [
“SmartSuite list records: UnexpectedErrorPayload (400)”
],
“message”: “SmartSuite failed to list records: (400)”,
“userHint”: “A request to the service API failed. Please check the error details”
}
],
“fingerprint”: [
“SmartSuite list records: UnexpectedErrorPayload (400)”
]
}

As i suspect its something to do with the API Connection ,

I have added and removed it twice.

Have put the API Token in separately from the workspce ID as the scrren prompt suggest ?

Hi Cameron

Thanks for sharing this!

Let’s make a step by step check

  1. Did you get the API token and input it on the first box.

  2. Then you got the workspace id from the URL and inputted into the second box?

And didn’t work?

Here’s a clip from our latest event where we show how to connect to smartsuite as well.

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