Contents:

• Overview
• Setting up LeanData-Slack Integration
• Authorizing Slack in LeanData
• Utilizing Slack Notifications in Flowbuilder
• Monitoring
• Appendix

 

Overview

Customers who utilize both LeanData and Slack can initiate Slack actions within LeanData’s FlowBuilder interface. Enabling Slack takes approximately 5-10 minutes to complete.

 

Features

• Send Slack notifications from LeanData FlowBuilder to one or multiple Slack users, Slack channels, record owners, matched object owners, or additional recipients
• Utilize and tag routed or matched object fields, Slack User(s), Slack Channel(s), and the record owners

 

Setting up LeanData-Slack Integration

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

 

Compatibility

Ensure that your Slack-Salesforce sync (if enabled) does not conflict with the LeanData-Slack integration. Here are the steps to configure Salesforce for Slack usage. 
 

 

Authorizing Slack in LeanData

• A Slack Administrator must complete the instructions outlined below:

  • First, ensure the appropriate remote site setting is configured in Salesforce to use LeanData Integrations. For more information, see LeanData Admin - Adding the LeanData Remote Site Setting.
  • In order to Authorize LeanData for use with Slack, the User who authorizes must:
    • Have the LeanData Custom Objects Full Access Permission Set in Salesforce
    • Be an administrator in their Slack workspace.
  • From the LeanData App, navigate to Integrations > Routing tab 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 to direct notifications to the right recipients. LeanData will identify Slack Users with the corresponding Salesforce Users by matching email addresses across orgs, by referencing the User field you select here.
  • To send Slack notifications to public and private channels, check the Send Slack notifications to both public and private channels box located to the right and invite the App to the private channels. If you do not invite the App, the private Channel will not be selectable in FlowBuilder.
  
  • Click Authorize and sign in with your Slack credentials. Ensure you have selected your desired Slack workspace via the dropdown menu on the top right of the screen, then click Allow.

  

   

  Please Note: LeanData can only be authorized for one workspace at any given time. If you have multiple workspaces, please ensure that the LeanData is authorized for a workspace that contains all of your relevant Users.

   

 

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.

 

Slack User

LeanData will map the Slack User to the corresponding Salesforce User by matching Email Addresses across orgs, by referencing the User field you selected for your mapping during the Authorization process.

 

Utilizing Slack Notifications in FlowBuilder

To use Slack in your FlowBuilder Graphs (Lead, Contact, Opportunity, Account, or Case) you must add the nodes to your Graphs. You can add an Send Notification Action from the Integrations > Notifications > Slack section in the FlowBuilder interface.

 

Within the Slack Send Notification node, you can configure your intended Recipients, and compose your Message.
.             

• Recipients: The New Owner, Previous Owner, Slack Users, and Slack Channel(s) will always be available as recipients. If you do not see the desired Slack User or Channel in the dropdown, you can hit the refresh icon to the right of the dropdown to pull the latest Users and channels from Slack. You can also select the slack channel which is associated with your record. The additional recipients of the Notification are dependent on the nodes in the path to the Send Notification node.
  • For example, if there is a Lead to Account Match node and a Create Opportunity node in the path of the Send Notification node, the recipients will include: Routed Lead, Matched Object, and Created Object User fields.
  • In addition to sending a Slack Notification to an individual user or a Slack Channel, you can also send a notification to a group of Slack users by selecting that option under Notification Delivery Method.
• Message: This is the configurable message that will be sent to the recipients designated on the bottom half of the node configuration.
• Mention Users and Channels: Using this dropdown, you can insert user mentions or channel callouts, including @here and @channel, individual Slack Users, and the previous and new owner of the routed record.
• Insert Variables: The routed object fields will always be available for insertion into the Message. The additional fields available for insertion depend on which nodes have been used in the path to the Send Notification node.
  • For example, if there is a Lead to Account Match node and a Create Opportunity node in the path of the Send Notification node, the Message fields for insertion will include: Routed Lead, Matched Object, and Created Object fields.

 

Advanced Settings

• After the Send Notification node, you can take another action on this lead by specifying a target for the Next Node edge under Advanced Settings. If you don’t want to take an action after the Send Notification node, simply select END OF FLOW
• Users also have the ability to choose the next node LeanData should move onto in the case of the following error:
  • Configuration Error: the authorization with Slack has been revoked in LeanData (note: LeanData does not follow this edge if the authorization is revoked in Slack)

 

Slack Notification Behavior after Specific FlowBuilder Actions

• Assign Owner (with Alternate User field option) + Slack “Send Notification” Behavior: When the Alternate User field option is selected on the Assign Owner node and followed by a Slack “Send Notification” node where “New Owner” is selected as a tag or recipient, LeanData sends the notification to the user in the selected Alternate User field.
• Convert Lead + Slack “Send Notification” Behavior: When a Lead is successfully converted to a Contact (after entering the graph and prior to the callout), LeanData will send the notification with the designated tags / to the recipients.
• “Merge Dupe” + Slack “Send Notification” Behavior: LeanData will not send a Slack notification if a “Merge Dupe” node is prior to the Slack node.  This is because of timing - for example, LeanData can make the call to Slack before merging into master is complete.
• Inactive User in Salesforce, Active User in Slack Behavior: If a User is inactive in Salesforce but active in Slack, LeanData still sends the message to the Slack User.

 

Monitoring

Audit Logs

Slack actions are tracked in the LeanData Audit Logs.

 

 

Error: If LeanData cannot perform the requested action in Slack, an error message will appear in the Audit Logs and be marked with a large Error block. 

 

Please Note: if you receive errors about missing scopes, please re-authorize Slack using the steps outlined in Authorizing Slack in LeanData above.

 

Routing Insights

Slack Actions will also be captured on the Routing Insights page in Router. Routing → Leads (or other object) → Routing Insights

 

If there are any configuration errors, such as the Authorization between LeanData and Slack getting disabled, errors will also be displayed here. You can click into the number next to the error type to see which records were affected by the error.

 

 

LeanData Partner Logs Report 

Visit Reports > LeanData Reports > LeanData Partner Logs Report to view a summary of all callouts.
 

• Action Type: the type of Partner node used (Slack - Send Notification for this integration)
• Node Name: the customizable name on the Slack node
• Response Status Code: indicates callout status
  • 200: Callout succeeded
  • 0, 300, 400: Callout failed
  • Blank: Pending
• Target Object: the object acted upon
• Callout History: displays all responses from the callouts (includes success and failures)
• Callout Duration in milliseconds: Callout end time - Callout start time
• Total Callout Duration in milliseconds: the entire length of time it took to process the request
• Failure Reasons: Reasons the callout failed
  • Token is not valid
  • Partner not authorized
  • Object has been deleted
  • Object has been merged
  • Retry attempt exceeded
  • Log length hit

Notes: Slack limits message posts via API to 4000 characters.  LeanData will restrict all messages to 4000 characters to adhere to this limitation.
 

 

Appendix

LeanData Technical Considerations:

• When a record meets the criteria for a callout to Slack, LeanData will wait 30 seconds to accumulate callout records before sending.
• If no other records enter the queue in that time frame, LeanData will run the callout batch every 30 seconds.
• On the callout object, LeanData tracks the readiness of the callout before initiating the callout batch.
• In the event of a Slack outage, LeanData will not reattempt to initiate any affected notifications, as Slack may complete these notifications once service is restored. Please check with Slack at https://status.slack.com/ for details on a specific Slack outage.