Slack + Salesforce Integration
The Slack+Salesforce integration allows Zuddl to send Slack notifications to the Salesforce account/ contact/ lead owner in your Slack workspace when attendees perform specific actions in a Zuddl event/webinar.
Overview
Currently, Zuddl notifies you of the following attendee actions:
User registration
Registrant check-in to the event (first time joining)
This integration sends notifications in a selected Slack channel and also as a direct message to the following recipients in the order of availability in Salesforce:
Account owner
Contact owner
Lead owner
Before sending notifications, the integration checks for the registrant’s email address in Salesforce in the following manner: if the registrant’s email address exists as a Contact in Salesforce and is associated with an account, the integration notifies the account owner. If an account owner does not exist in Salesforce, it notifies the contact owner. If the email is not present as contact, then the integration checks if a lead exists with the same email. If it exists, the integration notifies the selected Slack channel and the lead owner.
Note: If any of the recipients are not in Slack, the integration sends only channel notifications.
Note: This is one-way integration support only for Slack and does not push any notification on Salesforce.
Prerequisites
Before we begin the integration, ensure you have the following:
A logged-in Slack workspace account.
A logged-in Salesforce account with access to all leads, contacts and accounts.
Steps
Note: It is recommended that you stay signed in before you start installing the app.
Go to your organizer dashboard.
Go to Integrations.
From the integration listing page, click View details on the Slack+Salesforce tile.
On the Slack app details page, click Install app.
On the Slack authentication page, click on New authentication. This initiates the new authentication creation flow.
Note: If an account has already been added and you want to add another account, Click Add a new account.Enter Your authentication name. Your authentication is used to search your account from the list.
Select Production for the Salesforce instance type.
Click Create.
On the permission page for Salesforce, click Allow. This authorizes Zuddl to access your Salesforce account.
Note: If you aren’t already signed in to your Salesforce account, you would be taken through the sign-in process.
Click Next. This starts the Slack authentication flow.
On the permissions page, click Allow and grant tray.io all permissions to access the Zuddl Slack workspace. This authenticates and connects your Slack workspace on Zuddl.
Note: Zuddl uses tray.io to connect the two platforms.Click Next.
In the Slack Channel Name dropdown, select the channel where you want to receive the notifications.
Optional. Select the Notify the owner checkbox. This is disabled by default.
so that the lead/contact/account owner gets notified of the attendee actions on Slack.On the Activity Notification Configuration screen, select the Zuddl information that you want the integration to pass to Slack.
Click Finish.
Notification Format
The following subsections show how different notifications appear on Slack.
New registration for an event
When a new registration happens for an event, the Slack notification is as shown below:
Here, the term “user” is used for registrants in Zuddl. So the User email should be the same as Contact Email or Lead Email.
Attendee joining an event
The following screenshot shows how a notification appears on a Slack channel when an attendee joins an event with account/contact/lead owner information.
Sample notifications
The following sections describe how channel notifications appear on different use cases.
Contact with Account and Opportunity
If a contact is present (with the same email as the registrant’s) and is associated with an account and opportunities, the notifications show the most recently created opportunity.
If an account is linked to the contact, the notifications are sent to the account owner.
Note: If opportunity is not present, the opportunity fields are not shown in the notification.
Contact with Account without Opportunity
If a contact is present (with the same email as the registrant’s) and is associated with an account but no opportunities because the latest opportunity is in lost stage, the notifications appear as shown below:
No Account found for Contact
If there is no account linked to the Contact, notifications go to Contact owner if available on Slack. The notification message appears as shown below:
Account owner is not found on Slack
If account owner email is not found on Slack, notification only goes to the channel with the message as shown below:
No Contact owner found for Contact
If there is no Contact owner linked to a Contact but a Lead does exists with the same email, notifications go to the Lead owner if found on Slack. The message appears as shown below:
Note that, here the Lead link is given in the notification as the lead is not yet converted to a Contact.
Contact owner is not found on Slack
If no contact owner email is found on Slack, the notification is sent only to the channel. The message appears as shown below:
Lead owner is not found on Slack
Similar to the contacts, if no lead owner is found on Slack, the following message is sent to the channel:
No Contact or Lead owner found for Contact
If there is neither a Contact or a Lead owner linked to a Contact, notifications go to the channel. The message appears as shown below:
Custom fields added
If any custom fields are added to the registration form, they show up in the notification as shown below:
Limitations
We have a hard limit of 10 registration fields that can be passed from Zuddl to Slack. Fields are passed in this order:
Standard fields
Salesforce links (if any)
Custom fields
Empty fields
Editing the authentication
If you wish to change the channel or connect a new Salesforce account, you can click the Edit option.
This takes you through the entire authentication flow again where you can make changes.
Note: If we archive a channel, the messages won’t be sent to Slack.
