Leadmonk offers seamless integration with Salesforce Sales cloud CRM, allowing you to schedule meetings with prospects and automatically create or update corresponding records in Salesforce. The integration saves valuable time for your sales representatives, allowing them to focus on building customer relationships.
This documentation will guide you through the process of integrating Leadmonk Appointment Scheduling Software with Salesforce Sales cloud CRM.
TABLE OF CONTENTS
- What can the integration do?
- Pre-requisites for the integration
- Integration Steps
- CRM Integration Preferences
- Updating Contact and Lead Details in Salesforce
- Disconnecting Leadmonk from Salesforce CRM
- Other help page
Note: You must be a Leadmonk owner or admin to authenticate HubSpot for your organization and you must be on a Professional subscription plan and above.
Attention: Disabling the Salesforce user account that initially connected Leadmonk will disrupt data updates from Leadmonk in Salesforce. To resolve this, simply reconnect Salesforce to Leadmonk using valid Salesforce user account with the necessary permissions.
What can the integration do?
- Create Contacts
- Create Leads
- Create Account
- Create Opportunity
- Create and update engagements [meetings]
- Update Contact Owner
- Update Lead Owner
If you are using our router feature we require this SFCRM connection to do routing based upon records in Salesforce (Lead, Contact, Account, and Opportunity).
Pre-requisites for the integration
- You'll need Salesforce Enterprise or higher edition.
- You'll need Salesforce admin privileges.
- The person who will be using Leadmonk must have a Salesforce account.
- The email address that the person uses for their Leadmonk account must be the same email address that they use for their Salesforce account.
- In order to authenticate Salesforce CRM for your organization, you must be a Leadmonk owner or admin. Additionally, your Leadmonk subscription plan must be essential plan or above.
- Enable API access in Salesforce - API access must first be enabled on your Salesforce account in order for Leadmonk to integrate. API access may be restricted based on your Salesforce edition or administration restrictions. Please contact your Salesforce administrator if you do not have access to enable your API. This is a Salesforce limitation, and not controlled by Leadmonk.
- For instructions to enable the Salesforce API, please: click here.
Standard Object Permissions
- Accounts: Read/Edit/View All
- Contacts: Read/Edit/View All/Create*
- Leads: Read/Edit/View All/Create*
- Opportunities: Read**
* Create is required if Leadmonk will be creating Leads/Contacts in your instance.
** Only required if you are making use of this object type in Leadmonk.
Integration Steps
Follow these steps to integrate Salesforce CRM with Leadmonk:
- Log in to your Leadmonk account.
- Go to the Integrations page in the Leadmonk app.
- Look for Salesforce and Click Configure button.
- On the Salesforce Integration page, click Configure button to authenticate and connect.
- Once you are in the 'Salesforce Integration' page, click Connect button to connect your Salesforce account with your Leadmonk account.
- This will open a Salesforce integration page. Follow the on-screen prompts to complete the setup process.
- Once the two platforms are connected, you see 'enabled' status as shown below for the integration.
CRM Integration Preferences
The Salesforce integration has the following default behavior.
Enable lead creation
If this switch is enabled, Leadmonk searches for an account in SFCRM with the matching domain from the invitee email address [the website of account matching the domain of email address]. If it does not find a matching account in SFCRM, then a lead will be created.
How it works:
- When a lead schedules a meeting through Leadmonk or submits an inbound router form (provided it has name and email address fields), Leadmonk will check if there is an existing account in Salesforce matching the domain of invitee's email address.
- If there is no matching account, then Leadmonk will create invitee as a new lead in Salesforce and update the new lead with the invitee information, such as name, email address, and company.
Enable contact creation
If this switch is enabled, Leadmonk searches for an account with the matching domain from the invitee email address. If it finds a matching account in SFCRM, then Leadmonk searches for a matching contact within the account. If it does not find one, then a new contact will be created within the account.
How it works:
- When a lead schedules a meeting through Leadmonk or submits an inbound router form (provided it has name and email address fields), Leadmonk will check if there is an existing account in Salesforce matching the domain of invitee's email address.
- If it finds a matching account in SFCRM, then Leadmonk searches for a matching contact within the account. If it does not find a matching contact, then a new contact will be created within the account.
Enable account creation
If this switch is enabled, Leadmonk searches for an account with the matching domain from the invitee email address. If it does not find a matching account in SFCRM, then Leadmonk creates an account in SFCRM.
How it works:
- When a lead schedules a meeting through Leadmonk or submits an inbound router form (provided it has name and email address fields), Leadmonk will check if there is an existing account in Salesforce matching the domain of invitee's email address.
- If it does not find a matching account in SFCRM, then Leadmonk creates an account.
Enable opportunity creation
If this switch is enabled, Leadmonk searches for an account with the matching domain from the invitee email address. If it finds a matching account in SFCRM, then Leadmonk searches for an open (active) opportunity within the account. If it does not find one, then a new opportunity will be created within the account.
How it works:
- When a lead schedules a meeting through Leadmonk or submits an inbound router form (provided it has name and email address fields), Leadmonk will check if there is an existing account in Salesforce matching the domain of invitee's email address.
- If it finds a matching account in SFCRM, then Leadmonk searches for an open(active) opportunity within the account. If it does not find one, then a new opportunity will be created within the account.
Enable engagement updates
If this switch is enabled, Leadmonk will create or update a meeting in Salesforce for the contact.
How it works:
- When an invitee schedules a meeting through Leadmonk
- Search will be done in Salesforce to find a matching account (account with matching domain of the invitee email address). If it finds one, then a matching contact will be searched within that account. If it finds one, then meeting will be created for that contact.
- If there is no matching contact, then search will be done to look for a matching Lead. If it finds one, then meeting will be created for that lead in Salesforce.
- If Leadmonk does not find a matching lead or a matching contact, then it does not create the meeting in Salesforce.
- The meeting title will have the format Meeting-Leadmonk: {Event name} in Salesforce.
- When a meeting is canceled or rescheduled by either party, the activity will be updated in Salesforce and both parties will be notified.
- Canceled meetings will update the activity as [Canceled] <event name> in Salesforce. The activity does not disappear, giving you a complete history of activity for the account.
Contact and Lead owner updation
If this switch is enabled, Leadmonk will update the meeting assignee (meeting host) as Lead/contact owner in Salesforce.
When Leadmonk creates a lead, contact, account, or opportunity in Salesforce, it checks if the Leadmonk user [meeting host] exists in Salesforce with the same email address. If it does not find a matching user, the Salesforce admin becomes the owner of the corresponding object.Note: Owner updation in SFCRM is part of the advanced plan and it happens through inbound router only.Account identification in Salesforce
Now you have two options for account identification in Salesforce for ownership routing. They are:
Option 1: Find Account with Matching Contacts
This option searches for an account in Salesforce with at least one contact whose email domain matches the lead's email domain. If multiple accounts qualify, the one with the most matching contacts takes precedence.
Option 2: Find an Account with Matching Website
This option searches for an account in Salesforce whose website domain matches the lead's email domain.
Updating Contact and Lead Details in Salesforce
Leadmonk updates the following contact and lead fields in Salesforce by default: First name, Last name and Email address.
If the contact or lead creation happens through the inbound router, you can update other fields in Salesforce as well. To do this, you need to map the form properties to the Salesforce Lead/Contact properties as shown below.
Once you have done the mapping for both contact and lead objects, click Update mapping button to save the changes. Then Leadmonk will update the corresponding fields in Salesforce when a contact/lead is created through the inbound router.
Click on Clear mapping text to clear the mapping of a form property.
Note: Contact/Lead details updation with form properties is part of the advanced plan and it happens through inbound router only.
Disconnecting Leadmonk from Salesforce CRM
To disconnect Leadmonk from Salesforce CRM, follow these steps:
- Go to the Integrations page in the Leadmonk app.
- Select Salesforce CRM. Click 'Configure' button there. This opens 'Salesforce Integration' page
- Click on "Disconnect" button on the Salesforce Integration page
- Once disconnected, Leadmonk will no longer pass scheduled events information to Salesforce CRM.
If you have any further questions or encounter any difficulties during the integration process or disconnection, please don't hesitate to reach out to Leadmonk's support team for assistance.
Other help page
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article