NEON DEER DATA LABS Search documentation...

neondeerdata.com

Zoom Phone (VoIP) Integration for Attio

Sync selected Zoom Phone calls, SMS and recording events into Attio. Meeting-created metadata and historical reads can be included in the configuration.

Requirements

A Zoom tenant with Zoom Phone enabled, an approved account for OAuth authorization and app configuration, and an Attio workspace for the custom app.

Setup

If the integration is not installed in your workspace, request setup.

  1. Choose events and fieldsConfirm the Zoom tenant, Phone license, event coverage, Attio destination and matching rules.
  2. Authorize the Zoom appGrant the scopes needed for the selected call, SMS, voicemail or recording data.
  3. Validate the webhook endpointConfigure the delivery endpoint and complete Zoom's URL validation.
  4. Subscribe to eventsEnable the agreed Phone events and meeting.created when included.
  5. Install the custom Attio appThe app creates the destination object, mapped fields and any resync actions.
  6. Start live syncSubscribed events update Attio. Historical reads and reconciliation run separately when configured.

Configuration

SettingConfiguration
Tenant and accessZoom account, Phone license and approved app administrator.
EventsPhone events and optional meeting-created events to receive.
Attio destinationObject for call, SMS, recording and meeting data.
Field mapTimestamps, identifiers, phone numbers, available user IDs and event-specific fields.
Direction and numbersCaller/callee rules, tenant numbers for fallback matching and phone-number formatting.
Recordings and transcriptsRecording links, voicemail and transcript data to include.
Support actionsRecord and bulk resync, configuration refresh and reconciliation.

Sync behavior

Event updates

Subscribed call-status, SMS and recording events update the configured Attio object. Stable call, message and recording IDs identify existing records on repeat deliveries.

Recorded fields

Fields can include timestamps, direction, caller and callee numbers, available user IDs, recording links and SMS content. Meeting metadata is included when meeting-created events are configured.

Direction

SMS direction follows the sent or received event. Call direction uses caller and callee user IDs when available, with configured tenant phone numbers as a fallback.

Limitations

  • Zoom Phone must be enabled on the tenant.
  • Historical records are retrieved separately through Zoom Phone APIs. There is no documented Phone webhook replay path.
  • Caller and callee user IDs are not present on every event. Phone-number fallback rules are needed for direction.
  • Events and permissions are configured in the Zoom app, rather than toggled inside Attio.
  • Linking call records to Attio People by phone number requires a separate workflow or configured matching step.

Troubleshooting

Phone events stopped arriving

Check the Zoom event subscription and endpoint validation. Zoom can disable subscriptions after repeated validation failures.

Calls are not linked to People

Check whether a phone-matching workflow was included. Storing a call record does not automatically link it to an Attio Person.