Creating Slack Message Tasks for Automations

Slack Message tasks automatically post structured record cards to Slack channels or send direct messages to Slack users when an Automation's criteria are met. This task type extends automated communication beyond the portal by delivering formatted record information directly into team collaboration channels where stakeholders already work. Slack Message tasks eliminate manual cross-platform updates and ensure critical business events trigger immediate Slack notifications with relevant record details.

Requirements

To create and configure Slack Message tasks for Automations, users must be assigned a Security Role with the following permissions:

Administrator System Role

Only administrators can access Automations, create Slack Message tasks, configure message content and delivery settings, and manage task configurations. Standard users, partner users, and customer portal users cannot configure Automation tasks.

Additional Requirements

• Slack Feature License: Your portal must have the Slack feature licensed and activated.
• Slack Integration Enabled: Slack integration must be enabled in Setup → Extend → Slack.
• Active Slack Connection: At least one Slack workspace must be connected and authorized with an active, non-revoked connection.
• Bot Channel Access: For channel messages, the Slack bot must be invited to target channels (especially private channels).
• Supported Entity: Automations must be created on supported entities (Lead, Opportunity, Case, Account, or Contact).

Supported Entities

Slack Message tasks are available only 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

Before You Begin

Before creating Slack Message tasks, ensure you have:

• Slack Integration Configured: Complete Slack Integration setup including workspace authorization, bot configuration, and connection testing. Verify integration is enabled and connections are active in Setup → Extend → Slack.
• Channel and User Access: Identify target Slack channels and verify the bot is a member. For private channels, explicitly invite the bot before configuring tasks. For direct messages, confirm recipient users exist in the Slack workspace.
• Field Selection Strategy: Plan which record fields should display in Slack messages for creation events (up to 10 fields) and update events (up to 10 fields showing changes).
• Custom Labels Prepared: If using custom labels for headings, descriptions, or button text, ensure labels are created and translated for all active portal languages.
• Multi-Language Considerations: Understand that Slack messages automatically translate based on workspace language or user language preferences.

Understanding Slack Record Cards

Unlike free-form text messages, Slack Message tasks send structured record cards that automatically format record information into professional Slack messages. Each record card includes:

• Heading: Bold title identifying the record or event
• Description: Optional contextual information about the record
• Field Display: Formatted list of selected fields with labels and values
• Action Button: Clickable link opening the record in Magentrix portal

Behavior Differences by Event Type:

Record Creation: Displays all selected "Create Fields" with their current values in a clean, formatted list.

Record Update: Displays only "Update Fields" whose values actually changed, showing both old and new values side-by-side for easy comparison.

This structured approach ensures consistent, professional Slack communications without requiring manual message formatting.

Creating Slack Message Tasks

Accessing the Task Creation Interface

1. Navigate to Setup → Create → Automations
2. Click the Automation (on a supported entity: Lead, Opportunity, Case, Account, or Contact) to which you want to add a Slack Message task
3. In the Automation Tasks section, click New
4. Select Slack Task from the task type options
5. Click Next

The Slack Message task configuration page displays three primary sections: Detail Information, Slack Information, and Slack Record Card Configuration.

Configuring Detail Information

The Detail Information section defines basic task properties and execution order within the Automation.

Automation (Read-Only)

Displays the parent Automation this task belongs to. This field is system-populated and cannot be modified. The link opens the Automation detail page.

Name (Required)

Enter a descriptive name for the Slack Message task that clearly identifies its purpose and target channel or recipient.

Examples of effective task names:

• "Post New Opportunity to Sales Channel"
• "Send Case Escalation to Support Manager"
• "Notify Account Team of Status Change"
• "Alert Partner Manager of Lead Assignment"

Clear task names help administrators understand Automation workflows when reviewing or troubleshooting multi-task sequences.

Sequence (Required)

Enter a numeric value defining when this task executes relative to other tasks in the Automation. Lower sequence numbers execute first.

Description (Optional)

Enter notes explaining the task's purpose, business justification, or special considerations. Use this field to document:

