Docs
OverviewPlatformPlatform APIA2P Messaging API
AI & MCP
Open dashboard
OverviewPlatformPlatform APIA2P Messaging API
AI & MCP
Getting started
  • Overview
  • Start guide
  • Project status
  • Concepts
AI
  • Iris
  • AI writing
  • Connect your AI (MCP)
Channels
    • Countries & coverage
    • Senders & registration
    • Essentials
    • Countries & availability
    • What is RCS
    • Senders & verification
    • Agent profile
    • Best practices
    • Acceptable use
    • SMS fallback
  • WhatsAppSoon
  • Compliance
  • Countries
    • Austria
    • Brazil
    • Canada
    • Colombia
    • France
    • Germany
    • India
    • Indonesia
    • Mexico
    • Netherlands
    • Peru
    • Singapore
    • Spain
      • Authorise the alias
      • Register directly
      • Without a certificate
      • Rejected alias
    • Ukraine
    • United Kingdom
    • United States
    • Other countries
Marketing
  • Campaigns
    • Creating a campaign
    • Targeting
    • Test sends
    • Delivery
    • Compliance
    • Managing campaigns
    • Campaign analytics
  • Flows
    • Building a flow
    • Templates
    • Triggers & entry
    • Sending messages
    • Waits
    • Branches
    • Contact updates
    • Goals & exits
    • Versions & publishing
    • Managing flows
    • Monitoring
    • Analytics
    • Limits
  • Sequences (legacy)
    • Managing sequences
    • Sequence analytics
Data
  • Audience
    • Contacts
    • Audience table
    • Segments
    • Attributes & events
  • Integrations & data sources
    • Managing sources
    • CSV import
    • API & webhooks
    • Integrations
      • Shopify
      • Klaviyo
      • WooCommerce
      • PrestaShop
      • Magento
      • HighLevel
      • Hotmart
      • ActiveCampaign
      • Zoom
      • Facebook Leads
      • Google Sheets
      • Google Contacts
      • MailChimp
      • MailerLite
      • Intercom
      • Make
      • Zapier
      • Activepieces
      • n8n
      • Pabbly Connect
      • OptiMonk
      • Paperform
      • StockAgile
      • Typeform
  • Consent
    • How consent works
    • Subscription attributes
    • Shared consent
    • Opt-outs
    • Manage via API
Analytics
  • Audience
  • Messages
  • Sales
  • Reports
Settings
  • Project settings
    • Brand profile
    • Senders
    • Short links
    • Unsubscribe links
    • Test numbers
    • Attribution
    • Project memory
  • Developers & Apps
    • API tokens
    • Third-party apps
    • Data access
    • Connected apps
  • Organization
    • General
    • Legal profiles
    • Team
    • Localization
  • Billing
    • Plans
    • Cost calculator
    • Balance
    • Invoices
    • Pricing
    • Account
    • Theme
    • Security
    • Notifications
    • Language & currency
DashboardSupportinstasent.com

Data · Integrations & data sources

Zoom

Connect your Zoom account as a data source: the OAuth authorization, the contacts and meetings it syncs, how its fields map to Instasent attributes, and how meeting events map to consent.

On this page▾
  • How to connect
  • What it syncs
  • Field mapping
  • Consent mapping

Zoom is the native connector for your video-conferencing data. Once authorized, it syncs your Zoom contacts and meetings into Instasent, so the people who attend your meetings and the events they generate become part of your audience without any manual import.

How to connect

Zoom is a native OAuth connector: you authorize Instasent from Zoom and grant the requested permissions in Zoom's own window, and you're connected. There's no key to create or copy anywhere.

  1. 1

    Add the data source

    In Data sources, select Add data source and choose Zoom from the Integrations section.

  2. 2

    Authorize in Zoom

    Select the connect action to open Zoom's authorization window, sign in if needed, and approve the requested access. Instasent asks for read-only permissions on your meetings, reports and users.

  3. 3

    Initial import

    Zoom returns you to Instasent and the source moves to connected. The connector runs an initial import of your existing contacts and meetings, then keeps syncing as changes happen.

The Zoom connector page: what it brings into Instasent and the contact fields it maps, with Connect Zoom to start.

What it syncs

  • Contacts — the people in your Zoom account and your meeting participants, with their name, email and phone.
  • Meetings — your meetings and their activity, which arrive as events available for segments and automations.

Zoom keeps the data current through real-time webhooks and periodic resynchronization, and event types are mapped automatically. The direction is one-way, from Zoom into Instasent. Contacts unify with the rest of your audience by email and phone, the same as any source — see unification.

Field mapping

Zoom contact fields map to the matching Instasent attributes — email to _email, phone to _phone_mobile, name fields to their attributes — and meeting data arrives as events. As with any source you confirm the mapping on setup; see field mapping.

Consent mapping

Zoom does not carry a marketing subscription status for your contacts, so map it to Instasent's marketing-preference attribute (_accepts_marketing_*) following the consent golden rule:

Zoom statusInstasent valueMeaning
Opted intrueAccepted marketing
No statusnullNo preference — never opted in or out
Opted outfalseActively declined marketing

Only an active opt-out becomes false. A contact with no recorded status maps to no preference (null), never to false. For what these values mean for who receives a campaign, see Consent.

Last updated October 8, 2026

PreviousActiveCampaignNextFacebook Leads
  • How to connect
  • What it syncs
  • Field mapping
  • Consent mapping

© 2026 Instasent

Privacy PolicyTerms & ConditionsCookie PolicyLegal Notice
All systems operational