Connecting Slack to Landfall
Slack is a notification channel, not a context source: connect it and Landfall posts incident updates into it — a dedicated channel per incident, and (when a responder's email matches a Slack account) a direct mention of the person actually on the hook. Landfall never reads your Slack workspace's message history.
What you'll need
- Permission to create a Slack app (or use an existing one) in your workspace.
- An admin on your Landfall organization, to save the connection under Settings → Integrations.
1. Create a Slack app and bot token
api.slack.com/apps → Create New App
Under OAuth & Permissions, add the bot token scopes chat:write, users:read.email, and channels:manage — enough to post, match a responder by email, and create the per-incident channel.
api.slack.com/apps · OAuth & Permissions
Screenshot pending — see this guide's tracked follow-up. Install the app to your workspace
Copy the resulting Bot User OAuth token (starts with xoxb-).
2. Add it to Landfall
In Landfall, open Settings → Integrations → Slack, paste the bot token, optionally set a default channel, and run Test connection — it posts a real, visible test message.
Reference
| Field | Value |
|---|---|
| Bot User OAuth token | xoxb-… with chat:write, users:read.email, channels:manage |
| Default channel | Optional, e.g. #incidents |
See Integrations architecture for how every Landfall integration shares this same connector shape.