Send notification messages to Slack Flow Action
The Send notification message to Slack Flow Action can send a highly configurable message to static or dynamic Slack conversations. For a step by step guide on authoring a Salesforce Flow utilizing this Flow Action see Sending Centro Slack messages from Salesforce using Flow or Process Builder.
Post to Slack Channel
To send to a static channel, select a public, private or DM conversation using the picker. If the conversation is private, you must add the Centro app to the conversation. To send to a dynamic channel you must first have the channel ID in a flow resource variable. See Using Flow Resources with Centro Slack Action Element for more details. Enable "Use variable" and then select the local flow resource variable that is set to the desired channel ID.
Post a custom message
The message text may utilize Slack Mrkdwn for rich text formatting, URL links, user mentions and more. Refer to Slack Mrkdwn documentation for more info. Variables may also be inserted from Flow Resources by inserting using the "Insert local resource" drop down or by properly formatting the merge tag within the message text.
Pin to channel
Pin message for easy reference. Pinned messages are a great way to highlight existing messages in a conversation. All members of a conversation can access pinned messages in the conversation header.
Send as reply
Start a thread or reply in a thread to an existing message. The existing message TS identifier is required. The TS value is available from Centro Custom Buttons, Workflow Webhook Triggers, and from messages previously sent by Centro using the Message Queue Custom Object in Salesforce.
Send as ephemeral
A message may be sent ephemerally so that it is only visible to a specified user. The Slack User ID must be contained in a Flow variable and be specified when Send as Ephemeral message setting is enabled. Slack User ID's may be looked up for any Salesforce User that is connected to Centro using the User.Centro__Slack_UserId__c field. See Associating Slack Members to Salesforce Records.
Attach a Salesforce Record
Post record details
Also known as Centro Record Blocks, the record details displays a list of record fields based on the Salesforce Compact Layout by default. Record details also expose additional functionality to the user via buttons and overflow menu items. See Anatomy of Centro Record Blocks for more information and customization options.
Link record to channel
Link record to channel will pin the record details to the channel (if enabled) and associate the Slack Conversation with the Salesforce Record making it visible from the Centro Linked Conversations LWC. This enables users to view all Slack conversations associated with a Salesforce record at a glance. You may also differ the record details displayed from the record which is linked if desired.
Link message thread
Instead of linking the record to the entire Slack conversation the record will only be linked to replies (if any) to the message that is posted. When this is enabled only the message thread is visible in the Centro Linked Conversations LWC and the thread may me given a name that differs from the conversation name.
Attach a Salesforce File
A Salesforce File (ContentDocumentVersion) may be attached to the message and if supported show a preview of the file contents inline in the conversation (i.e. Image or PDF). The ContentDocumentVersion ID (starts with 068) must be stored in a Flow variable and be less than 4MB. The File will be uploaded to your Slack workspace and will count toward Slack storage limits.
Attach a Salesforce Report
A Salesforce Report may be run and attached as a PDF or Excel format. The Report ID must be stored in a Flow variable.
Report File Format
PDF is preferred if an inline preview of the report is desired. Excel format may be preferred if editing of report data is desired.
Filter By parameter
Reports may be filtered by a single parameter (typically a related record ID). The parameter value must be stored in a Flow variable and the parameter API name must be known. With Standard Objects the parameter API name is often intuitive (i.e. CONTACT_ID) but for custom relationships it may be cryptic. Contact Centro for support with Report parameters.
Please refer to Make actionable Notifications using Centro Custom Buttons for more information on custom button capabilities.