# Fix Slack app install failing with workspace_app_not_found

## TL;DR
workspace_app_not_found means the install link points at an app that does not exist in that workspace's context, usually a deleted app or a wrong app id in the URL. Confirm the app still exists in your Slack app config and regenerate the install link. The URL is stale, not your workspace.

## The error
```text
Slack app installation failed
Error: workspace_app_not_found
```

## Use this skill
Agent? Search Vectle for this error:
```bash
curl -s "https://vectle.com/api/v1/search?q=slack app install failed workspace_app_not_found"
```

## Fix it

### Step 1: Verify the app still exists

```bash
Open your Slack app configuration at api.slack.com and confirm the app is listed and not deleted.
```

Expected: The app exists with the same app id as the install link.

### Step 2: Regenerate the install link

```bash
From the app config, generate a fresh install or shareable URL.
```

Expected: The new link carries the current app id.

### Step 3: Check the workspace matches

```bash
Confirm you are installing into the intended workspace, not a different one where the app was never added.
```

Expected: The workspace domain matches your target.

### Step 4: Retry the install with the fresh link

```bash
Open the new link and complete the OAuth install flow.
```

Expected: Installation succeeds and the app appears in the workspace.

### Step 5: Update any docs or buttons

```bash
Replace the stale install URL wherever it was published.
```

Expected: No stale links remain for users to hit.

## When this applies

- Slack app installs fail with workspace_app_not_found
- An install link that used to work now fails
- You are distributing a Slack app to workspaces

## When it doesn't

- The install starts but OAuth fails later (check scopes and redirect URLs)
- The app installs but does not respond (check the event subscriptions)
- The error is about admin approval (that is a workspace policy gate)

## Compatibility

Slack platform apps. api.slack.com app config as of 2026.

## Variant phrasings

### slack workspace_app_not_found on install

Same error. The app id in the URL is the thing to verify first.

### slack app install link invalid

Install links go stale when apps are deleted or recreated. Regenerate from the current app config.

### slack app not found in workspace

If the app was uninstalled from the workspace, reinstall from a fresh link rather than reusing the old one.

## Why it happens

Install URLs embed the app id. When the app is deleted, recreated, or the URL was copied from a different app, the id no longer resolves in the workspace's context. Slack fails the install rather than guessing which app you meant.

## Edge cases

- App ids change when you recreate an app; every published install link must be regenerated
- Enterprise Grid workspaces have their own install rules; org-level installs differ from workspace installs
- Users clicking old links in chat history will keep hitting this; update the pinned messages

## If it still fails

- Reproduce with one API call in isolation, outside the agent, to separate platform issues from agent issues.
- Check the platform status page and changelog; OAuth and webhook behaviors change without warning.
- Capture the full request and response with timestamps for the vendor ticket, redacting credentials.
- Test in a second workspace or sandbox to rule out workspace-specific policy blocks.
- If the integration is business-critical, build the fallback now: cached data, a manual trigger, or a second provider.

## Prevention

- Store OAuth credentials in a secrets manager with rotation reminders.
- Build the reconnect flow before you need it; every integration gets revoked eventually.
- Log token ages so expiring grants are visible ahead of time.
- Keep a sandbox integration for testing config changes.
- Document the required scopes per integration so reinstalls request the right ones.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_O6B_BTLDh06eehNEI_oIGQ