> ## Documentation Index > Fetch the complete documentation index at: https://docs.firsttouch.com/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > For API operations, fetch https://gateway.firsttouch.ai/api/public/openapi.json for the complete input/output schemas, internal references, and x-mcp-annotations. Endpoint Markdown intentionally omits generated schema fragments. Select /api/public/tools/ using the exact underscore-separated name. Send requests to https://gateway.firsttouch.ai; the canonical document currently omits servers. Start at https://docs.firsttouch.com/api-reference/agent-start.md. # Slack Task Notifications > Connect Slack, map members, and review or complete supported FirstTouch task cards in direct messages. FirstTouch sends supported newly created tasks to assigned members in Slack direct messages. Task cards are separate from [Slack Agent conversations](https://docs.firsttouch.com/WebApp/Slack/Agent.md), but share the same installation and member mappings. ## Connect Slack and Enable Members **1. Select the FirstTouch Team** Switch to the intended Active Team. A Team Admin must manage the connection and mappings. **2. Install from FirstTouch** Open **Team Settings > Integrations** and choose **Connect** on the Slack card. Complete installation in Slack, selecting the intended destination and granting the requested permissions. **3. Enable member mappings** Return to the Slack integration **Settings**. Review suggestions, choose the correct Slack recipient for each FirstTouch member, and explicitly enable each mapping. Suggestions start disabled. Start installation from FirstTouch, not a generic Slack installation page, so the installation is associated with the correct Team. Current mapped access does not require each member to complete a separate personal authorization flow or use a slash command. A FirstTouch Team connects to one Slack installation; several FirstTouch Teams can share the same Slack destination. Disconnect the existing connection before moving a Team elsewhere. Within one Team, the same Slack recipient cannot map to two different FirstTouch members. ## Permissions and Eligibility Slack adds no separate FirstTouch plan or Seat Type restriction. Normal task ownership, Team Role, sender eligibility, entitlement, and action requirements still apply. A displayed card is not permanent permission to act. Slack must allow installation and grant the requested messaging and member-directory permissions. FirstTouch Admin authority does not grant Slack administrator authority. See [Roles and Permissions](https://docs.firsttouch.com/WebApp/Roles-and-Permissions.md). ## Which Tasks Appear? Notifications cover supported newly created tasks assigned to an enabled mapped member. They go to that member's direct messages, not a configured channel. Existing pending tasks are not backfilled when a mapping is enabled. Historical updates or reassignment alone do not create new cards. Re-enabling a mapping establishes a new starting point for notifications. | Task type | Actions when permitted | | - | - | | Manual Task | **Mark as done**, **Skip** | | Call Task | **Log call**, **Skip**; logging does not place a call. | | Approval Task | **Approve**, **Review / Edit**, **Cancel** | ## Review and Approve Approval applies checked actions and marks unchecked actions skipped. **Review / Edit** opens supported message or task fields; **Apply** submits approval, not merely a saved draft. > [!WARNING] > > **Cancel** stops the Approval Task and its Flow Enrollment. Slack does not provide the web app's three-second **Undo** countdown for card actions; do not expect another confirmation before processing. If a review changes or becomes blocked, review the refreshed card. Saved edits are not guaranteed to roll back if approval subsequently fails. ## Review Limits Reviews exceeding ten steps, or containing step selections that Slack cannot safely represent, must be reviewed and approved in FirstTouch. | Field | Slack edit limit | | - | - | | LinkedIn connection note | 300 characters | | InMail subject | 200 characters | | Email subject | 1,000 characters | | InMail body | 1,900 characters | | Other supported review text fields | 3,000 characters | Empty required fields or unresolved text enclosed in curly braces block **Apply**. These edit limits do not override channel eligibility, sender capacity, or other action requirements. ## Missing or Outdated Cards Delivery can retry with increasing delays and respect Slack rate limits. It is not instant or guaranteed. Existing cards are refreshed through background processing. Check the Team connection, enabled recipient mapping, task creation time, assignment, and current FirstTouch task state. An older card can become unusable if its task was completed elsewhere, its review changed, or its mapping was disabled. Open [Tasks](https://docs.firsttouch.com/WebApp/Tasks.md) before retrying an uncertain approval. ## Reconnect or Disconnect If settings show **Reconnect required**, use **Reconnect** to grant updated permissions. Existing mappings are preserved. Start a new agent conversation after reconnecting. Disabling a mapping or disconnecting Slack schedules cleanup of affected cards without canceling the underlying FirstTouch tasks. Cancel the task or Flow Enrollment in FirstTouch when work must stop; disabling notifications is not a substitute. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.