Slack Integration Checklist

To deploy Slack messaging capabilities for automated record notifications, the Slack Integration module must be properly configured with workspace connections, appropriate token types, and automation task settings. Slack Integration enables real-time delivery of structured record cards to Slack channels and direct messages, extending portal communication workflows into team collaboration environments where stakeholders already work.

Foundation Setup

Understanding Slack Integration Familiarize yourself with Slack Integration capabilities including workspace connections, dual token authorization (bot and user tokens), automated record card messaging, multi-language translation support, and integration with the Automations module. Understand how Slack messaging extends existing automation workflows by delivering formatted notifications to Slack channels and direct messages when automation criteria are met.

Verifying Slack Feature License Confirm that your portal has the Slack feature licensed and activated. Navigate to Setup > Extend > Slack to verify access. If Slack settings are not available or display a licensing error, contact your Customer Success Manager to discuss licensing options and edition requirements. Slack Integration cannot be enabled without the appropriate feature license.

Confirming Administrator Access Verify that users who will configure Slack Integration have Administrator System Role permissions with access to Setup > Extend > Slack. Only administrators can enable Slack Integration, authorize workspace connections, manage existing connections, and configure Slack Message tasks within automations. Standard users, partner users, and customer portal users cannot access Slack configuration settings.

Identifying Slack Workspace Administrators Determine which team members have administrator privileges or app installation permissions in your organization's Slack workspaces. Workspace authorization requires someone with sufficient Slack permissions to approve app installations during the OAuth flow. Coordinate with Slack workspace administrators before beginning the connection process.

Enabling Slack Integration

Accessing Slack Settings Navigate to Setup > Extend > Slack to access the Slack Integration configuration page. This page contains the global enable toggle, connection status indicator, and Connected Workspaces management area. Bookmark this location for ongoing Slack Integration administration.

Enabling the Integration Toggle the Enable switch to ON to activate Slack Integration for your portal. When enabled, the status indicator displays "Connected" and the Connected Workspaces section becomes available for workspace authorization. Enabling Slack Integration prepares the portal to establish workspace connections but does not automatically connect any workspaces.

Connecting Slack Workspaces

Choosing a Connection App Type Decide whether to use the Magentrix Slack App or a Custom Slack App for your workspace connections. The Magentrix Slack App provides quick setup with no custom configuration required and is recommended for most organizations. Custom Slack Apps are appropriate when organizational policies require ownership of all connected applications or when custom branding is essential. For Custom Slack App setup, see Creating a Custom Slack App.

Authorizing Workspace Connections Click the Connect Workspace button to begin the authorization process. Select your preferred app type (Magentrix Slack App or Custom Slack App) and click Authorize. Complete the Slack OAuth flow by entering your workspace URL, signing in if required, reviewing the requested permissions, and clicking Allow. Upon successful authorization, the workspace appears in the Connected Workspaces table with both bot and user token connections created automatically.

Understanding the OAuth Consent Screen Review the permissions requested during authorization. The consent screen displays all scopes the Magentrix app requires, organized into information the app can view (channels, users, workspace details) and actions the app can take (sending messages, performing actions in channels). For the Magentrix Slack App, a notice stating "App is not approved by Slack" appears because the app is not listed in the public Slack Marketplace. This is standard for privately distributed applications and does not affect functionality.

Verifying Connection Creation After authorization completes, verify that the workspace appears in the Connected Workspaces table. Confirm that both bot and user token connections were created by checking the Token Type column. Verify the Active checkbox is selected for both connections, indicating they are ready for use in automation tasks.

Connecting Additional Workspaces Repeat the authorization process for each Slack workspace that should receive automated notifications from Magentrix. Organizations with multiple workspaces for different teams, regions, or business units can connect all relevant workspaces to a single portal. Each workspace maintains independent connection credentials and can be managed separately.

Understanding Token Types

Understanding Bot Token Capabilities Recognize that bot token connections enable posting messages to Slack channels where the bot is a member. Bot tokens are ideal for channel-based notifications where messages should appear as coming from the application rather than an individual user. Bot tokens cannot send direct messages to human users due to Slack platform limitations.

Understanding User Token Capabilities Recognize that user token connections enable sending direct messages to individual Slack users or Slack channels. User tokens are essential for automation scenarios requiring private notifications to specific individuals. Messages sent via user tokens appear as coming from the platform user who authorized the connection.

Planning Token Usage Determine which automation scenarios require channel messages (use bot tokens) versus direct messages (use user tokens). Plan automation task configurations accordingly, ensuring the appropriate connection type is selected for each Slack Message task based on the intended delivery method.

Preparing for Automation Tasks

Identifying Target Channels Determine which Slack channels should receive automated record notifications. Document channel names, purposes, and intended notification types. Identify whether target channels are public or private, as private channels require explicit bot invitation before messages can be delivered.

Inviting Bot to Private Channels For each private channel that should receive automated messages, invite the Magentrix bot as a channel member. Open the private channel in Slack, access channel settings, and add the bot to the channel membership. Verify the bot appears in the member list before configuring automation tasks targeting that channel.

Identifying Direct Message Recipients For automations requiring direct message delivery, identify which Slack users should receive notifications. Verify these users exist in the connected Slack workspace and have not been deactivated. Plan which user token connection will be used for direct message tasks.

Planning Field Selections Determine which record fields should display in Slack messages for each automation scenario. Plan up to 10 fields for record creation notifications (showing current values) and up to 10 fields for record update notifications (showing changed values with previous and new comparisons). Prioritize fields that help recipients understand record importance and determine required actions.

