Contents:

• Overview
• Setting up the LeanData-Slack Integration
• Authorizing Slack in LeanData
• Salesforce Authorization Settings
• Adding LeanData to a Slack Channel
• Using the Send Action Notification Node
• Recipients
• Message
• Action Buttons
• Time-to-Action Tracking
• Advanced Settings
• Action Notification Experience In Slack
• Troubleshooting and Monitoring

 

Overview

Send interactive Slack notifications that let users take action on Salesforce records without leaving Slack. Responses sync back to Salesforce before the routed record continues through the graph. Use the Send Slack Action Notification node in FlowBuilder to embed custom action buttons in Slack messages so recipients can create new records or update any routed or matched record, directly from the notification.

This capability is available at the Platform level to all tiers, including Standard, Advanced, and Premium.

Features

• Custom Buttons in Slack Notifications: Prescribe necessary and prompt action for your reps with context. Define which actions a team member needs to complete, from creating a new record or updating an existing record in Salesforce.
• SLA Tracking: Set expiration times and auto-tracking completion for each action sent in a notification. Easily hold team members accountable to taking action in a timely manner.
• Suggested Inputs: Accelerate updates and keep Salesforce data accurate by suggesting values or enabling reps to provide their own values used to create or update records.
• Continued Processing: Automate next steps based on inputs or SLA compliance. Whether next steps are conditional on action taken, inputs provided, or timely action taken, continue to automate updates, merges, or even initiating engagement sequences. Seamlessly incorporate manual input as part of one entire process.

 

Setting up the LeanData-Slack Integration

In order to use the Slack integration you must be a joint customer of LeanData and Slack.

Authorizing Slack in LeanData

A Slack Administrator must complete the instructions outlined below. For details on the broader Slack integration tile and basic Slack alerts in FlowBuilder, see Routing - LeanData-Slack FlowBuilder Integration.

• To use Slack with LeanData, ensure the appropriate remote site setting is configured in Salesforce. For more information, LeanData Admin - Adding the LeanData Remote Site Setting.
• From the LeanData App, navigate to Integrations > Routing and click the Get Started button on the Slack tile.

• Specify the correct User Field to help LeanData map Salesforce User Emails to Slack User Emails and direct notifications to the appropriate recipients. LeanData identifies Slack Users with the corresponding Salesforce Users by matching email addresses across both platforms, using the User field you select here.
• To send Slack notifications to both public and private channels, check the Send Slack notifications to both public and private channels box and invite the App to private channels.
  • Note: If you do not invite the App to a private channel, that channel will not be selectable in FlowBuilder.

• Please note: You must be either the owner or an admin of the Slack workspace to authorize the Slack integration with LeanData. If you need to change a Slack member's role, refer to the Change a member's role article.

 

Salesforce Authorization Settings

When users take an action in Slack via Slack Action Notifications, the resulting action in Salesforce will be attributed as follows:

• Actions will be assigned to the Primary/Secondary user tokens configured in the Authorization Tab in Admin Settings unless the user has connected their Salesforce account.
• Actions taken by users who have connected their Salesforce accounts will be attributed directly to their Salesforce User instead of the token user.

Authorization Options

1. Optional Salesforce Authorization:
   • Slack users can act on Slack Action Notifications in Slack without connecting their Salesforce accounts.
   • Actions by users who do not connect their accounts will be attributed to the Primary/Secondary user tokens configured in the Authorization Tab in Admin Settings.
2. Required Salesforce Authorization:
   • Slack users must connect their Salesforce accounts to respond to Slack Action Notifications.
   • Users will be automatically prompted to connect their Salesforce account when first attempting to respond to a Slack Action Notification in Slack.

Invite Users to Connect their Salesforce Accounts

• Click the Copy Link button to copy an invitation link.
• Share this link with your users to prompt them to connect their Salesforce accounts.

 

Adding LeanData to a Slack Channel

In Slack:

• Navigate to the channel you wish to add LeanData to.
• Click into the Members of the Channel. Under the Integrations tab, click Add an App in the Apps section.

• Find LeanData in the list of Apps in your workspace and click Add.

 

Using the Send Action Notification Node

To send Slack Action Notifications from your FlowBuilder graphs, add the Send Action Notification node to your graph. From the Node Bar on the upper right, go to Integrations > Notifications > Slack > Send Action Notification, and drag the node onto your FlowBuilder graph.

Within the Send Action Notification Node, there are five main sections: Recipients, Message, Action Buttons, Expiration Time, and Advanced Settings.

 

Recipients

Here you will select the intended recipient of your Slack Action Notification. This will determine who will receive the Action Notification in Slack.

• Owner: You can select from either the New Owner whom LeanData assigned the record to in a prior node or the Previous Owner before any ownership changes. Please note that this refers to the last User field that LeanData updated in the graph, not necessarily the default Owner field.
• Slack Channel: Will allow you to select a Slack channel in the connected Slack workspace. All public channels will be available, along with any private channels to which the LeanData App has been added.
• Slack User: Will allow you to select a recipient from a list of your Slack Users.
• Variable in Field: This option will allow you to select a User from other fields, including any Users on the routed record, related record, prior matched records, or any other Variables that have been defined in a previous node in the graph.

 

Message

Once you have selected your recipient, you can craft the content of the Slack message itself.

By using the dropdowns, you can insert mentions of Users and Channels, such as the New Owner, as well as insert Variables such as the record's name, a link to the record, or a link to the corresponding LeanData Audit Log.

 

Action Buttons

The Action Buttons section allows you to configure the actions you wish to incorporate within your Slack notification. By clicking the Add Action button, you can select from two options: Create Record and/or Update Record.

