How do you connect Salesforce to Zapier?

Before You Start: Salesforce Edition Requirements

Salesforce API access is required for any automation platform connection. API access availability depends on your Salesforce edition:

Verify your edition and API access before starting the integration. Without API access, the OAuth connection will fail silently or return authentication errors.

Step 1: Understand the Zapier Salesforce Connector

Zapier's Salesforce connector supports:

Triggers (events that start a Zap):

• New Record — triggers when any record type is created
• Updated Record — triggers when a record is modified
• New Outbound Message — triggered by Salesforce workflow rules
• New/Updated Record (SOQL) — uses custom SOQL queries for advanced filtering

Actions (steps Zapier performs):

• Create Record — creates contacts, leads, opportunities, or custom objects
• Update Record — modifies existing records by ID
• Find Record — searches for existing records using SOQL
• Find or Create Record — searches first, creates if not found

Step 2: Connect Salesforce via OAuth

1. In the Zapier editor, select "Salesforce" as your app
2. Click "Sign in to Salesforce"
3. Zapier redirects to Salesforce's OAuth consent screen
4. Log in with a Salesforce user that has API permissions and the "Modify All Data" or "API Enabled" profile permission
5. Approve access
6. Zapier stores the OAuth token securely

Use a dedicated integration user (not a personal account) for production Zaps. This prevents Zaps from breaking when an employee changes their password or leaves the organization.

Step 3: Configure Triggers

Basic Trigger: New Lead

Select "New Record" trigger, choose "Lead" as the object type. Zapier polls Salesforce every 1-15 minutes depending on your plan (1 minute on Professional+). Each new lead creates a Zap run.

Advanced Trigger: SOQL Query

For filtered triggers, use "New/Updated Record (SOQL)":

SELECT Id, Name, Email, LeadSource
FROM Lead
WHERE CreatedDate > LAST_N_HOURS:1
AND LeadSource = 'Web'
ORDER BY CreatedDate DESC

SOQL triggers provide fine-grained control over which records fire the Zap, reducing unnecessary task consumption.

Step 4: Configure Actions

Create a Contact from a Form Submission

Map fields from your trigger (e.g., Typeform, Gravity Forms) to Salesforce Contact fields:

• First Name → FirstName
• Last Name → LastName
• Email → Email
• Company → Account (use a Find step first to match by company name)

Update an Opportunity Stage

Use "Update Record" with the Opportunity ID from a previous step. Map the new stage value to the StageName field.

Step 5: Handle Salesforce API Rate Limits

Salesforce enforces API call limits based on your edition and license count:

• Enterprise: 1,000 calls per user license per 24 hours (minimum 15,000)
• Unlimited: 5,000 calls per user license per 24 hours (minimum 25,000)

Each Zap trigger poll consumes 1 API call. Each action step (create, update, find) consumes 1-3 API calls. High-volume Zaps can exhaust API limits quickly.

Monitor API usage in Salesforce: Setup → Company Information → API Usage (Last 24 Hours).

Step 6: Test and Activate

1. Run a test with sample data to verify field mapping
2. Check the created/updated record in Salesforce
3. Verify no duplicate records were created
4. Turn on the Zap
5. Monitor the first 24 hours in Zapier's Task History

Common Patterns

Editor's Note: The most common mistake we encounter in client projects: Professional edition users without the API add-on ($25/user/month extra). Clients discover this only after hitting authentication failures during Zap setup — the error message from Salesforce does not clearly indicate the issue is a missing API license. We now include "Verify Salesforce API access" as the first step in every integration engagement. For high-volume integrations (1,000+ records/day), also verify that the Salesforce API call limit is sufficient. One client exceeded their daily API limit by 2pm because a misconfigured Zap was polling every minute with SOQL queries that each consumed 3 API calls.