Slack App still not including `search:read` scope!

Questions
1

Describe the problem/error/question

Despite this thread, where @Jon added the scope search:read thread, when installing the Slack app today, the scope search:read is not actually requested.

Also side note, please submit the app to the Slack Marketplace :eyes::heart_hands:

Steps to reproduce:

  1. Go to: https://[instance].app.n8n.cloud/projects/[project]/credentials
  2. Click on “Create new credential”
  3. Search for “Slack OAuth2 API”
  4. Click “Continue”
  5. Open Dev Tools
  6. Click “Connect my account”

You will see several requests being made. Look for this one:

https://simpleclub.app.n8n.cloud/rest/oauth2-credential/auth

Actual Slack OAuth URL

This endpoint will return the following URL that gets opened:
Raw:

https://slack.com/oauth/v2/authorize?user_scope=channels%3Aread+channels%3Awrite+chat%3Awrite+files%3Aread+files%3Awrite+groups%3Aread+im%3Aread+mpim%3Aread+reactions%3Aread+reactions%3Awrite+stars%3Aread+stars%3Awrite+usergroups%3Awrite+usergroups%3Aread+users.profile%3Aread+users.profile%3Awrite+users%3Aread&client_id=1228824229986.1235010924836&redirect_uri=https%3A%2F%2Foauth.n8n.cloud%2Foauth2%2Fcallback&response_type=code&state=eyJ0b2tlbiI6ImIzd2tlS3hhLUhuQzFldW9jbTM0S3FOWnI2ODRVcmliTjhwUSIsImNpZCI6Ik10bU5SZDdnUjVLTjlaWXAiLCJjcmVhdGVkQXQiOjE3NjI3MjIxMTAxNzgsInVzZXJJZCI6IjllYjdhODdmLWRmZTUtNDE5ZS05NzYzLTdhNDQwMWZjZDhjNiIsImhvc3QiOiJzaW1wbGVjbHViLmFwcC5uOG4uY2xvdWQvcmVzdCJ9&scope=chat%3Awrite

Prettified:

https://slack.com/oauth/v2/authorize
  ?user_scope=channels:read channels:write chat:write files:read files:write groups:read im:read mpim:read reactions:read reactions:write stars:read stars:write usergroups:write usergroups:read users.profile:read users.profile:write users:read
  &client_id=1228824229986.1235010924836
  &redirect_uri=https://oauth.n8n.cloud/oauth2/callback
  &response_type=code
  &state=<state>
  &scope=chat:write

Expected Slack OAuth URL

The Slack OAuth URL returned by the n8n API must also include the scope search:read (only configuring it in the Slack app, if this was done?! is not sufficient).

This endpoint will return the following URL that gets opened:
Raw:

https://slack.com/oauth/v2/authorize?user_scope=search%3Aread+channels%3Aread+channels%3Awrite+chat%3Awrite+files%3Aread+files%3Awrite+groups%3Aread+im%3Aread+mpim%3Aread+reactions%3Aread+reactions%3Awrite+stars%3Aread+stars%3Awrite+usergroups%3Awrite+usergroups%3Aread+users.profile%3Aread+users.profile%3Awrite+users%3Aread&client_id=1228824229986.1235010924836&redirect_uri=https%3A%2F%2Foauth.n8n.cloud%2Foauth2%2Fcallback&response_type=code&state=eyJ0b2tlbiI6ImIzd2tlS3hhLUhuQzFldW9jbTM0S3FOWnI2ODRVcmliTjhwUSIsImNpZCI6Ik10bU5SZDdnUjVLTjlaWXAiLCJjcmVhdGVkQXQiOjE3NjI3MjIxMTAxNzgsInVzZXJJZCI6IjllYjdhODdmLWRmZTUtNDE5ZS05NzYzLTdhNDQwMWZjZDhjNiIsImhvc3QiOiJzaW1wbGVjbHViLmFwcC5uOG4uY2xvdWQvcmVzdCJ9&scope=chat%3Awrite

Prettified:

https://slack.com/oauth/v2/authorize
  ?user_scope=search:read channels:read channels:write chat:write files:read files:write groups:read im:read mpim:read reactions:read reactions:write stars:read stars:write usergroups:write usergroups:read users.profile:read users.profile:write users:read
  &client_id=1228824229986.1235010924836
  &redirect_uri=https://oauth.n8n.cloud/oauth2/callback
  &response_type=code
  &state=<state>
  &scope=chat:write

What is the error message (if any)?

Your Slack credential is missing required Oauth Scopes
Add the following scope(s) to your Slack App: search:read

Please share your workflow

Share the output returned by the last node

NodeOperationError: Your Slack credential is missing required Oauth Scopes

Information on your n8n setup

  • n8n version: 1.106.3
  • Database (default: SQLite): SQLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main): own, main
  • Running n8n via (Docker, npm, n8n cloud, desktop app): n8n cloud
  • Operating system: ??
2

Okay never mind, apparently, that was already done by @ cadiac in this PR:

Also, I’m super confused why are we on a two months old version of n8n on the cloud version :exploding_head:and how do we even upgrade that?

Why aren’t we always on the latest version when using a cloud product?!

When I saw the original thread, I was not even considering that we’d not have the change from @Jon installed for us.

Edit: Update your n8n cloud instance:

1 Like
3

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