• Why Slack notifications are sent at this workflow stage
• What information stakeholders need from the record card
• Which team or channel should receive notifications
• Any dependencies on Slack Integration configuration or channel memberships

Comprehensive descriptions help future administrators maintain and troubleshoot Slack Message tasks.

Configuring Slack Information

The Slack Information section defines where the message will be delivered and which Slack connection will send it.

Slack Connection (Required)

Select the Slack workspace connection that will send the message. The dropdown displays all active (non-revoked) Slack connections showing:

• Connection Name: Identifier for the workspace connection
• Token Type: "bot" (bot token) or "user" (user token)
• App Type: "Magentrix" (shared app) or "Custom" (white-labeled app)
• Owner Name: For user tokens, shows the Magentrix user who owns the connection

The selected connection determines:

• Which Slack workspace will receive the message
• Which bot or user identity will post the message
• What channel access and permissions are available
• Language preferences for direct messages (uses connection owner's language)

Connection Management Actions:

• Add: Opens the Slack workspace connection page in a new tab where you can authorize additional workspaces
• Refresh: Reloads the connection dropdown to display newly created connections without leaving the task configuration page

Message Type (Required)

After selecting a Slack connection, the Message Type field appears. Select how the record card will be delivered:

Channel

Posts the record card to a specific Slack channel visible to all channel members.

When to Use:

• Broadcasting record updates to entire teams or departments
• Creating shared awareness of workflow events across multiple stakeholders
• Generating discussion opportunities about important records
• Logging visible audit trails for team visibility

Configuration Requirements:

• Select a Slack Channel from the dynamically loaded dropdown

Who Receives Notifications: All members of the specified Slack channel can view the message and receive Slack notifications according to their individual channel notification preferences.

Direct Message

Sends the record card as a private message directly to a specific Slack user visible only to that recipient.

When to Use:

• Sending confidential record information to individual stakeholders
• Providing private notifications about personal responsibilities or assignments
• Delivering sensitive updates that should not appear in public channels
• Alerting specific users without broadcasting to entire teams

Configuration Requirements:

• Select a Slack User from the dynamically loaded dropdown

Who Receives Notifications: Only the specified recipient receives the direct message and related Slack notifications.

Slack Channel (Required for "Channel" Message Type)

When "Channel" is selected as Message Type, the Slack Channel dropdown appears, displaying channels from the selected workspace:

• Channel Name: The channel name with # prefix
• Channel Type: Indicates whether the channel is public or private

The channel list is dynamically loaded based on the selected Slack connection, showing only channels where the bot or user has access.

Slack User (Required for "Direct Message" Message Type)

When "Direct Message" is selected as Message Type, the Slack User dropdown appears, displaying users from the selected workspace:

• User Display Name: The user's display name or real name in Slack

The user list is dynamically loaded based on the selected Slack connection.

Configuring Slack Record Card

The Slack Record Card Configuration section defines how record information is formatted and displayed in Slack messages. This structured approach ensures consistent, professional messaging without requiring manual text composition.

Record Heading (Required)

Enter the main title that appears at the top of the Slack message in bold formatting. The heading should clearly identify the record or event being communicated.

Field Details:

• Maximum Length: 80 characters
• Supports: Plain text and Custom Label references
• Format: Use {!$Label.LabelName} syntax to reference custom labels for multi-language support

Examples:

• Plain Text: New Opportunity Created
• Plain Text: Case Escalated to High Priority
• Custom Label: {!$Label.Slack_Opportunity_Title}
• Custom Label: {!$Label.New_Lead_Notification}

Record Description (Optional)

Enter additional context or detailed information about the record that appears below the heading. Descriptions can include static text, custom labels, and merge fields referencing record data.

Field Details:

• Maximum Length: 255 characters
• Supports: Plain text, Custom Label references, and merge fields
• Format: Use {!FieldName} syntax for merge fields and {!$Label.LabelName} for custom labels

Examples:

• Plain Text: This opportunity requires immediate follow-up
• With Merge Fields: Opportunity value: {!Amount} for account {!Account.Name}
• With Custom Label: {!$Label.High_Value_Opportunity_Alert}
• Combined: Case #{!CaseNumber} assigned to {!Owner.Name} - Priority: {!Priority}

Record Card Create Fields (Optional)

Select up to 10 entity fields that will display in the Slack message when new records are created. Selected fields appear in a formatted list showing field labels and current values.

Field Details:

• Maximum Selection: 10 fields
• Display Format: Field Label: Field Value
• Reordering: Use up/down arrow buttons to reorder selected fields
• Display Order: Fields appear in Slack messages in the order configured

Selection Strategy:

Choose fields that provide stakeholders with essential information about new records:

• Identification Fields: Record name, number, or unique identifiers
• Key Attributes: Amount, priority, status, type, category
• Relationship Fields: Account name, contact name, owner name
• Date Fields: Close date, due date, created date
• Context Fields: Source, campaign, region, product

Examples by Entity:

Opportunity: Amount, Close Date, Stage, Account Name, Type, Lead Source, Owner Name, Probability, Next Step, Description

Case: Case Number, Priority, Status, Subject, Account Name, Contact Name, Owner Name, Origin, Type, Description

Lead: Lead Name, Company, Email, Phone, Status, Lead Source, Owner Name, Rating, Industry, Annual Revenue

Record Card Update Fields (Optional)

Select up to 10 entity fields that will display in the Slack message when records are updated. Unlike Create Fields, Update Fields display only when their values actually change, showing both the previous and new values for easy comparison.

Field Details:

• Maximum Selection: 10 fields
• Display Format: Field Label: Previous Value → New Value
• Display Condition: Only fields whose values changed in the triggering update appear
• Reordering: Use up/down arrow buttons to reorder selected fields
• Display Order: Fields appear in Slack messages in the order configured (if they changed)

Selection Strategy:

Choose fields whose changes represent meaningful workflow events or state transitions:

• Status/Stage Fields: Workflow stage, case status, lead status, opportunity stage
• Assignment Fields: Owner, assigned user, responsible party
• Value Fields: Amount, priority, severity, probability
• Date Fields: Close date, due date, resolution date
• Approval Fields: Approval status, approval date, approver

Examples by Entity:

Opportunity: Stage, Amount, Close Date, Probability, Owner Name, Next Step, Approval Status, Forecast Category

Case: Status, Priority, Owner Name, Escalated (checkbox), Resolution Date, Customer Satisfaction, Severity

Lead: Status, Owner Name, Rating, Lead Source, Converted (checkbox), Conversion Date

Record Button Label (Required)

Enter the text that appears on the clickable button at the bottom of the Slack message. Clicking this button opens the record in the Magentrix portal.

Field Details:

• Maximum Length: 75 characters
• Supports: Plain text and Custom Label references
• Format: Use {!$Label.LabelName} syntax to reference custom labels for multi-language support

Examples:

• Plain Text: View Opportunity
• Plain Text: Open Case Record
• Plain Text: Review Lead Details
• Custom Label: {!$Label.Open_Record}
• Custom Label: {!$Label.View_Full_Details}

Saving the Slack Message Task

After configuring all settings:

1. Review all configuration for accuracy
2. Verify the Slack Connection is active and functional
3. Confirm Message Type and target (channel or user) are appropriate
4. Check that Record Heading and Button Label are clear and concise
5. Validate that selected Create Fields and Update Fields provide meaningful information
6. Ensure field character limits are respected (Heading 80 chars, Description 255 chars, Button 75 chars)
7. Click Save

The Slack Message task is added to the Automation's task list and will execute according to its sequence number when the Automation triggers.

If validation errors occur:

• Check that Name is provided
• Verify Sequence is a valid number
• Confirm a Slack Connection is selected
• Ensure Message Type is selected
• Verify Channel or User is selected based on Message Type
• Confirm Record Heading is provided and within 80 characters
• Check that Record Description (if provided) is within 255 characters
• Ensure Record Button Label is provided and within 75 characters
• Verify no more than 10 Create Fields are selected
• Verify no more than 10 Update Fields are selected

Understanding Slack Message Behavior

Task Execution

When the Automation criteria are met and the Slack Message task's sequence is reached:

1. The system validates Slack Integration is licensed and enabled
2. The system verifies the Slack Connection exists and is active (not revoked)
3. The system checks the target channel or user is valid and accessible
4. The record card is assembled with heading, description, and selected fields
5. Field labels and picklist values are translated based on recipient language preferences
6. The formatted message is sent to the Slack API for delivery
7. Slack delivers the record card to the target channel or user
8. Recipients receive Slack notifications according to their individual preferences

Slack message delivery occurs synchronously during Automation execution. Messages typically appear in Slack within seconds of the Automation triggering.

Message Content for New Records

When a record is created and the Automation triggers:

• The Record Heading appears as the message title
• The Record Description (if configured) appears below the heading
• All Record Card Create Fields display in the configured order
• Each field shows: Field Label: Current Value
• The Record Button appears at the bottom with configured label text
• Clicking the button opens the record in the Magentrix portal

Create messages provide stakeholders with complete snapshots of new records, enabling immediate understanding of record context and importance.

Message Content for Updated Records

When a record is updated and the Automation triggers:

• The Record Heading appears as the message title
• The Record Description (if configured) appears below the heading
• Only Record Card Update Fields whose values actually changed display
• Each changed field shows: Field Label: Previous Value → New Value
• Fields that did not change are omitted from the message
• The Record Button appears at the bottom with configured label text
• Clicking the button opens the record in the Magentrix portal

Update messages focus stakeholder attention on specific changes, making it easy to understand what triggered the notification and what action may be required.

Multi-Language Support and Translation

Slack Message tasks automatically translate content based on recipient language preferences:

Channel Messages

Translation for channel messages uses the workspace language:

• The system uses the workspace language for channel messages
• Field labels, picklist values, custom labels, and system text translate to match the workspace language
• If the workspace language is not an active language in Magentrix, the system falls back to English
• All channel members see the same translated content regardless of individual language preferences

Direct Messages

Translation for direct messages uses the Slack connection owner's language preference:

• The system uses the Magentrix language preference of the user who owns the Slack connection
• All content translates to match the connection owner's language setting
• Recipients see content in the connection owner's language, not their own Slack language preference

Translated Content

Automatic translation applies to:

• Field Labels: Entity field labels translate to recipient language
• Picklist Values: Single-select and multi-select picklist values translate
• Custom Labels: Labels used in headings, descriptions, and button text translate
• System Text: Words like "New," "Previous," and other system-generated text translate

Language Compatibility

Slack messages will display in the target language if both Magentrix and Slack support that language. If a language is active in Magentrix but not supported by Slack, the system falls back to English to ensure message delivery. Verify that critical Custom Label translations exist for all languages you intend to use for Slack notifications.

Notification Delivery

After record cards are posted to Slack:

Channel Messages:

• All channel members can view the record card in the channel feed
• Members receive Slack notifications according to their channel notification preferences (all messages, mentions only, or muted)
• Messages appear with the Slack bot's name and icon as the sender (or user name for user token connections)
• Messages persist in channel history according to workspace retention policies

Direct Messages:

• Only the recipient can view the private record card
• Recipients receive Slack notifications according to their direct message preferences
• Messages appear in the recipient's direct message list from the bot or user
• Messages are private and not visible to other workspace members

Failed Message Delivery

Slack message delivery may fail if:

• Slack Integration is disabled in the portal settings
• The Slack feature license has expired or been removed
• The Slack Connection is revoked or inactive
• The Slack bot is not a member of the target channel (especially private channels)
• The channel has been deleted or archived in Slack
• The recipient user does not exist or has been deactivated (for direct messages)
• The connection uses a bot token attempting to send direct messages to users
• Slack API is temporarily unavailable or experiencing issues
• Network connectivity issues prevent API communication
• Character limits are exceeded (Heading 80 chars, Description 255 chars, Button 75 chars)

Validation Before Execution

Before attempting to send messages, the system validates:

• License Check: Slack feature must be licensed on the portal
• Settings Check: Slack Integration must be enabled in Setup → Extend → Slack
• Connection Check: Selected Slack Connection must exist and be active (not revoked)
• Target Check: For direct messages, validates target user exists and is not deleted or deactivated
• Field Validation: Heading required and ≤80 chars, Description ≤255 chars, Button Label required and ≤75 chars

If validation fails, the task logs a warning and stops execution gracefully without interrupting other Automation tasks.

Common Use Cases

New Opportunity Notifications: When high-value opportunities are created (detected by Amount field criteria), post a record card to the #sales-team channel showing opportunity amount, account name, close date, stage, and owner. This provides immediate team visibility into significant pipeline additions without requiring manual communication.

Case Escalation Alerts: When support cases are escalated to High or Critical priority, send a direct message to the support manager showing case number, priority change (Previous → New), customer account, subject, and current owner. This ensures management awareness of urgent customer issues requiring immediate attention.

Lead Assignment Notifications: When new leads are assigned to sales representatives (detected by Owner field changes), post a record card to a team channel showing lead name, company, rating, source, and new owner. This creates transparency around lead distribution and enables peer collaboration on new prospects.

Deal Stage Progression: When opportunities advance to final stages like "Negotiation" or "Closed Won," post celebration messages to the #sales-wins channel showing opportunity name, amount, account, and stage transition. This recognizes sales achievements and motivates team performance.

Contract Renewal Reminders: When account renewal dates approach (detected by date-based criteria), send direct messages to account managers showing account name, renewal date, contract value, and current status. This ensures proactive renewal management without relying on manual calendar tracking.

Partner Deal Registration Notifications: When partners submit deal registrations (detected by Status change to "Submitted"), post a record card to the #channel-managers channel showing partner name, deal value, customer account, expected close date, and registration details. This provides immediate visibility to channel managers who can review and approve registrations promptly.

Deal Approval Direct Messages: When deal registrations are approved or rejected (detected by Approval Status field changes), send direct messages to the partner account owner showing the decision, approval date, approver name, and any approval comments. This provides private, immediate notification to partner-facing teams who can communicate decisions to partners appropriately.

Best Practices

Maintain Active Slack Integration

Regularly verify that Slack Integration remains enabled and connections stay active:

• Monitor Slack Connection status in Setup → Extend → Slack monthly
• Re-authorize connections before they expire (typically annually)
• Test message delivery periodically with sample Automation triggers
• Document connection ownership and renewal responsibilities
• Train backup administrators on Slack Integration maintenance

Active integration maintenance prevents silent failures where Automations trigger but messages never deliver.

Invite Bot to Private Channels

Before configuring Slack Message tasks targeting private channels:

• Identify all private channels that will receive automated messages
• Use Slack workspace admin privileges to invite the bot to each private channel
• Verify bot appears in channel member lists
• Test message delivery to private channels before activating Automations
• Document which channels require bot membership for future reference

Proactive bot invitation prevents message delivery failures that are difficult to diagnose.

Select Meaningful Fields

Choose Create Fields and Update Fields that provide genuine value to recipients:

• Prioritize fields that help recipients understand record importance and urgency
• Include context fields that explain why the record matters (account name, amount, priority)
• For Update Fields, select fields whose changes represent workflow events requiring awareness
• Avoid selecting excessive fields that create cluttered, hard-to-scan messages
• Test field selections with actual users to validate information usefulness
• Use consistent field selections across similar Automations for predictable formatting

Thoughtful field selection ensures Slack notifications provide actionable information rather than overwhelming recipients with data.

Use Custom Labels for Multi-Language Support

When your portal supports multiple languages or regions:

• Create Custom Labels for all user-facing text (headings, descriptions, button labels)
• Translate Custom Labels into all active portal languages
• Use {!$Label.LabelName} syntax rather than plain text in configurations
• Test message delivery with workspaces in different languages to verify translations
• Maintain Custom Label translations when adding new languages to the portal

Custom Label usage ensures stakeholders in different regions receive appropriately translated notifications, improving comprehension and engagement.

Consider Channel Membership and Visibility

Design channel targeting strategies considering who has access:

• Remember that channel messages are visible to all members regardless of portal permissions
• Use private channels for sensitive record information requiring restricted visibility
• Use direct messages for confidential information not appropriate for any channel
• Review channel membership lists before configuring Automations posting to channels
• Document channel purposes and membership criteria to guide Automation design
• Avoid posting sensitive data to broad team channels where it may be over-shared

Visibility awareness prevents inadvertent information exposure through Slack channels.

Test with Different Token Types

Understand limitations of bot tokens vs. user tokens:

• Use bot tokens for channel messages where bot identity is acceptable
• Use user tokens for direct messages to actual users (bot tokens can only message the bot itself)
• Test direct message delivery with the specific connection token type before activating Automations
• Consider creating both bot and user token connections for different use cases
• Document which connection types are appropriate for which Automation scenarios

Token type awareness prevents configuration errors causing direct message failures.

Balance Notification Frequency

Design Automation criteria to prevent excessive Slack notifications:

• Use "Created, and any time updated which previously did not meet the criteria" Evaluation Criteria to prevent repeated notifications for the same event
• Target specific workflow transitions rather than all record updates
• Consider whether every record change warrants Slack notification or only significant events
• Monitor channel activity to identify whether notification volumes are appropriate
• Solicit user feedback about notification usefulness and frequency
• Adjust Automation criteria if users report notification fatigue

Appropriate notification frequency maintains Slack channel value without overwhelming recipients.

Coordinate with Other Communication Tasks

When using Slack Message tasks alongside Email Alert or Feed/Message tasks:

• Avoid duplicating identical content across Slack and email
• Use Slack for immediate awareness and email for formal documentation
• Consider whether stakeholders monitor Slack actively enough to rely solely on Slack notifications
• Provide links to portal records in Slack messages so recipients can access full details
• Sequence tasks thoughtfully (Slack often last after all data updates complete)

Multi-channel communication strategies ensure comprehensive stakeholder awareness without creating redundant notifications.

Monitor Message Delivery

Regularly verify that Slack messages deliver successfully:

• Check Slack channels periodically to confirm automated messages appear
• Review system logs for Slack Message task warnings or errors
• Solicit user feedback about whether they receive expected notifications
• Test Automations after Slack Integration configuration changes
• Document known issues or limitations for administrator reference

Proactive monitoring identifies delivery problems before users report missing notifications.

Document Integration Dependencies

Use Description fields extensively to document:

• Which Slack Connection the task uses and why
• Target channel or user selection rationale
• Field selection strategy (why these fields were chosen)
• Dependencies on bot channel membership or connection authorization
• Expected message delivery patterns and notification timing
• Business owners or stakeholders who requested the integration

Comprehensive documentation helps administrators maintain Slack Message tasks when integration settings, channel structures, or business requirements change.

Troubleshooting

Slack Task Not Available When Creating Tasks

Symptom: The Slack Task option does not appear in the task type list when creating new Automation tasks.

Diagnosis:

• Verify Slack feature is licensed on the portal
• Check that Slack Integration is enabled in Setup → Extend → Slack
• Confirm the Automation is on a supported entity (Lead, Opportunity, Case, Account, Contact)
• Verify you have Administrator permissions to access Automations

Solution: License the Slack feature, enable Slack Integration, or select a supported entity for the Automation. Contact portal administrators if licensing or feature access issues persist.

No Slack Connections in Dropdown

Symptom: The Slack Connection dropdown is empty when configuring Slack Message tasks.

Diagnosis:

• Verify at least one Slack workspace is connected in Setup → Extend → Slack
• Check that existing connections are active (not revoked)
• Confirm connections were authorized successfully

Solution:

1. Navigate to Setup → Extend → Slack
2. Click "Authorize Workspace" to connect a Slack workspace
3. Complete the OAuth authorization flow
4. Return to the Slack Message task configuration
5. Click "Refresh" to reload the connection dropdown
6. Select the newly created connection

Messages Not Delivering to Slack

Symptom: Automations trigger successfully but messages do not appear in Slack channels or direct messages.

Diagnosis:

• Verify Slack Integration is enabled (not disabled) in portal settings
• Check that the Slack Connection is active (not revoked)
• Confirm the bot is a member of target channels (especially private channels)
• Verify channel names or user selections are correct and targets still exist
• Check system logs for Slack Message task warnings or errors

Solution:

• Enable Slack Integration if disabled
• Re-authorize revoked connections through Setup → Extend → Slack
• Invite bot to private channels using Slack workspace admin tools
• Update task configuration if channels or users have been deleted
• Verify character limits are respected (Heading 80, Description 255, Button 75)

Bot Token Cannot Send Direct Messages to Users

Symptom: Only the bot itself appears in the user dropdown when configuring direct messages, or direct messages fail to deliver to users.

Diagnosis: The selected Slack Connection uses a bot token, which can only send direct messages to the bot itself, not to human users.

Solution:

• Create a Slack Connection using a user token instead of a bot token
• Select the user token connection when configuring direct message tasks
• Alternatively, use Channel message type instead of Direct Message
• Post to private channels for restricted visibility rather than direct messages

Wrong Language in Messages

Symptom: Slack messages display in unexpected languages or do not translate as expected.

Diagnosis:

• For channel messages: Check the workspace language
• For direct messages: Check the Slack connection owner's Magentrix language preference
• Verify the target language is an active language in the Magentrix portal
• Confirm Custom Labels are translated into the target language
• Check whether the target language is supported by both Magentrix and Slack

Solution:

• Update workspace language in Slack workspace settings
• Update connection owner's language preference in Magentrix user settings
• Activate additional languages in Magentrix portal settings if needed
• Translate Custom Labels used in headings, descriptions, and button labels
• Test with workspaces in different languages to verify translation behavior
• If a language mismatch exists between Magentrix and Slack, messages will default to English

Messages Missing Expected Fields

Symptom: Slack messages do not display all expected fields, or update messages show no fields at all.

Diagnosis:

• For create messages: Verify Create Fields are selected in task configuration
• For update messages: Remember Update Fields only display when their values actually changed
• Check that field values are not null (null values may display as blank)

Solution:

• Review and update Create Fields and Update Fields selections in task configuration
• Test with records where Update Fields have actual value changes
• Verify Automation Evaluation Criteria trigger on meaningful updates ("Created, and any time updated which previously did not meet the criteria")
• Ensure up to 10 fields maximum are selected for each field type

Character Limit Errors

Symptom: Task configuration cannot be saved due to character limit validation errors.

Diagnosis: Record Heading, Record Description, or Record Button Label exceed maximum character limits.

Solution:

• Reduce Record Heading to 80 characters or fewer
• Reduce Record Description to 255 characters or fewer
• Reduce Record Button Label to 75 characters or fewer
• Consider using shorter Custom Labels if plain text exceeds limits
• Remove unnecessary words or merge field references to reduce length

Private Channel Messages Failing

Symptom: Messages post successfully to public channels but fail when targeting private channels.

Diagnosis: The Slack bot is not a member of the private channel.

Solution:

1. Open the private channel in Slack
2. Click channel name to view channel details
3. Click "Add people" or "Integrations"
4. Search for and add the Magentrix bot to the channel
5. Verify bot appears in the channel member list
6. Test message delivery again with sample Automation trigger

Integration Authorization Expired

Symptom: All Slack Message tasks suddenly fail across multiple Automations.

Diagnosis: The Slack Connection authorization has expired (typically occurs annually).

Solution:

1. Navigate to Setup → Extend → Slack
2. Identify connections with "Revoked" or inactive status
3. Delete the expired connection
4. Click "Authorize Workspace" to create a new connection
5. Complete the OAuth authorization flow
6. Update all Slack Message tasks to use the new connection
7. Test message delivery with sample Automation triggers

See Troubleshooting Automations documentation for additional problem resolution guidance.

Jump to Automations Checklist

<< Creating Change Security Role Tasks for Automations | Automations Best Practices and Recommendations >>