In n8n, add a Salesforce node, then create a Salesforce credential. Most setups use OAuth: sign in to Salesforce, approve access, and you’re done. If your org restricts OAuth, you may need a connected app and the right permission set. After authentication, test with a simple “Get Record” or “Create Lead” step. From there, you can chain actions like Slack messages, Gmail sends, or Google Sheets updates.

A lot: lead capture, routing, enrichment, pipeline updates, and follow-ups. You can auto-create leads from web forms, dedupe contacts, update opportunity stages from external events, or post deal alerts to Slack. Many teams also sync Salesforce fields to Google Sheets for quick reporting, then write cleaned data back. You can even draft first-touch emails or call notes with OpenAI, then save them to Salesforce for consistency.

Yes. You’ll need access to a Salesforce org and a user with permission to use the API and the objects your workflow touches (like Leads or Opportunities).

The big ones are permissions, API limits, and field mapping. If a workflow fails, it’s often because the Salesforce user can’t read/write a field, or the record type requires values you didn’t send. Some orgs also hit daily API call limits, so batching updates and avoiding unnecessary polling matters. Webhooks help, but Salesforce events can be tricky depending on your edition and setup. Frankly, starting with one clear use case and logging every step saves hours later.