Preparing Custom Labels If supporting multiple languages, create custom labels for record card headings, descriptions, and button text. Translate custom labels into all active portal languages to ensure recipients receive appropriately localized notifications. Use the {!$Label.LabelName} syntax in Slack Message task configurations to reference custom labels.

Configuring Slack Message Tasks

Understanding Supported Entities Confirm that automations requiring Slack Message tasks are created on supported entities: Lead, Opportunity, Case, Account, or Contact (including CRM-integrated variants such as Force__Lead or DynamicsCrm__opportunity). Slack Message tasks cannot be created for other entities including User Journey, User, or custom entities.

Creating Slack Message Tasks Add Slack Message tasks to automations by navigating to Setup > Create > Automations, selecting the target automation, clicking New in the Automation Tasks section, and selecting Slack Task. Configure task properties including name, sequence, Slack connection, message type (channel or direct message), target channel or user, record heading, optional description, create fields, update fields, and button label.

Configuring Record Card Content Define how record information appears in Slack notifications by configuring Record Heading (required, maximum 80 characters), Record Description (optional, maximum 255 characters with merge field support), Record Card Create Fields (up to 10 fields for new record notifications), Record Card Update Fields (up to 10 fields for changed value notifications), and Record Button Label (required, maximum 75 characters).

Setting Task Sequence Position Slack Message tasks appropriately within automation workflows by setting sequence numbers. Slack Message tasks typically execute late in sequences (after field updates, security role changes, and other data modifications complete) to ensure messages contain accurate information reflecting the final workflow state. Use sequence increments of 10 to allow easy insertion of additional tasks.

Testing and Validation

Testing Channel Message Delivery Create or update test records that trigger automations with Slack Message tasks configured for channel delivery. Verify messages appear in the target Slack channel with correct heading, description, field values, and button functionality. Confirm the button opens the correct record in Magentrix when clicked.

Testing Direct Message Delivery Create or update test records that trigger automations with Slack Message tasks configured for direct message delivery using user token connections. Verify messages appear as private direct messages to the intended recipient with correct formatting and content.

Validating Multi-Language Translation If supporting multiple languages, test message delivery to workspaces or connections with different language settings. Verify field labels, picklist values, custom labels, and system text translate correctly based on workspace language (for channel messages) or connection owner language preference (for direct messages).

Verifying Update Field Behavior Test record update scenarios to confirm that only fields whose values actually changed appear in Slack notifications. Verify previous and new values display correctly for changed fields. Confirm fields that did not change are omitted from update notifications.

Testing Private Channel Delivery If automations target private channels, verify the bot was successfully invited and messages deliver correctly. Confirm bot membership before activating automations to prevent silent delivery failures.

Connection Management

Monitoring Connection Status Regularly check the Connected Workspaces table to verify all connections remain active. Look for the Active checkbox to confirm connections are functional. Investigate any connections showing inactive status, as these cannot be used for automation message delivery.

Understanding Revocation Recognize that revoking a workspace connection immediately stops all Slack message delivery using that connection. Automation tasks referencing revoked connections will skip Slack message delivery without interrupting other automation tasks. Revoked connections remain visible in the table but cannot be used until reauthorized.

Managing Connection Lifecycle Plan for connection maintenance including periodic verification, reauthorization when needed, and cleanup of unused connections. Slack connection tokens may require reauthorization based on Slack platform policies. Check Slack documentation for current token expiration and refresh requirements.

Verifying Revocation in Slack When revoking connections in Magentrix, verify that the app access has also been revoked in the Slack workspace. Navigate to Slack workspace settings and review installed apps to confirm the connection status matches between both platforms.

Ongoing Maintenance

Periodic Connection Verification Establish a schedule for verifying Slack connection status, such as monthly or quarterly reviews. Check that all connections remain active and test message delivery periodically to confirm end-to-end functionality. Document connection ownership and reauthorization responsibilities.

Monitoring Message Delivery Periodically verify that automated messages appear in target Slack channels as expected. Review system logs if messages are not delivered. Note that failed Slack Message tasks currently do not generate administrator notifications; proactive monitoring is required to identify delivery issues.

Maintaining Bot Channel Membership When new private channels are created that should receive automated messages, remember to invite the bot before configuring automation tasks. Maintain documentation of which channels require bot membership for automation functionality.

Updating Custom Labels When adding new languages to the portal or modifying notification content, update custom labels used in Slack Message task configurations. Ensure translations exist for all active languages to maintain consistent multi-language support.

Reviewing Automation Effectiveness Periodically assess whether Slack notifications provide value to recipients. Gather feedback about notification frequency, content usefulness, and delivery timing. Adjust automation criteria, field selections, or target channels based on stakeholder input to optimize notification effectiveness.

Disabling Slack Integration

Understanding Disable Impact Recognize that disabling Slack Integration immediately stops all Slack message delivery across all automations. The Connected Workspaces list becomes hidden, all Slack automation tasks stop executing, and the Slack Task option becomes unavailable for new automation task creation. Existing automation configurations are preserved but inactive.

Disabling the Integration If Slack Integration is no longer needed, toggle the Enable switch to OFF in Setup > Extend > Slack. Confirm the action when prompted. The status indicator changes to "Disconnected" and all Slack messaging functionality becomes inactive until the integration is re-enabled.

<< About Slack Integration | Configuring Slack Settings >>