> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gettap.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Salesforce

> Sync captured leads and meeting summaries into Salesforce.

## What syncs

| Tap | Salesforce |
| - | - |
| Captured lead | **Lead** record |
| Meeting summary and action items | Task on the lead |
| Capturing member | Lead owner |

<Note>
  Tap creates Salesforce **Leads**, not Contacts. That matches how most teams work — a person met at an event is unqualified until someone qualifies them. Convert the Lead to a Contact and Account in Salesforce using your normal process.
</Note>

## Connect

<Frame caption="Find it under Integrations in Tap Teams">
  ![The Integrations screen in Tap Teams showing each available connector and its connection status.](https://cdn.gettap.co/docs/images/screens/teams-integrations.png)
</Frame>

<Steps>
  <Step title="Start the connection">
    In Tap Teams, go to **Integrations → Salesforce → Connect**.
  </Step>

  <Step title="Sign in to the right org">
    You're sent to Salesforce to authorize. Make sure you're signing into the org you actually want — if you're currently logged into a sandbox in the same browser, Salesforce will happily authorize the sandbox.
  </Step>

  <Step title="Approve access">
    Approve with a user who can create and edit Leads and Tasks.
  </Step>

  <Step title="Map your fields">
    Standard fields map automatically. Map custom fields by hand — see [Field mapping](/en/integrations/field-mapping).
  </Step>
</Steps>

## Custom fields

Create the field in Salesforce first: **Setup → Object Manager → Lead → Fields & Relationships → New**. Only then will it appear as a mapping target in Tap.

## Notes specific to Salesforce

<AccordionGroup>
  <Accordion title="Required fields and validation rules block syncs" icon="shield-halved">
    Salesforce enforces required fields and validation rules on every write. A validation rule demanding a value Tap never sends rejects the whole record. If syncs stopped working right after an admin added a rule, that's your cause.
  </Accordion>

  <Accordion title="Company is required on standard Leads" icon="building">
    Salesforce's standard Lead object requires a Company. Map your `company-name` capture field to it, and consider making that field required on your capture form — otherwise leads captured without a company are rejected.
  </Accordion>

  <Accordion title="Owner assignment needs matching emails" icon="user-check">
    Tap matches the capturing member's Tap email to a Salesforce user's email. No match means the org's default owner, not a failed sync.
  </Accordion>

  <Accordion title="Assignment rules still apply" icon="route">
    Tap sets an owner where it can, but your org's Lead assignment rules run afterwards and may reassign. If ownership looks wrong, check your assignment rules before assuming Tap set it.
  </Accordion>
</AccordionGroup>

<Card title="Not arriving?" icon="wrench" href="/en/integrations/troubleshooting">
  Work through the troubleshooting guide.
</Card>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.