Slack

Create cases, tasks, and notes from Slack, link threads to cases, and receive personal notifications. Slack integration is available on Pro.

Connect Slack

1. In the Web app, select the Epismo workspace and open Workspace integrations (/workspace/integrations). An Owner or Admin chooses Add to Slack on the integrations page and authorizes the app for the intended Slack workspace.
2. Each member runs /epismo connect in Slack and chooses Connect Epismo. Authorize Slack message access, then sign in to Epismo and approve the connection. Use the same Slack account throughout this flow.
3. Return to Slack. If connection began while creating or saving work, use Continue in the Epismo DM to resume, then confirm the destination.

An active Slack installation is tied to one Epismo workspace and cannot simultaneously point to another. Each user connects their own Epismo account and must be a member of that workspace. Commands run with that user's existing permissions and workspace context; installing the app does not grant access to cases.

Create work from Slack

Forms let you choose a recent open case or enter a Case code, UUID, or Epismo case URL. A typed reference takes priority over the selection. New cases can use a playbook alias, UUID, or URL and JSON input; select Epismo Teams to share the case, or leave the selection empty to keep it private to you. Tasks can be assigned to yourself or left unassigned.

Review the destination, audience, and credit cost before choosing Save. Creating a case or task costs 5 credits; adding a note costs 1 credit. Existing-case operations require edit access to an open case.

Link and inspect Slack threads

From a Slack message menu, choose Link thread to Epismo, select a recent open case or enter its code, UUID, or URL, then confirm the destination, audience, and cost. Epismo reads the entire thread using your connected Slack account; you must be able to read it. A case supports up to 25 external sources. These are separate from timeline records.

Open the case in Epismo Web and check External sources, below the tasks, for its original Slack link, status, saved content, and capture/check times. In an open case you can edit, choose Add source and paste a Slack thread URL. If multiple source connections are available, select one first; a single authorized connection opens the URL input directly. If a connection needs your authorization, or no source connections are available, the menu includes Integration settings. Complete workspace installation and your personal Slack read authorization before linking.

Case editors can also refresh or unlink existing sources from Web. CLI, MCP, and API can link threads using your active personal Slack connection in the selected workspace.

Content is shared with all case work collaborators, even when they cannot read the original Slack thread. Public-only readers cannot see source links or captures, even on a public case. Public AI reviews and Brief generation exclude sources. Text already copied into a record, review, or Brief follows that object's visibility and is not erased by unlinking.

Fetching runs asynchronously after linking, Slack changes, or a manual refresh. Reads return saved content without contacting Slack; an idle thread is not continuously polled. Closed cases do not trigger automatic refreshes, but editors can explicitly refresh or unlink. During an update the previous complete capture remains visible. Check status and timestamps before treating it as current.

A complete capture supports up to 500 messages / 750 KB; partial captures are never published. File metadata may be included, but attached files are not downloaded. Only the latest complete content is retained. The revision identifies that content; unchanged content preserves the revision and capture time while advancing the check time. Historical content is not retrievable. The case response limits total source content to 1 MB: if snapshotOmitted is true, retrieve the latest complete source using its source ID with the source API, epismo_case_source_get, or epismo case source get.

Linking and unlinking cost 2 credits each. Linking includes the first completed capture, even when updates queue before it starts. Each subsequent completed manual or automatic capture costs 1 credit to the source’s case billing account, including a closed case whose explicit refresh request is fulfilled. Charges use each case’s billing account, including Web writes. Queuing, failures, pagination, and retries are free. Requests coalesced into one capture incur one charge for that case, even when the content is unchanged. Reads do not trigger refresh charges. Reuse an idempotency key only for the same uncertain retry.

Each case holds one source per resource, regardless of who links it. Repeated linking contributes the caller’s grant to that source; another case has independent content. Any case editor can unlink the source once for all collaborators, deleting its saved content and grant references without disconnecting provider accounts. Disconnecting a user removes only that user’s contributed grant. Another contributed live grant can continue updating the source. Content is cleared and synchronization suspended when no grants remain, including when the app is removed. Transient failures hide the current capture and schedule retries; they do not erase the last complete saved content. Reconnecting creates a new user grant, even within the same Slack installation. Link the same URL again to contribute the new grant to the existing source; manual refresh alone cannot add a new grant.

Personal notifications

Connected members receive their workspace's Epismo notifications in Slack DMs. Notifications are enabled by default and are controlled per Epismo user, across their Slack connections.

• /epismo notifications shows your setting with Turn on and Turn off buttons.
• /epismo notifications on or /epismo notifications off changes it directly.
• /epismo disconnect disconnects your own Epismo account from that Slack workspace.

Turning notifications off leaves commands and thread linking available and does not change email notification settings. Notifications skipped while disabled are not replayed when you turn them back on. Disconnecting or removing the Slack app removes affected source captures; ordinary records remain.