>_AFK / Docs
ProductPricingCommunity
Start free

Chat integrations

Start an enabled AFK Automation from Slack, Google Chat, or Discord and keep follow-up messages attached to one durable AFK session.

Before you connect

You need:

  • An AFK account with a model connection configured.
  • A connected daemon that can access the intended project.
  • An enabled on-demand Automation. Scheduled Automations cannot be selected for chat.
  • Permission to install apps in the chat workspace or server.

Each person links their own chat identity to AFK through the guided sign-in flow. Do not manually share or map another person's AFK account.

Slack

  1. Install AFK in the Slack workspace.
  2. Open the AFK App Home and choose Connect AFK.
  3. Sign in with Google, choose your personal or organization scope, and select an enabled Automation.
  4. Send AFK a direct message, or invite it to a channel and mention @AFK.
  5. Continue in the originating Slack thread to keep using the same AFK session.

AFK can use bounded recent context from the direct message or channel where it is present. It cannot use this integration to read another channel. General multi-person direct messages are not supported; use a private channel with an explicit @AFK mention for collaborative private work.

Google Chat

  1. Install AFK from Google Workspace Marketplace.
  2. Open a direct message with AFK and choose Continue with AFK.
  3. Choose your personal or organization scope and an enabled Automation. AFK then starts the request that opened the connection flow; you do not need to mention it again.
  4. Use plain text in a direct message, or mention AFK in a shared space. The afk prefix also works.
  5. Continue in the same Google Chat thread to keep using the same AFK session.

In shared spaces, AFK's account-connection card is visible only to the person who requested it. Other participants do not see the private linking action.

Reply delivery works without conversation-history access. Bounded recent history is optional and requires a Google Workspace administrator to approve AFK's read-only Chat app message scope in the Google Admin Console.

Discord

  1. Install AFK in the Discord server.
  2. Mention @AFK with a task in a server channel or thread.
  3. Follow the guided link in AFK's reply to connect your AFK account and select an enabled on-demand Automation.
  4. Mention @AFK again after linking. Continue mentioning it in the originating channel or thread for follow-up requests.

Discord direct messages are not supported. AFK suppresses generated mentions, uses only bounded recent context from the originating server channel or thread, and posts only replies the agent explicitly chooses to publish. The Discord bot owner must enable Message Content Intent. A Discord-enabled deployment currently supports one AFK server replica because only one replica may own the Gateway connection.

Privacy and replies

Chat requests and relevant bounded context may become part of AFK session history and may be sent to the customer-selected model provider. AFK does not use chat-platform data to train machine-learning or large-language models. Detailed agent work remains private in AFK unless the agent explicitly publishes a reply to the originating conversation.

Troubleshooting

  • No connection action: reopen the app Home or run the platform's connect command.
  • No Automation available: create and enable an on-demand Automation in AFK, then reconnect.
  • Request does not start: confirm the selected daemon is online and can access the project.
  • No channel reply: confirm the app is present and has permission to post in the originating conversation.
  • History unavailable: the workflow can still run without prior chat context; check the platform permission status in Account → Integrations.

Disconnect, uninstall, or request deletion

Disconnect an installation from Account → Integrations or uninstall it from the chat platform. AFK revokes or removes the stored provider credential when it receives the uninstall or disconnect event. For access, export, or deletion requests concerning associated data, email support@mooglest.com. We verify the requester and complete valid deletion requests within 14 business days, except where retention is legally required.

Support

Email support@mooglest.com with the platform, workspace or server name, approximate time of the problem, and the visible error. Do not include access tokens, API keys, or private repository content. We aim to respond within two business days.