Zapier setup guide

Before you connect

• A Burki workspace administrator account, a Zapier account and access to the private Burki app invitation shown in Integrations.
• Choose an assistant you own and the events you intend to share. Your workspace privacy settings must permit Zapier access, and event delivery must be active on the deployment.
• Outbound calls additionally need explicit key permission, a configured calling number, an assistant ready for live calls, sufficient balance and an authorized recipient. Normal calling charges apply.

Review Burki usage pricing and your provider’s plan before a live test. Telephone calls, phone numbers and optional SMS can add charges; this guide does not promise a free provider plan.

Access and permissions

A connection key grants access within its Burki workspace. Create a named key for the connection, store it securely and never put it in Zap step data or an assistant prompt.

Call analysis, appointment and callback events can share customer phone numbers, call summaries, extracted fields, booking details or a callback reason. Select only the assistant and events your workflow needs.

Allow outbound calls is a separate key permission and starts off unchecked. You can change it without replacing the key. A key alone does not turn on a Zap.

Connect and configure

1. Open the private app invitation

   In Burki Integrations, choose Zapier and Open Burki in Zapier. Accept the private app invitation in the intended Zapier account.

2. Create and save a connection key

   Back in Burki, name the key and choose Create key. Leave outbound permission off for event-only workflows. Copy the key when it is shown once, then paste it only into Zapier’s Burki account connection. Test the connection.

3. Choose the workflow

   For a trigger, choose Call Analysis Ready, Appointment Booked or Callback Requested, then select the assistant. Appointment Booked requires a confirmed Cal.com booking. Callback Requested requires the callback action on the assistant and the caller’s confirmed callback details.

4. Configure searches or outbound actions

   Find Call searches for an existing call using an exact customer phone number and an optional assistant; no match can return an empty result. Start Outbound Call needs outbound permission and a stable request ID for that intended call. Do not change the ID just to retry an uncertain request.

5. Test, then publish the Zap

   Map only the fields your destination needs. Editor samples and simulated outbound tests do not place a real call. Publish and turn on the Zap when ready, then verify an authorized real event or call in both Burki and Zapier’s run history.

Test the workflow

The editor can display example data when no real event exists. A successful sample test does not prove that a live event was exported or a phone call was placed.

Use Recent delivery activity in Burki to inspect saved event and subscription states. Its date filters refer to when events were created. Accepted means Zapier received an event, not that every later Zap step completed. Check Zapier’s run history for downstream results.

Find Call returns an existing call and available analysis; it does not generate missing analysis. A call’s analysis can arrive after the call ends.

Troubleshooting

The Burki app or invitation is missing

Open the invitation from the same workspace and Zapier account you plan to use. If Burki shows no invitation, contact support. Do not choose an unrelated app with a similar name.

No live trigger events

Confirm the Zap is on, the subscription is active, the assistant matches and deployment delivery is enabled. Check workspace privacy restrictions. A browser practice call or static sample is not a live event.

An outbound call is blocked

Check the key’s Allow outbound calls setting, workspace access, calling number and balance. Confirm the recipient is authorized before trying a live call. An uncertain existing request should be checked before creating a new request ID.

Burki says accepted but the destination is empty

Open the Zap’s run history and inspect subsequent steps, field mappings and destination permissions. Burki’s acceptance status does not prove downstream completion.

The connection no longer authenticates

Check whether the key was revoked or workspace privacy settings changed. Revoked keys cannot be restored; create a replacement and update the affected connection only if access should continue.

Disconnect safely

1. Turn off affected Zaps in Zapier to stop the automations.
2. Revoke the key in Burki Integrations to remove that connection’s access. Any Zap sharing the key is affected. Remove the saved connection in Zapier when no longer needed.
3. To stop only new outbound requests, turn off Allow outbound calls on the existing key. Calls already being placed may finish. Revoking a key does not erase data already delivered to Zapier or its destination apps.

Data and support

Only the selected workflow’s eligible events are exported. Data already sent is subject to Zapier and destination-app settings as well as Burki’s policy. Manage those copies separately; disconnecting does not retract previous exports or delete Burki call records.

Burki’s privacy policy explains retention and data requests. Your workspace settings and applicable terms govern your account. Disconnecting an integration is separate from requesting deletion. See the terms of service for service conditions.