Every new Salesforce lead joins your Meser10 list on its own
A managed package installed in your Salesforce org that sends each lead or contact to the Meser10 list you choose. One-way only: nothing is written back to the CRM, and every attempt is logged in a record you can read.
Your sales team works in Salesforce and your email goes out from Meser10. Without a connection, someone exports a file every week, uploads it to a list, and forgets the week after. This app removes that step: a lead or contact created in Salesforce reaches your Meser10 list right away.
What the app does
- A new lead or contact is added to the mailing list you chose in Meser10.
- A change to an existing record is sent again, but only if a field that is actually synced has changed.
- Every attempt writes a log line you can read: sent, skipped or failed, with the reason.
- You decide per object whether it syncs, and to which list.
What it does not do, on purpose
The app reads nothing back from Meser10 and changes no record in Salesforce. It is one-way by design, so nothing in your CRM changes without you asking. It also does not create lists: the list must already exist in Meser10. If it does not, Meser10 rejects the contact and the app logs the rejection.
Installation, in short
- Install the package. Your Salesforce admin receives an install link from us and chooses Install for Admins Only. You can install in a Sandbox first.
- Enter the API key. In Setup, under External Credentials, open Meser 10 Auth and paste your account API key into the ApiKey parameter.
- Choose what syncs. One Sync Rule record per object: the object, the list name exactly as it appears in Meser10, and whether to send updates too.
- Permissions. Whoever needs to see the log gets the app permission set.
It takes a Salesforce admin about ten minutes. We guide the installation, including a live check that a lead created in your org really reached the list.
Where the API key is kept
The key is stored in a Salesforce External Credential, encrypted by the platform. It is not written to a field, does not appear in the sync log, and is not exposed by metadata retrieve or data export. Every class runs with sharing and in the context of the user, and a field the user may not see is not sent.
Status today
The app is packaged as a managed package and it works: it was tested end to end in a real Salesforce org, including a lead that reached the list. It is not yet listed on AppExchange, which requires a partner account and a Salesforce security review. We are in that process. Until then, installation is by direct link, with our support.
Questions
Is the app already on AppExchange?
Not yet. It is a ready managed package installed by direct link with our support. AppExchange needs a partner account and a Salesforce security review, and we are in that process.
Is anything written back to Salesforce?
No. The only thing the app writes inside Salesforce is the sync log record itself.
What happens if the list name is wrong?
Meser10 rejects the contact and the app logs the rejection with the reason. The app never creates lists, so a typo cannot create a new list.
Can I sync only leads and not contacts?
Yes. Each object has its own rule with its own on/off setting, and you choose whether to send updates to existing records or only new ones.
How do I get the install link?
Email support@meser10.co.il and we will send the install link and setup guide, and stay with you until the first lead reaches the list.