https://linen.dev logo
Powered by
m
It is using the default scopes composio asks to use that integration, but in Figma one of those scopes does not exist 
file_read,file_comments:write,file_dev_resources:read,file_dev_resources:write,webhooks:write
Those scopes above are the ones I find when calling 
https://backend.composio.dev/api/v3/toolkits/figma
but 
file_read
is not available to assign to the oauth app in figma. https://cdn.discordapp.com/attachments/1441065442033668239/1441065442243379260/image.png?ex=693cc887&is=693b7707&hm=d9a0d44bfb965569ad52d2640fc3a5499b684253f1aadbb49378c4bdda9414ba&
u
Hey @Mr. Roiz, looks like 
file_read
is deprecated scope. We'll remove it from the default scopes.
m
great, thanks! keep me posted
@User don't know if this helps but i removed that scope from the auth config and I still get the invalid scopes error
u
I see, could you share your authConfigId and screenshot of error from auth consent screen?
m
sure, this is the authConfigId 
ac_-EGwxqjwaG5x
and the error I get is this (see attachment), that's after I open the redirectUrl from the initiated connected account https://cdn.discordapp.com/attachments/1441065442033668239/1441082996580028568/image.png?ex=692080a0&is=691f2f20&hm=4160fd1014fb6f51685a0b58d7b2efafe282f09bf798e2a824ee636be4b8c94f&
u
@Mr. Roiz, looks like you still have 
file_read
configured in your authConfig. Could you make sure you remove it and try initiating a new connection?
m
God i forgot to save 🤦‍♂️ my bad, after saving it works
that's the change you are going to do right? just remove that scope from the defaults
just to make sure that we're synced with your defaults
u
Awesome! yes, we'll remove the scope from default set of scopes.
m
cool, thanks!
u
Hey @Mr. Roiz, we've updated the default authConfig scopes.
m
hi @Uday thanks! but i found a new scope issue here, look, i was trying to use that tool but figma requires a scope outside of composio defaults https://cdn.discordapp.com/attachments/1441065442033668239/1444040109472092170/image.png?ex=692b42a7&is=6929f127&hm=49376edd6c66d0d9be2d27f5d691b48893748568cbc63a5b49f80f9e5f87e4c1&
oh, nevermind i just realized that you updated all the defaults from figma, i thought you were going to only remove 
file_read
i'll add the new defaults to my auth config. I'll reach you out if I see something weird, sorry.
I found a wrong scope with the new default scopes, it is not available in the figma oauth app config, I get an invalid scopes everytime I try to connect with it, after removing that scope it works again. https://cdn.discordapp.com/attachments/1441065442033668239/1444044663144054876/image.png?ex=692b46e4&is=6929f564&hm=8425d7e599cb8d27dc96e7ad628206031f8a69ed6532f96a5347d96c23379b03&
u
m
u
m
weird, in my settings it is not present to select, maybe that "private" has something to do with it 🤔 but still it seems to work rn, but I had a different issue now, trying to use FIGMA_GET_FILE_JSON, it hits a rate limit with only one query https://cdn.discordapp.com/attachments/1441065442033668239/1444069738803368118/image.png?ex=692b5e3f&is=692a0cbf&hm=e8b3f2d9def6090504b9e64f2bf074a21f381d3e5747c842ca34f84350325b89&
u
I see, the rate limit could be due to high number of requests with our default app. You can use our default app for testing, but we recommend using custom creds in prod. ref: https://developers.figma.com/docs/rest-api/rate-limits/
m
Actually we're using our own creds, but it still blocks the request for some reason
those creds are used just by me in a local env
u
We checked your logs and it seems like the response was returned by Figma itself. Could you check with Figma support to understand more about their rate limiting and why you are seeing 429? docs for ref: https://developers.figma.com/docs/rest-api/rate-limits/
PreviousNext
Powered by