Update notification events and channels for an already-connected Slack workspace. Only listed events change; others remain unchanged. Slack must be connected and licensed. Connecting Slack requires the Wayfront interface.
Connector
Destructive
OAuth718,556 tools. Updated 2026-10-29 11:28
"Slack" matching MCP tools:
- View notification settings and available events for an already-connected Slack workspace.ConnectorOAuth
- Check a Slack webhook URL shape. Secret discarded.ConnectorNo auth
- Slack channel name shape, value discardedConnectorNo auth
- Send appointment events to a URL (Pro). SimpleDock posts a test event first and saves the webhook only if the URL answers 2xx. Non-Slack payloads are signed: verify the X-SimpleDock-Signature header with signingSecret, which is returned only now. ZAPIER and SLACK need hooks.zapier.com / hooks.slack.com URLs; every URL must be https://. eventTypes empty = every event; locationIds empty = every location. Listing, editing, and deleting webhooks happen in Settings → Integrations, not over MCP. Returns { webhookId, signingSecret, test }. Requires scope locations:write (Admin role).ConnectorAPI key
- Send appointment events to a URL (Pro). SimpleDock posts a test event first and saves the webhook only if the URL answers 2xx. Non-Slack payloads are signed: verify the X-SimpleDock-Signature header with signingSecret, which is returned only now. ZAPIER and SLACK need hooks.zapier.com / hooks.slack.com URLs; every URL must be https://. eventTypes empty = every event; locationIds empty = every location. Listing, editing, and deleting webhooks happen in Settings → Integrations, not over MCP. Returns { webhookId, signingSecret, test }. Requires scope locations:write (Admin role).ConnectorOAuth
Matching MCP Servers
- AlicenseAqualityCmaintenanceMCP Server for the Slack API, enabling Claude to interact with Slack workspaces.870,822 npmMIT
- AlicenseAqualityDmaintenanceInteract with Slack Workspaces over the Slack API. Supports stdio and Streamable HTTP transport. Extended from Anthropic's archived server822,381 npm75MIT
Matching MCP Connectors
Check a Slack webhook URL shape. Secret discarded.
Enable interaction with Slack workspaces. Supports subscribing to Slack events through Resources.
- Creates an automation on a perspective. Triggers: per_interview (fires on every completed conversation) or scheduled (daily/weekly, with digest, invite, or insights purpose). Actions: internal insight discovery, webhook, email, or connected provider-backed integrations such as Slack, HubSpot, Gmail, Google Docs, Notion, and Confluence. Execution modes: direct (fast, deterministic, webhook-only) or agent (LLM-powered, required for insights and delivery channels). Behavior: - Each call creates a new automation — even if name/config matches an existing one. - Once enabled, the automation starts firing on real events: per_interview sends on every completed conversation going forward; scheduled sends a real message on the configured cadence (daily/weekly). - For HubSpot, the workspace's HubSpot connection is required — errors with "Could not resolve HubSpot portal ID — please reconnect HubSpot" if not connected. - Webhook channels: do NOT ask the user for the endpoint URL or credentials — neither is accepted through this tool. The automation is created disabled and the response includes configure_url, a web app page where the user sets the URL (and an authentication header if needed). Share that link and ask the user to reply "Done" after saving, then enable the automation via automation_update. - Insight automations use kind "insights", execution_mode "agent", omit channel, and use scheduled purpose "insights" when scheduled. - Errors when the perspective is not found or you do not have access. When to use this tool: - The user wants ongoing notifications on every completed conversation (per_interview). - Building a daily/weekly digest delivered to Slack, email, HubSpot, or a webhook (scheduled). - Running scheduled insight automation which creates insights without external delivery. When NOT to use this tool: - Trying a one-off send before going live — create the automation, then use automation_test (use override_email on email channels to avoid hitting real recipients). - Editing or toggling an existing automation — use automation_update. - Connecting Slack or HubSpot — use integration_manage first; the provider must be connected before slack/hubspot channels work. Example — per-conversation Slack notify (resolve the channel with slack_channel_resolve first, then pass it as resource_id): ``` { "perspective_id": "...", "automation": { "name": "Notify Slack", "trigger": { "type": "per_interview" }, "execution_mode": "agent", "channel": { "type": "composio", "delivery_config": { "provider": "slackbot", "tool_slug": "SLACKBOT_SEND_MESSAGE", "resource_id": "C0123ABCD", "resource_name": "#research" } } } } ``` resource_id is the Slack channel ID or name. The channel is re-verified live on create; an unresolvable channel is rejected. Typical flow: 1. integration_manage (operation: "list"/"connect") → ensure Slack / HubSpot is connected (only needed for those channels) 2. For Slack: slack_channel_search / slack_channel_resolve → find/verify the channel to use as resource_id 3. automation_create → create the automation 4. automation_test (with overrides) → verify delivery before relying on itConnectorOAuth
- Use this when the user wants accessibility alerts for a site to go to a Slack channel, or to a different one than now. WRITES to this website's Inclusify configuration, never to the site itself. It CANNOT install Slack: that is a browser OAuth flow on the Inclusify panel's Integrations page and no assistant can do it, so this refuses until the workspace is connected. It also cannot list channels — ask the user for the channel, by name or by Slack channel ID. NOTE THAT THIS POSTS A MESSAGE to the channel before saving, on purpose: a binding that looks right and posts nowhere is worse than a refusal, because the customer believes they are covered. If the post fails — wrong channel, private channel the app was never invited to — nothing is saved and the reason is returned. REQUIRES CONFIRMATION, because it both writes to their Slack and redirects where alerts go. Changing the channel keeps the existing notification settings; only a first-time binding takes the defaults. Use set_slack_events to change which alerts fire. Needs the PRO plan, matching the panel.ConnectorDestructiveAPI key
- Inventory of the user's connected accounts and workspaces: Google (Gmail) accounts, Slack workspaces, and Facebook Messenger. Call this to find out WHICH accounts/workspaces are connected and WHAT each one can do — read/search (`readable`), send (`sendable`), and for Google accounts also Calendar (`calendar`), Drive metadata search (`drive`), Drive CONTENT reads (`drive_content` — read_file_content/download_file_content), Gmail label management (`mail_labels`), Gmail drafts (`mail_drafts`), and Contacts (`contacts` — search_contacts, list_contacts, list_other_contacts, list_contact_groups, get_contact_groups). Questions like "which Gmail/Google accounts are connected?" or "which Slack workspaces can I search or send from?" are answered by this tool — don't guess from search results. It is also the source of the labels accepted by the `accounts`/`account` parameters of search_messages / search_messages_raw / send_message and the calendar/drive/gmail/slack/contacts tools, so call it FIRST to learn valid labels and how many Gmail accounts exist before sending. A false capability means the connection predates that scope — 設定 → サービス連携 で再接続 grants it. Returns, per account: account (label), connector, connector_label, `belongs_to` (the classification label this account's work is filed under — derived automatically when the account is connected: the user's existing label for that company if there is one, otherwise a new label named after the Slack workspace or the mail domain — so a company's Slack and mail share one label; 'プライベート' for personal mail; null = unfiled), readable, sendable, and for Google accounts the capability booleans above; plus `belongs_to_options`: every label the user has, each with its accounts (a label may have none) — these names are the only values add_memory `belongs_to` accepts. Chatwork accounts (connector "chatwork", readable/sendable) are listed too; use the Chatwork tools (list_chatwork_rooms, send_chatwork_message …) — send_message does not handle Chatwork.ConnectorOAuth
- Create a place for alerts to be delivered: a webhook, an email list, or Slack. This provisions a real outbound effect. Once a rule points at this channel, alert content leaves the platform to wherever you named — for a webhook, an HTTP POST to that URL. The payload carries the alert title (which is a span's error message, so it can contain model output), its labels, counts, and a sample of trace ids. Needs the `channels:manage` capability. name: a label for the channel, 1 to 120 characters. channel_type: `webhook`, `email`, or `slack`. url: for a webhook — the https URL to POST to. recipients: for email — 1 to 20 addresses. slack_channel_id: for Slack — a channel id from the connected Slack workspace. Slack must be connected in the console first. enabled: whether it starts receiving deliveries. Defaults to true. workspace: optional workspace id, name, or `org-name/workspace-name` when the same name occurs in two of your orgs (defaults to your default). Example: > Send my alerts to this webhook. ```json { "name": "create_alert_channel", "arguments": { "name": "ops webhook", "channel_type": "webhook", "url": "https://hooks.example.com/rius" } } ```ConnectorAPI key
- List a workspace's Slack channels whose name contains a substring (paged). Reads the indexed channel directory, so it's fast. Read-only — to confirm a specific channel before saving an automation, use slack_channel_resolve. Behavior: - not_connected: Slack isn't connected — connect it via integration_manage (operation "connect") first. - directory_synced: false with an empty result means the directory hasn't been indexed yet — run slack_channel_refresh, then search again. Examples: - `{ "query": "feedback", "limit": 25 }` - `{ }` (list all indexed channels)ConnectorOAuth
- Refresh a workspace's Slack channel directory from Slack and wait for it. Only needed when a channel can't be found via slack_channel_search / slack_channel_resolve — most channels (including newly created ones and channels the bot was just invited to) are indexed automatically within seconds, so try those first. A full refresh can take a while on large workspaces, so confirm with the user before running one (unless a resolve reported "refresh_required"). Behavior: - Starts a refresh, or joins the one already running for the workspace (only one runs at a time). - Long-polls up to wait_ms, then returns "running" — call slack_channel_refresh_status to keep waiting (it won't start a new crawl). - After "completed", use slack_channel_search / slack_channel_resolve to find the channel.ConnectorOAuth
- List the authenticated customer's registered notification channels (Slack or email). Returns JSON. Each entry's `id` is the notification-channel registry UUID — pass this value (not `channelId`) into Fixter alert-rule routing (the `channelIds` parameter of `save_alert_rule` / `set_alert_rule_delivery`, served by a different service). `channelId` is the Slack-side channel id: pass it, not `id`, as the `channel` of `set_issue_digest_config`. `sources` lists the notification sources this channel receives — null means all sources, including future ones.ConnectorAPI key
- Permanently delete a Slack channel trigger you own. The agent stops starting Runs for that channel. To keep the trigger but stop it firing, update it with `enabled: false` instead.ConnectorDestructiveNo auth
- <summary>Which integrations the account has connected, keyed by integration_id (gmail, outlook, linkedin, slack, googlesheets, salesforce, notion, ...) — for an integration get_tool_connect_url can link, the same id it takes. Call this before telling a user an integration is unavailable, or before minting a connect link for one they say is already connected — it may already be active.</summary> <returns> <description>A dict mapping each integration_id to its connection status; read one with result[integration_id]['connected']. Some entries carry extra detail — linkedin, google_calendar, and fathom include needs_reconnect (connected, but the auth broke and the user must re-link). The gmail and outlook entries carry one connected account's address under 'email', while linkedin's 'email' is an internal account ID, not an address. A missing key means that integration wasn't checked, not that it's disconnected. The slack entry carries two independent flags: 'connected' is the workspace bot link that delivers Sliq's notifications, and 'slack_mcp_connected' gates only your Slack MCP tools in chat — judge notification delivery by 'connected' alone.</description> </returns>ConnectorOAuth
- List where your signals are delivered — Slack channels, webhooks, Google Sheets, n8n, Clay and Notion — with each destination’s health and recent failure state. Connection settings (URLs, tokens) are never returned.ConnectorOAuth
- Lists the Slack workspaces (teams) the user has connected in Slack Desktop. Start here for Slack — the workspace id it returns is what slack_list_channels / slack_read_channel_messages / slack_search_messages need. Reads from the local IndexedDB cache — no token needed. Only workspaces that have been synced to disk are returned. Each entry's `permissions` carries only the permissions this service has (read, send, write; a key that is missing does not apply). true: allowed in the account's boxes (LMCP's icon → My apps → open the app's row → the account's Read · Send · Write) and the item accepts it. false: turned off there, or the item is read-only (`read_only`: true).ConnectorOAuth
- Post a message to a Slack channel as YouSpot right now, optionally as a reply in a thread. Only for text the user already approved word for word in this conversation, or for an agent delivering its own report. When the user asks you to write, draft or prepare a Slack message, use draft_slack_message instead: nothing posts until they tap Send on the card. Only channels the bot has been invited to work; use list_slack_channels to find ids. '## ' headings, '- ' bullets, **bold** and [label](url) links all render.ConnectorNo auth
- Attach an existing organization channel to an agent, so the channel's events wake it. Find the channel with list_channels. A webhook channel lets callers outside Valet reach the agent. Attaching a channel that is already attached reports it and changes nothing. Slack needs a Slack app and a browser, so for Slack this gives the step to take and attaches nothing. Requires connecting a Valet account.ConnectorNo auth
- Use this when the user wants to change which Slack and Teams channels get Winquill's alerts, or asks where they go: "stop the morning summary in Slack". Change only what the user asked for; with neither send nor stop it changes nothing and says where alerts go now. Owners and admins can change alerts. Needs a Winquill account and workspace. Not for connecting a channel (Winquill dashboard, Settings, Connections) or for email alerts (use watch_tenders). Example: {"app":"slack","stop":["morning_summary"]}ConnectorDestructiveNo auth
- Monitor Google Maps reviews and detect only NEW ones since previous runs (stateful tracking per business), with Bayesian urgency classification and optional Slack alerts — your reputation radar. Use when tracking review activity OVER TIME for businesses you already know. Use google_maps_scraper instead for one-shot bulk extraction of business data; use review_pitch_generator instead to turn existing bad reviews into a sales pitch and shareable report; use local_presence_audit instead for a one-time full presence audit. Returns review objects flagged isNew with urgency scores. Side effects: sends a Slack notification ONLY if you provide your own Slack webhook URL in the input — no messages are sent otherwise. Auth: Apify API token required (Authorization: Bearer). Rate limit: 60 calls/min/IP on this facade. Pricing: $0.25 per run + $0.01 per new review.ConnectorNo auth