Clicking the Add Action button again will allow you to add more Action buttons to your Slack notification. You may add up to 5 Actions.

• Create Record: this option will give your Slack recipients a button to create a record in Salesforce, directly from Slack.

• • What kind of record do you want to create?: Select from a list of your Salesforce objects to indicate what kind of record you want your Slack recipient to be able to create.
  • What text do you want on the action button?: Enter the text you want to appear on the Action button that will appear in the Slack notification.
  • Which Salesforce fields do you want to populate on this record?: Click Add Field to add a field you wish to populate on the newly created record. You can select any editable field on the Salesforce object you selected in the previous step. You can either enter a static value for this field, or you can dynamically insert values from any previously stored Variable by using the Insert button. For date fields, you can either enter a static date or insert a Relative Date (relative to today).
    • Toggling the Editable switch on will give the recipient the ability to edit the value before they take the associated action.
  • After you configure your field, you can add more fields by clicking Add Field.

• Update Record: this option will give your Slack recipients a button to update a record in Salesforce, directly from Slack.

• • Which record do you want to update?: Select either the routed record or a related record, matched record, or other record stored in a Variable earlier in the graph.
  • What text do you want on the action button?: Enter the text you want to appear on the Action button that will appear in the Slack notification.
  • Which Salesforce fields do you want to update on this record?: Click Add Field to add a field you wish to update on the newly created record. You can select any editable field on the Salesforce object you selected in the previous step. You can either enter a static value for this field, or you can dynamically insert values from any previously stored Variable by using the Insert button. For date fields, you can either enter a static date or insert a Relative Date (relative to today).
    • Toggling the Editable switch on will give the recipient the ability to edit the value before they take the associated action.
  • After you configure your field, you can add more fields by clicking Add Field.

 

Time-to-Action Tracking

Time-to-Action Tracker User

Select which user will be tracked in the Time to Action Tracker. If you enable the "Evaluate while User is Working" setting, LeanData will use this user's schedule to determine working hours.

Expiration Time

Under the Expiration Time section, define a time frame using the dropdowns. LeanData will follow the Time Expired edge if the selected time elapses and none of the previously defined Actions have been taken by the Slack recipient. Currently, the default is 5 minutes with a max of 180 days as the longest time frame.

If one of the previously defined Actions is taken within the allotted time frame, the record will exit through the SLA Met edge.

If the Evaluate while User is Working box is checked, the specified expiration time will only elapse while the Time-to-Action Tracker User is working.

Records that enter the Send Action Node will automatically be tracked in the Time-to-Action Tracker Object. For more information on Time-to-Action Reporting, please see the Time-to-Action Reporting Guide.

 

Advanced Settings

A record will exit this node either when the recipient of the Slack Action Notification takes one of the Actions defined above or when the designated expiration time elapses, whichever happens first.

• Action Completed: Records will follow this edge if a rep takes one of the actions defined in the Slack Actions within the designated time frame. If you do not wish for any further processing or actions to take place, set this edge to End of Flow.
  • When a record proceeds through this edge, the original Slack Action notification will be modified to remove the Action button and will indicate that the SLA has been met.
• Time Expired: Records will follow this edge if the designated time frame elapses without a User taking one of the designated Slack actions above. You can assign the record to a different rep, send out a notification, or you can set this to End of Flow if you do not want any further action.
  • When a record proceeds through this edge, the original Slack Action notification will be modified to remove the Action button and will indicate that the time expired.

 

Action Notification Experience In Slack

The Action Notification sent in Slack will contain the message and Action Buttons as you configured it in the Send Action Notification Node.

When the recipient clicks one of the buttons, they will be taken to an interface to complete the fields you had specified within the node. Fields that you marked as editable can be updated by the Slack recipient. Fields that you did not mark as editable will display the value that you defined.

If the Slack recipient completes one of the actions within the timeframe, the buttons in the Slack Notification will be replaced with an Action Completed indicator, and the record will follow the Action Completed edge from the Action Notification Node.

If the Slack recipient does not complete one of the actions within the timeframe, the buttons in the Slack Notification will be replaced with a Time Expired indicator, and the record will follow the Time Expired edge from the Action Notification Node.

 

Troubleshooting and Monitoring

In addition to the reporting available in the Time-to-Action Tracker, LeanData will allow you to track records that are either pending or completed via a Send Action Notification node in Routing Insights and Audit Logs.

Routing Insights

Records that have not met specified rules and are currently waiting for expiration will be indicated by an orange counter on the Slack Action Notification node itself. This will detail how many records are still waiting to be qualified or expired via that node.

LeanData will always attempt to use the newest deployment as long as node names do not change. If node names change, LeanData will abort the hold.

Abort Reasons

In the case that any of the following occurs, LeanData will abort the hold on these records and mark the record status as “Aborted” in the Time-to-Action Tracker with an Abort Reason populated.

• Lead Converted
• Record Deleted or Merged
• Hold Until Conflict
• Incompatible Graph Deployment
  • Node name changes or conditions are incompatible
• Manual Abort by a User
• Business Unit Changed
  • Only applicable for Multi-Graph customers

 

Audit Logs

The Send Action Notification Node will create two audit logs. A parent log will be created when the initial notification is sent, and a child log will be created when the record exits the node via either edge and is completed.

Within the Audit Logs page, records that are still pending due to a Send Action Notification Node will display as a Parent Log with a Pending status in the Path Column.

When the time frame expires or when the record is actioned, another log will be generated as the child log, showing the routing outcome and detailing the path from the Send Action Notification Node onward. If you expand the More Info section, you will see a link to the Parent Log that triggered the initial routing process.

 

For questions or additional assistance please contact LeanData Support.