You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[`slackauth`](https://github.com/rusq/slackauth) library, which drives a
7
+
browser via the [Rod](https://go-rod.github.io/) / CDP protocol to capture the
8
+
Slack session token and cookie on your behalf.
9
+
10
+
Run the following command to add a new workspace:
11
+
12
+
```bash
13
+
slackdump workspace new
14
+
```
15
+
16
+
You will be asked for the workspace name (the part before `.slack.com`), then
17
+
prompted to choose one of four login methods described below.
18
+
19
+
## Login Methods
20
+
21
+
### Interactive (recommended for most users)
22
+
23
+
A clean browser window opens on the Slack login page. Log in as usual —
24
+
including any SSO, MFA, or company identity provider steps. The browser
25
+
closes automatically once the session token and cookie have been captured.
26
+
27
+
Choose **Interactive** unless your workspace uses Google Authentication (use
28
+
**User Browser** instead) or you know your email/password login works
29
+
headlessly.
30
+
31
+
### User Browser
32
+
33
+
Instead of launching a bundled browser, Slackdump opens **your own installed
34
+
browser** (Chrome, Firefox, etc.) on the Slack login page. Your existing
35
+
browser profile is used, which means Google Authentication and other flows that
36
+
block embedded browsers will work.
37
+
38
+
When prompted, select the browser you want to use from the list of detected
39
+
browsers.
40
+
41
+
### Automatic (Headless)
42
+
43
+
Slackdump automates the email + password login flow entirely without opening a
44
+
visible browser window. You will be prompted to enter your email and password
45
+
in the terminal. If Slack sends a confirmation code to your email, you will
46
+
also be asked to enter that.
47
+
48
+
**Limitations:** only works with plain email/password workspaces. Does not
49
+
support SSO, Google, or passwordless (OTP-only) workspaces.
50
+
51
+
### QR Code (Sign in on Mobile)
52
+
53
+
Use this method when other browser-based methods are blocked (e.g. Google Auth
54
+
blocks the embedded browser, or your workspace enforces strict SSO policies).
55
+
It uses the Slack "Sign in on mobile" QR code flow, which still relies on Rod
56
+
internally to exchange the QR image for a session token.
57
+
58
+
**Steps:**
59
+
60
+
1. In the logged-in Slack desktop app or web client, click your **workspace
61
+
name** in the upper-left corner.
62
+
2. Choose **Sign in on mobile**.
63
+
3. Slack displays a QR code. **Right-click the QR code image** and choose
64
+
**Copy Image**.
65
+
4. Switch to the Slackdump terminal — it will be showing a text field titled
66
+
"Paste QR code image data into this field".
67
+
5. Paste the copied image data into that field and press **Enter**.
68
+
69
+
Slackdump exchanges the base64-encoded image with Slack's API and captures the
70
+
resulting session token and cookie automatically.
71
+
72
+
## Troubleshooting
73
+
74
+
| Symptom | Fix |
75
+
|---------|-----|
76
+
| Browser fails to launch or closes immediately | Close any existing Chrome/browser processes, then retry. See [Troubleshooting](troubleshooting.md#browser-fails-to-launch-or-closes-immediately). |
77
+
| Slack shows "browser not supported" | Switch to **User Browser** or use [manual login](login-manual.md). |
78
+
| Google / SSO login blocked | Use **User Browser** or **QR Code** method. |
79
+
| Login hangs after completing 2FA / SSO | Use **QR Code** method or fall back to [manual login](login-manual.md). |
80
+
| Running in Docker / CI | Browser-based login requires an interactive display. Use [manual login](login-manual.md) instead. |
0 commit comments