Slack data powers conversation context and supports prompt delivery throughout Fostr. This page explains how messages, threads, and user context are synced into the platform.

Interaction with Slack Events

Fostr listens for Slack events such as slash commands, app mentions, button clicks, and other permissioned triggers. Depending on the event, Fostr responds with:

• Context summaries relevant to the workflow
• Workflow accelerators to move processes forward
• Task or assignment updates, such as marking completion or resolution

Data Storage Behavior

By default, Fostr does not replicate or persist Slack conversation data. Messages are only carried into Fostr if a user takes explicit action to convert them.

Content is persistently stored in Fostr only when it is translated into one of the following:

• A task
• A decision log
• An action record

Anything else remains ephemeral and stays within Slack.

Ingestion and Action Triggers

Fostr determines what to ingest exclusively through real‑time event hooks. These cover actions such as:

• Slash commands
• App mentions
• Button responses and approvals
• Message actions tied to the Fostr app

Unless a user explicitly promotes Slack content into a workflow record, no Slack data is retained beyond the immediate interaction.