About Slack Integration

The Slack Integration module enables administrators to connect Magentrix portals with Slack workspaces, allowing automated delivery of structured record notifications directly into Slack channels and direct messages. This integration extends portal communication capabilities beyond email and in-app notifications by leveraging Slack's real-time messaging platform where teams already collaborate, ensuring critical business events reach stakeholders immediately without requiring manual cross-platform updates.

Slack Integration transforms how organizations communicate about record changes by automatically posting formatted record cards to Slack when automation criteria are met. Whether notifying sales teams about new high-value opportunities, alerting support managers to escalated cases, or informing channel managers about partner deal registrations, the integration ensures relevant stakeholders receive timely, actionable information in their preferred collaboration environment.

Core Functionality

Workspace Connections

Slack Integration supports connecting one or more Slack workspaces to a single Magentrix portal. Each workspace connection establishes the authorization required for Magentrix to send messages to that workspace's channels and users.

Multiple Workspace Support: Organizations with separate Slack workspaces for different teams, regions, or business units can connect all relevant workspaces to a single portal. Each workspace maintains its own connection credentials and can be managed independently.

Dual Token Authorization: When authorizing a workspace, Magentrix automatically creates both a bot token and a user token for the connection. Use Appropriate Token Types: Select bot token connections for channel messages and user token connections for direct messages to individual users. This dual-token approach provides flexibility for different messaging scenarios within the same workspace.

Connection App Options: Administrators can connect workspaces using the Magentrix Slack App, a pre-configured multi-tenant application that requires no custom setup, or a Custom Slack App for organizations requiring full control over app branding, permissions, and security policies.

Automated Slack Messaging

The primary purpose of Slack Integration is enabling Slack Message tasks within the Automations module. These tasks automatically post structured record cards to Slack when automation criteria are met, eliminating manual notification processes and ensuring consistent, timely communication.

Record Card Format: Unlike free-form text messages, Slack Message tasks send professionally formatted record cards that include a bold heading, optional description, selected field values with labels, and a clickable button linking directly to the record in Magentrix. This structured format ensures recipients receive consistent, scannable information.

Creation and Update Notifications: Slack Message tasks can notify stakeholders when records are created (displaying selected field values) or when records are updated (displaying only changed fields with both previous and new values). This targeted approach helps recipients quickly understand what happened and why they are being notified.

Channel and Direct Message Delivery: Messages can be posted to Slack channels for team-wide visibility or sent as direct messages to specific users for private notifications. Channel messages are visible to all channel members, while direct messages reach only the intended recipient.

Supported Entities

Slack Message tasks are available for automations created on the following entities:

• Lead: Lead, Force__Lead, DynamicsCrm__lead
• Opportunity: Opportunity, Force__Opportunity, DynamicsCrm__opportunity
• Case: Case, Force__Case, DynamicsCrm__case
• Account: Account, Force__Account, DynamicsCrm__account
• Contact: Contact, Force__Contact, DynamicsCrm__contact

This entity restriction ensures structured record card formatting works correctly with entity field configurations. Slack Message tasks cannot be created for other entities including User Journey, User, custom entities, or any entities not listed above.

Token Types and Capabilities

Understanding the difference between bot tokens and user tokens is essential for configuring Slack Integration effectively. Each token type has distinct capabilities and limitations that affect how messages can be delivered.

Bot Tokens

Bot tokens represent the Slack app itself rather than an individual user. When messages are sent using a bot token, they appear in Slack as coming from the bot with the app's configured name and icon.

Channel Messaging: Bot tokens excel at posting messages to Slack channels. The bot can post to any public channel and to private channels where the bot has been explicitly invited as a member.

Direct Message Limitation: Bot tokens cannot send direct messages to human users. When using a bot token connection, direct messages can only be sent to the bot itself. This is a permanent Slack platform limitation, not a Magentrix restriction.

User Tokens

User tokens represent the individual Magentrix user who authorized the Slack connection. When messages are sent using a user token, they appear in Slack as coming from that user.

Direct Message Capability: User tokens can send direct messages to any user in the Slack workspace, making them essential for automation scenarios requiring private notifications to specific individuals.

Channel Messaging: User tokens can also post to channels where the authorizing user has access, though bot tokens are typically preferred for channel messaging to maintain clear distinction between automated messages and personal communications.

Multi-Language Support

Slack Integration automatically translates message content based on recipient language preferences, ensuring stakeholders receive notifications in their appropriate language.

Channel Message Translation

For messages posted to Slack channels, the system automatically detects the workspace language via the Slack API and translates all message content accordingly. Field labels, picklist values, custom labels used in headings and descriptions, and system text such as "New" and "Previous" all translate to match the workspace language setting.

Direct Message Translation

For direct messages, the system uses the Magentrix language preference of the user who owns the Slack connection. All message content translates to match the connection owner's language setting, ensuring consistent language presentation.

Supported Languages

Slack messages will display in the target language when both Magentrix and Slack support that language. The following languages are supported for Slack message translation:

• English (en)
• French (fr)
• German (de)
• Italian (it)
• Japanese (ja)
• Portuguese (pt)
• Spanish (es)
• Chinese (zh)

Russian (ru) is supported in Magentrix but not in Slack. If the target language is not supported by Slack or is not an active language in Magentrix, messages fall back to English to ensure successful delivery.

Connection App Options

Magentrix provides two approaches for connecting Slack workspaces, each suited to different organizational requirements.

Magentrix Slack App

The Magentrix Slack App is a pre-configured, multi-tenant application managed by Magentrix. This option provides the fastest path to Slack Integration with no custom configuration required.

