> ## 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.

# Veeva Vault

> Sync captured leads and meeting summaries into Veeva Vault CRM.

Veeva Vault is the CRM most life-sciences teams run on. If your team works in pharma, biotech, or medical devices, this is the connector you want — the others in this list aren't built for that world's data model or its record keeping expectations.

## What syncs

| Tap | Veeva Vault |
| - | - |
| Captured lead | Contact record |
| Meeting summary and action items | Call or activity record |
| Capturing member | Record owner |

## 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 → Veeva Vault → Connect**.
  </Step>

  <Step title="Authorize">
    Sign in with a Vault account that can create and edit the record types above. A read-only account connects successfully and then fails on the first sync — a pattern worth checking for before an event rather than after.
  </Step>

  <Step title="Map your fields">
    Match your capture fields to Vault fields. See [Field mapping](/en/integrations/field-mapping).
  </Step>

  <Step title="Test with one lead">
    Capture a test lead and confirm it lands on the right record type with the right owner.
  </Step>
</Steps>

## Notes specific to Veeva

<AccordionGroup>
  <Accordion title="Your Vault configuration governs what's accepted" icon="shield-halved">
    Vault instances are heavily configured per organisation. Required fields, picklist values, and validation rules differ from company to company, and they're enforced on write — so a mapping that works in one Vault can be rejected by another. Test against your own instance rather than assuming.
  </Accordion>

  <Accordion title="Record types matter" icon="table-list">
    If your Vault uses several record types for contacts or activities, confirm which one Tap is writing to before your first event. Records landing on an unexpected type are easy to miss and tedious to move.
  </Accordion>

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

  <Accordion title="Compliance is still yours" icon="scale-balanced">
    Life-sciences teams usually have rules about what may be recorded about an interaction and for how long. Tap syncing into Vault doesn't change those obligations — particularly around [meeting recordings](/en/leads/transcription) and consent.
  </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.