The world's leading cloud-based CRM platform powering sales, service, and marketing for businesses of all sizes.
Full ReviewMake connects to Salesforce through a dedicated module that supports all standard and custom Salesforce objects. This integration is particularly valuable for organizations that need Salesforce to communicate with tools outside its native ecosystem: syncing leads from marketing platforms, updating records based on events in other systems, or building complex multi-step automations that span Salesforce and dozens of other applications.
While Salesforce has its own automation tools (Flow, Process Builder), Make excels when workflows cross system boundaries. A single Make scenario can watch for a new Salesforce opportunity, enrich the account data from an external source, notify the sales team in Slack, create a project in Asana, and update a tracking spreadsheet, all without code. Make's Salesforce module supports SOQL queries, giving advanced users the ability to pull precisely the data they need.
Make is a strong choice over Zapier for Salesforce integrations when you need complex data transformations, conditional logic with multiple branches, or iterative processing of related records. The visual canvas makes multi-step Salesforce automations significantly easier to build, understand, and debug.
Log in to Salesforce. Navigate to Setup > Users > Profiles. Open the profile assigned to the user account you will use for Make. Scroll to Administrative Permissions and confirm that API Enabled is checked. If it is not, edit the profile and enable it. Without this permission, Make cannot connect to Salesforce.
In Make, click Create a new scenario. Click the empty module node on the canvas to open the module search. Search for "Salesforce" and select the Salesforce module.
Select a trigger or action (e.g., Watch Records). Click Add next to the Connection field. Choose your Salesforce environment: Production or Sandbox. Click Continue and you will be redirected to Salesforce's login page. Enter your credentials and click Allow to grant Make access. The connection will be saved for reuse across scenarios.
For the Watch Records trigger, select the Salesforce object to monitor (Lead, Contact, Account, Opportunity, or any custom object). Choose whether to watch for New Records, Updated Records, or both. Set the Limit to control how many records are processed per cycle. Optionally add a SOQL WHERE clause to filter which records trigger the scenario (e.g., StageName = 'Closed Won' to only trigger on won opportunities).
Click the + icon to add modules after the Salesforce trigger. Map Salesforce fields to downstream module inputs by clicking fields and selecting from the available data. For example, map the Salesforce Lead's email to a Mailchimp subscriber's email field, or map the Opportunity amount to a Slack message template.
Click Run once to test. If using a Watch trigger, Make will pull the most recent records that match your criteria. Review the data output from the Salesforce module and verify downstream modules process it correctly. Fix any field mapping issues before activating.
Toggle the scenario to ON. Configure the schedule by clicking the clock icon on the trigger module. For Salesforce integrations involving sales data, a 5-15 minute interval is typical. For daily reporting workflows, schedule once per day.
Make's Salesforce module supports several configuration approaches. Use Search Records with SOQL queries for pulling specific datasets (e.g., all opportunities closing this month). The Create/Update Record action supports upsert operations using an external ID field to prevent duplicates. Attachment and file operations are available for uploading documents to Salesforce records. For Salesforce-to-Salesforce scenarios (e.g., sandbox to production sync), you can use two separate Salesforce connections in the same scenario.
| Data | Direction | Frequency |
|---|---|---|
| Leads | Bidirectional | Based on scenario schedule |
| Contacts | Bidirectional | Based on scenario schedule |
| Accounts | Bidirectional | Based on scenario schedule |
| Opportunities (with stage history) | Bidirectional | Based on scenario schedule |
| Custom objects | Bidirectional | Based on scenario schedule |
| Files and attachments | Bidirectional | Based on scenario schedule |
This typically means the Salesforce session has expired. Go to Connections in Make, find the Salesforce connection, and click Reauthorize. If this happens frequently, check that the connected user's Salesforce session timeout settings are not unusually short under Setup > Session Settings.
This error means a required field is missing or a field value violates a validation rule. Check Salesforce's validation rules and required fields for the object you are trying to create. Map all required fields in the Make module and ensure values conform to validation rules and picklist values.
Salesforce imposes daily API call limits based on your edition and number of user licenses. Each Make module execution that calls Salesforce counts toward this limit. Reduce frequency, add filters to process fewer records, or use batch operations where possible. Check your current usage under Setup > System Overview > API Usage.
Use Make's HTTP module with Salesforce's REST or Bulk API endpoints for operations not covered by the standard module, such as bulk data loads or metadata API calls. Implement webhook-based triggers using Salesforce Outbound Messages or Platform Events to achieve near-real-time automation instead of polling. The Aggregate module can compile multiple Salesforce records into a single downstream action, useful for summary reports or batch updates. Use Make's data stores to maintain cross-reference maps between Salesforce IDs and external system identifiers.
