IntegrationCRM destination
Salesforce Integration - Product Events in Salesforce Campaigns and Properties
Meshes routes product events into Salesforce through campaign membership and property updates. That gives sales, success, and RevOps a cleaner path from product activity to CRM action without tying your application code to Salesforce availability.
account.plan_changedpayment.failedchurn.risk_changed|Actionsadd_to_campaignremove_from_campaignupdate_propertyThe event names shown here are examples. In Meshes, event types are fully customized for each organization.
What you can do
Supported actions with real product context behind them
Create the Salesforce connection in your Meshes workspace with OAuth. Meshes then loads the campaigns and properties available to that Salesforce account so rules can stay tied to real CRM objects.
Salesforce is where pipeline, account health, and customer follow-up often become operational. When account.plan_changed or payment.failed happens in your product, that context needs to land in Salesforce quickly enough for the downstream process to react.
Meshes lets you keep Salesforce wiring in the delivery layer instead of sprinkling CRM writes across billing jobs, admin tooling, and lifecycle workers. You define the rule once in Meshes, map the event data to the campaign or property you care about, and let Meshes handle the delivery path.
add_to_campaignAdd contacts to campaigns
Use product qualification, onboarding, or expansion events to place the right contacts into Salesforce campaigns for follow-up and reporting.
remove_from_campaignRemove contacts from campaigns when state changes
Stop the wrong follow-up path when the event means the user converted, churned, or moved into a different motion.
update_propertyUpdate Salesforce contact properties
Write plan, health, qualification, or revenue context into Salesforce so the CRM reflects the latest state from your product.
Common use cases
Where Meshes teams put Salesforce to work
Workflows where this destination tends to matter first — the product event, the destination action, and the operational retry path living inside the same workspace.
Plan and account-state changes visible inside the CRM
Use account.plan_changed to keep Salesforce fields current when customers upgrade, downgrade, or move between contract states.
Churn or billing risk in the CRM, quickly
Surface payment.failed or risk-scoring events in Salesforce so customer teams can react before the account goes cold.
Campaign membership driven by product qualification
Add or remove contacts from campaigns when enterprise leads, onboarding milestones, or expansion signals happen in-product.
No stale CRM context during customer handoff
Let support, sales, and success see the same product signal in Salesforce without waiting for a manual sync to close the gap.
How it works
Connection, rule, event — the three-step operating model
A connection lives in the workspace, a rule binds the event to the action, and the delivery layer handles the last mile with retries, replay, and per-destination history.
Connect Salesforce
Create a Salesforce connection in Meshes with OAuth and confirm the campaigns and properties you want to use are available in the connection action data.
Create routing rules in Meshes
Create rules for events like account.plan_changed or payment.failed, choose add_to_campaign or update_property, then map the event fields that Salesforce needs.
Emit the event and review delivery
Emit the event from your product or trigger Send Test Event in Meshes. Meshes delivers the CRM update, retries transient errors, and records the attempt history for review and replay.
Event example
Emit the product event once
import MeshesEventsClient from '@mesheshq/events';
const meshes = new MeshesEventsClient(
process.env.WORKSPACE_PUBLISHABLE_KEY!,
);
await meshes.emit({
event: 'account.plan_changed',
resource: 'account',
resource_id: 'acct_913',
payload: {
account_id: 'acct_913',
email: 'owner@northstar.io',
previous_plan: 'starter',
current_plan: 'growth',
monthly_recurring_revenue: 499,
},
});Connection model
OAuth
Create the Salesforce connection in your Meshes workspace with OAuth. Meshes then loads the campaigns and properties available to that Salesforce account so rules can stay tied to real CRM objects.
Why Meshes
Why teams use Meshes for Salesforce
Salesforce sits inside the same fan-out, retry, replay, and delivery-visibility layer as every other destination — customer-connected or internal — that the workspace owns.
CRM updates stay close to the source signal
Instead of asking billing code or admin jobs to know Salesforce, Meshes turns the product event into the CRM update with one dedicated delivery path.
Campaign membership and field updates can coexist
The same event can move contacts into the right campaign and update the properties downstream automation depends on.
Retries matter more when the CRM drives follow-up
A missed Salesforce write can become a missed customer conversation. Meshes keeps the attempt visible, retryable, and replayable.
CRM coupling stays out of product handlers
Your app can emit the account event once and let Meshes absorb Salesforce auth, action data, and delivery concerns separately.
Keep exploring
Related guides, use cases, docs, and comparison pages
Concrete patterns, supporting documentation, and build-vs-buy context that usually come up during evaluation.
Catalog
All integrations
Return to the catalog and compare Salesforce with other CRM, messaging, and email destinations.
Open linkDocs
Salesforce integration docs
Salesforce connection, rule configuration, and testing flow in the product docs.
Open linkUse Case
Churn prevention event routing
Example of lifecycle and risk events updating the systems that customer teams already rely on.
Open linkUse Case
Payment failed notifications
Example of payment.failed reaching CRM, support, alerts, and email from the same product event.
Guide
Update Salesforce on plan change
Use account.plan_changed to keep the Salesforce record aligned with the current subscription state.
Compare
Meshes vs. DIY
Breakdown of the effort required to build Salesforce fan-out, retries, and replay into your own product code.
Open link