Salesforce
Connect Salesforce so Meerkats has leads, accounts, contacts, opportunities and campaigns, and can update them with your approval.
The Salesforce connection imports leads, accounts, contacts, opportunities, campaigns and campaign members, with their standard and custom fields and the activity timeline. It links contacts and leads to orders and ad clicks Meerkats already has.
| How it connects | Sign in and approve |
| Reads | Leads, Accounts and contacts, Opportunities, Campaigns and members, Activities |
| Can change | Update a field on a lead, account, contact or opportunity; Change an opportunity stage; Create a lead, contact or opportunity; Create a task or log an activity; Add a lead or contact to a campaign |
| Refresh | On your plan's schedule, plus Resync anytime |
Before you start#
- A Salesforce user with API Enabled on their profile and read access to the objects you want to sync.
- A System Administrator to approve the connected app the first time.
- Sandbox or production: each connects separately.
Permissions#
Salesforce asks you to approve these permissions. Each one is listed with why Meerkats needs it.
| Permission | Why Meerkats needs it |
|---|---|
api | Read and write the objects your Salesforce user can access |
refresh_token, offline_access | Stay connected without signing in again |
id, profile, email | Identify the connecting user |
Connect#
1. Connect Salesforce#
- Open Integrations
In the sidebar, select Integrations, find Salesforce and select Connect.
- Sign in to Salesforce
Choose production or sandbox, sign in, and select Allow on the Meerkats connected app.
- Choose objects and record types
Pick the objects to import (Lead, Account, Contact, Opportunity, Campaign, Task, Event) and any record types to include.
- Resync
Go to Data Hub › Bronze Layer, pick Salesforce and select Resync.
What syncs#
| Salesforce | In Meerkats |
|---|---|
| Leads | Standard and custom fields, source, status, owner, converted lead links |
| Accounts and contacts | Fields, owner, account hierarchy, contact roles |
| Opportunities | Amount, stage, probability, close date, owner, products, stage history |
| Campaigns and members | Campaign, type, status, members and their status |
| Activities | Tasks and events on each record |
Raw data lands in Data Hub › Bronze Layer. Modelled tables, with metrics defined once, are in Data Hub › Gold Layer. Every number in a report or an agent’s answer comes from a query on these tables, never from the model’s own arithmetic.
Metrics you get#
The metrics people ask for most, named as Salesforce names them. The full list, with each definition, is in the metric catalog.
New leadsLeads by sourceLead conversion rateOpportunities createdPipeline valueWin rateAverage deal sizeSales cycle lengthCampaign influenced revenue
How often it syncs#
Meerkats syncs on your plan's schedule: daily on Free, hourly on the $49 plan, every 30 minutes on $149 and every 15 minutes on $399. You can run a sync at any time with Resync in Data Hub › Bronze Layer.
- Meerkats syncs changed records on your plan's schedule. Salesforce API limits apply per org; Meerkats stays under them and backs off if the org is close to its daily limit.
What Meerkats can change#
In every connected tool, Meerkats can create, read, update and delete records, within the permissions you grant and the permissions the tool allows. These are the changes it proposes for Salesforce, and the limit that applies to each.
| Change | Limit |
|---|---|
| Update a field on a lead, account, contact or opportunity | Proposed for approval; before and after values shown |
| Change an opportunity stage | Proposed for approval |
| Create a lead, contact or opportunity | Proposed for approval |
| Create a task or log an activity | Low risk: can run on its own once you allow it |
| Add a lead or contact to a campaign | Low risk: can run on its own once you allow it |
How every change is governed
Every change starts as a proposal in your Inbox. Nothing changes in the connected tool until a person approves it, unless you set that rule to act on its own.
Before it runs an approved change, Meerkats re-reads the live value. If the value moved since the proposal, it asks again instead of acting on stale data.
Meerkats stores the value it replaced, so every change can be undone from Agents run history.
Anything Meerkats creates starts paused. Switching it on is a second, separate approval.
Troubleshooting#
Login fails with an API error
The user needs API Enabled on their profile or permission set. Ask a System Administrator.
A custom object isn't available
Meerkats syncs the standard objects listed above plus any custom object you add on the connection. Add it there, then Resync.