Silky in Slack

Silky has one set of hiring actions. The same set whether you invoke them from the dashboard, from a Claude Code session, from the API, or from Slack. You can do everything in Slack that you can do in Silky.

Go to Settings > Integrations in the Silky dashboard and press Install Silky for Slack. Slack walks you through the standard OAuth flow. Pick the workspace, pick the default channel you want activity in, and approve the scopes.

Silky needs: channels:read, chat:write, commands, im:write, and users:read. That is the minimum needed to post cards, read your roster, and run slash commands. We do not request history access.

After OAuth completes you are redirected back to Silky with a confirmation. The default channel starts receiving activity immediately.

Mention @silky in a channel where it is invited, or send it a direct message (DM). Ask in plain English. Silky reasons over your data, takes the action, and confirms anything destructive or bulk before it happens.

Silky always asks for confirmation before anything destructive or a bulk action. Everything else happens immediately and posts the result in the thread.

If it is in the Silky action registry, it works in Slack. Here is the full list, grouped by what you are trying to do. Phrase it however you like. Silky understands plain English.

Expect the list here to grow. If you are not sure whether something is possible, ask Silky. It will either do it or tell you it cannot.

If you prefer typing /silky reject Alice over asking in natural language, slash commands always work. They sit alongside the natural-language surface as a quick shortcut.

Every event Silky thinks you care about posts as a Block Kit card. Cards link back to the full record and most include one-click buttons so you can act from Slack.

When a card is posted for Alice Smith, everything else about Alice lands in that thread. Scorecards, offer updates, notes. The channel stays tidy and the context stays tight. If Alice applies to a second role, she gets a fresh thread scoped to that role.

Each user controls what they get DM'd about from their own settings page at app.silky.so/settings/slack. Most recruiters turn on reference red flags, offers signed, and the weekly digest. Interviewers usually only want interview reminders and feedback nudges. Admins can set defaults for the workspace, but users can override on their own account.

The default channel picks up everything. If you want interviews in #hiring but red flags in #silky-alerts, set a per-event override. The UI for this ships shortly; until then you can set it via the API.

{
  "channel_overrides": {
    "interview_scheduled": "C07ABCD1234",
    "interview_feedback_nudge": "C07ABCD1234",
    "reference_red_flag": "C08XYZ9876",
    "application_received": null,
    "weekly_digest": "C09DIGEST42"
  }
}

Keys are Slack notification type names. Values are Slack channel IDs (the ones that start with C). A null value falls back to the default channel. Missing keys also fall back to the default. Every notification type listed on this page is a valid key.

Five things to try.

• Install from Settings > Integrations.
• Pick a default channel.
• Mention @silky in the channel and ask 'how many applicants did we see this month?'
• Ask Silky to draft a new role: @silky new job senior backend engineer Sydney around AUD 180k.
• Open your Slack preferences at app.silky.so/settings/slack and choose which events you want DM'd.