waveline

Integrations

Waveline for Zapier

Use Waveline triggers and actions in Zapier to connect calls, messages, and contacts to your other apps. The Waveline integration is available through the invitation linked from your Waveline environment.

Connect Zapier

  1. Open Settings > Integrations > Add integration > Zapier in Waveline.
  2. Select Connect Zapier and accept the invitation for the Waveline app shown.
  3. Create a Zap, choose that Waveline app, and sign in to Waveline.
  4. Select the available inbox or inboxes on Waveline’s authorization page. Only workspace Owners can turn on Entire workspace. Review the requested permissions and approve access.
  5. Finish setting up the Zap in Zapier. Refresh Waveline's integrations list to see the authorized connection.

If the connection button is unavailable, contact Waveline support. Owners and Admins can connect shared inboxes; workspace Members can connect their own personal inbox and shared inboxes where they are a Manager. Use the app linked from Waveline so the Zap connects to the intended account environment. See API access and permissions for activity and contact visibility; Zapier’s consent page can offer multiple permitted inboxes.

Build an automation

Waveline triggers include completed calls; recording, transcript, and summary readiness; received messages; delivered or failed messages; and contact creation or updates. Actions and searches let you find, create, or update contacts, add notes, send messages, read call and message history, and retrieve existing recordings, transcripts, or summaries. Choose the destination app’s action to create a CRM activity, support ticket, or notification.

For example, use a completed Waveline call to add an activity to a matching CRM contact. Review sample data and contact matching before enabling the Zap. Multiple contact matches require an explicit choice rather than using the first result.

Workspace activity includes current and future shared and personal inboxes. Workspace contact access includes workspace-visible contacts only; contacts restricted to either kind of inbox remain restricted. An inbox connection receives only its permitted call interactions, and messages require the entire conversation to be in scope. Internal-only activity is excluded.

Use recordings, transcripts, and summaries

Call Completed means the call ended; it does not mean its recording, transcript, or summary is ready. Start with Call Recording Ready, Call Transcript Ready, or Call Summary Ready when the next step needs that content. Use the trigger’s Recording Type filter when you need call recordings or voicemail specifically.

Map Recording ID to Get Recording, Get Call Transcript, or Get Call Summary. Recording ID and Call ID are different. Use Get Call Recordings with a Call ID when you need to find the recordings attached to that call.

These steps retrieve existing content; they do not create a transcript or summary. A recording can be unavailable even when the connection can read the call. Get Recording returns a temporary download link; retrieve it again if the link expires and share it only with an authorized destination.

Read a page of history

Use Get Call History or Get Message History with the inbox, number, and date filters you need. Maximum Results accepts 1–100 records per step. If the result includes Next Page Cursor, pass it to the next history step with the same filters and maximum results to continue. A single page may not include all matching activity.

Request IDs and duplicate prevention

Map each write action's Request ID to a stable source event ID, or a source record ID combined with its change version. Keep it unchanged for retries and use a new value for each intended change. Reusing an ID with different inputs causes a conflict.

For contact and note changes, retry the original request within seven days; after that, check the existing record before creating it again. A retry of an accepted message send with the same Request ID does not send or charge again. Separate Zaps or connections can still act on the same event, so avoid overlapping automations that send the same message twice.

Message fees

Each external recipient send accepted by Waveline costs US$0.01 before tax, added to the workspace subscription invoice. Normal messaging charges may also apply. The fee applies even if delivery later fails; retries of the same send do not add another fee. Reading or logging existing activity has no integration sending fee.

Choose an authorized sending inbox with a registered number and an active billed subscription. Review recipient and message mappings before testing a sending action: an accepted test send is billable too.

Manage the connection

Manage and pause your Zaps in Zapier. Use Waveline's integration details to inspect the connection and its delivery history. Deleting the Waveline integration stops its access while preserving existing records and billing history. Deleting it does not cancel messages Waveline has already accepted for sending.