Quick Setup: Administrators simply click Authorize, select the target workspace, and approve the requested permissions. The connection is established immediately without creating or configuring any custom applications.

Managed Updates: Magentrix maintains the shared application, ensuring compatibility with Slack platform changes and security requirements without administrator intervention.

"App is not approved by Slack" Notice: During authorization, Slack displays a notice that the app is not approved by Slack. This message appears because the Magentrix Slack App is not listed in the public Slack Marketplace. This is standard for privately distributed and multi-tenant applications and does not affect functionality. The app operates fully within Slack's security and permission framework.

Custom Slack App

Organizations requiring full control over their Slack app can create and connect a custom application. This approach is appropriate when organizational policies require ownership of all connected applications or when custom branding is essential.

Full Control: The organization owns the Slack app, controls its branding and icon, manages permission scopes, and maintains complete governance over the application lifecycle.

Additional Setup Required: Custom Slack Apps require creating an application in Slack's developer portal, configuring OAuth credentials, registering the app as a Connected App in Magentrix, and then authorizing the workspace connection.

Integration with Automations

Slack Integration extends the Automations module by adding Slack Message as an available task type. This integration enables event-driven Slack notifications that trigger automatically when records meet specified criteria.

Automation Workflow Integration

Slack Message tasks function as steps within broader automation workflows. They can execute alongside other task types including email alerts, field updates, security role changes, and feed messages. Task sequencing ensures Slack messages send at the appropriate point in the workflow, typically after all data updates complete so messages contain accurate, final information.

Event-Driven Messaging

Slack notifications trigger based on automation criteria and evaluation settings. Administrators can configure notifications for record creation events, specific field value changes, status transitions, or any combination of conditions supported by the Automations module. This event-driven approach ensures stakeholders receive notifications only when meaningful business events occur.

Record Card Configuration

Each Slack Message task defines how record information appears in the Slack notification. Administrators select which fields display for creation events (up to 10 fields showing current values) and which fields display for update events (up to 10 fields showing changed values with previous and new comparisons). Custom labels can be used for headings, descriptions, and button text to support multi-language deployments.

Security and Access Control

Administrator-Only Configuration

Slack Integration configuration is restricted to administrators with access to Setup areas. Only administrators can enable or disable 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.

Channel Visibility Considerations

Messages posted to Slack channels are visible to all channel members regardless of their permissions in Magentrix. Record information that is restricted in the portal may be visible to Slack channel members who lack portal access to the underlying record. Administrators should carefully consider channel membership when configuring channel-based Slack notifications for records containing sensitive information.

Connection Ownership

Each Slack connection is associated with an owner, the Magentrix user who authorized the connection. For user token connections, the owner's identity and language preferences affect message delivery. Connection ownership is displayed in the Connected Workspaces table for administrative reference.

Prerequisites and Requirements

Before configuring Slack Integration, ensure the following requirements are met:

Slack Feature License: The portal must have the Slack feature licensed and activated. If Slack Integration is not available in your portal, contact your Customer Success Manager to discuss licensing options and edition requirements.

Administrator Access: Users configuring Slack Integration must have Administrator System Role permissions in Magentrix with access to Setup > Extend > Slack.

Slack Workspace Admin Access: Authorizing a workspace connection requires administrator privileges or app installation permissions in the target Slack workspace. The person completing the OAuth authorization flow must have sufficient Slack permissions to approve app installations.

Bot Channel Membership: For channel messages, the Slack bot must be a member of target channels. Public channels may allow the bot to join automatically, but private channels require explicit invitation by a channel administrator before messages can be delivered.

Common Use Cases

Sales Pipeline Notifications: Automatically notify sales teams when high-value opportunities are created or when deals advance to critical stages. Post record cards to sales channels showing opportunity amount, account name, close date, and stage transitions so the entire team maintains visibility into pipeline activity.

Support Escalation Alerts: Send direct messages to support managers when cases are escalated to high or critical priority. Private notifications ensure management awareness of urgent customer issues requiring immediate attention without broadcasting sensitive information to broader channels.

Lead Assignment Communications: Post notifications to team channels when new leads are assigned to sales representatives. Transparent lead distribution visibility enables peer collaboration and ensures no leads are overlooked during handoffs.

Partner Deal Registration Updates: Notify channel managers when partners submit deal registrations by posting record cards showing partner name, deal value, and customer information. Immediate visibility enables prompt review and approval, improving partner experience and deal velocity.

Account Status Changes: Alert account teams when important account attributes change, such as tier upgrades, contract renewals approaching, or risk status modifications. Timely notifications enable proactive account management and relationship preservation.

Best Practices Summary

Maintain Active Connections: Regularly verify that Slack connections remain active and have not been revoked. Revoked connections prevent message delivery without generating obvious errors. Check connection status in Setup > Extend > Slack periodically and reauthorize connections as needed.

Invite Bot to Private Channels: Before configuring automations targeting private channels, ensure the Slack bot is explicitly invited to those channels. Private channel messages will fail silently if the bot is not a member.

Use Appropriate Token Types: Select bot token connections for channel messages and user token connections for direct messages to individual users. Bot tokens cannot send direct messages to human users due to Slack platform limitations.

Consider Channel Visibility: Remember that channel messages are visible to all channel members regardless of Magentrix permissions. Use private channels or direct messages for sensitive record information that should not be broadly visible.

Leverage Custom Labels: Use custom labels for headings, descriptions, and button text rather than plain text when supporting multiple languages. Custom labels automatically translate based on recipient language preferences.

Select Meaningful Fields: Choose record card fields that provide genuine value to recipients. Prioritize fields that help stakeholders understand record importance and determine whether immediate action is required.

Slack Integration Checklist >>