Slack test tokens can no longer be created.

grundleborg / slack-advanced-exporter

A tool for exporting additional data from Slack that is missing from the official data export.

MIT License

95 stars 18 forks source link

Slack test tokens can no longer be created. #20

Open kuchengrab opened 4 years ago

kuchengrab commented 4 years ago

The api-code appearing under https://[workspace].slack.com/services/export does not work with fetch-emails --api-token [token]:

When running fetch-emails, an error message appears: (Unexpected lack of ok=true in Slack API response. Is access token correct?)
https://api.slack.com/docs/oauth-test-tokens redirects to https://api.slack.com/legacy/custom-integrations/legacy-tokens where it says:

Legacy tester tokens may no longer be created.

→ Is there any possibility to access slack with a "slack app" (whatever that is)? Or has their ecosystem just become much more restrictive?

jedahan commented 2 years ago

So if you unzip the archive, the tokens are included in the urls of the export. You can use the token shown there.

jedahan commented 2 years ago

This is a case where slack has actually made things easier

sdarwin commented 2 years ago

Hi, The README files says "You'll need to obtain an API token here." leading to a page that says "Legacy tester tokens may no longer be created." Could the README be updated?

Another feature request, Slack allows you to download a members list as a CSV file. If I have a copy of the CSV file, could the slack-advanced-exporter merge it into the zip file, adding the email addresses?

fwerner1 commented 1 year ago

So if you unzip the archive, the tokens are included in the urls of the export. You can use the token shown there.

I don't find what you are referring to.

After doing unzip MyWorspaceExport.zip I get the directories with the .json files, and I don't find the "urls" you are referring to.

Here, MyWorspaceExport.zip was generated by the Slack export, the actual filename being of the format [workspace name]\ export\ [date].zip