Zapier 2 8 0 Update Dial Session Trigger and contact search

✅ Summary

Zapier 2.8.0 Update for the PhoneBurner App

This video outlines the four key updates included in the 2.8.0 release of the PhoneBurner Zapier app. These updates expand automation capabilities, particularly for real-time and conditional data handling:

1. New Trigger: All Dial Session Data
   A new Zapier trigger fetches dial session data in near real-time. For team admins, this includes sessions from the entire team. While webhooks are still recommended for true real-time data, this trigger provides an alternative when webhooks aren't an option (e.g., for Salesforce or Zoho users).

2. Search Contact by Email or Phone
   A new search action allows users to look up PhoneBurner contacts by email address or phone number. Only the first matching contact will be returned, making it ideal for systems where contact identifiers are unique.

3. Get Contact by Contact ID
   Users can retrieve a specific PhoneBurner contact using the contact ID. This is useful for syncing status updates or managing data between PhoneBurner and external systems like CRMs.

4. Zap Example Demonstration
   The speaker demonstrates these updates through a Zap that logs dial session data into a Google Sheet. This highlights how users can integrate PhoneBurner with other systems for improved workflow automation.

These updates aim to enhance data access and integration options for more efficient team operations using the PhoneBurner app in Zapier.

🏷️ Tags

Zapier, integration, dial session, contact search, contact ID, CRM sync, team admin, real-time data, automation, webhooks, PhoneBurner app, version 2.8.0, trigger, Google Sheets

📝 Cleaned-Up Transcript

Let me introduce you to the Zapier 2.8.0 update for the PhoneBurner app. There are four updates included in this release, and I’ll walk you through each of them to help you understand their purpose and how you might use them.

On the screen, you’ll see a Zap I created to test this version. I’m using all four of the updates in the Zap to demonstrate them in action.

1. New Trigger: All Dial Session Data

We’ve added a new trigger that allows you to pull all of your dial session data as calls are being made. If you’re a team admin, it will include dial session data from your entire team. Keep in mind, this only works from the time the Zap is activated—it's not retroactive. This enables near real-time visibility into call activity.

Previously, customers used webhooks to get real-time call data from PhoneBurner. Webhooks are still highly recommended because they work without polling and provide immediate updates. You can set these up in the integration section of your PhoneBurner account. You can enter a webhook URL under the "call end" option to send contact and call details when a call is completed. You can also configure webhooks for specific dispositions to only trigger under certain conditions.

However, in cases where webhooks aren’t ideal—like when you’re already using them for integrations with Salesforce, Zoho, or other systems—you can use the new “All Dial Session Data” trigger in Zapier. This will poll for updates based on your Zapier account level (every 2, 5, or 15 minutes). It checks for new activity since the last poll and returns call details like contact info, start/end time, notes, and custom fields.

In my example, I’m logging this data to a Google Sheet for testing, but it can be used to update any external system.

2. Search Contact by Email or Phone

The next update is a search step that allows you to look up contacts in PhoneBurner by email or phone number. This is useful when pushing data to PhoneBurner and checking if a contact already exists. Note that if multiple contacts match, only the first one found will be returned. It’s important to ensure unique identifiers for best results.

In the demo, I created two action steps—one for email and one for phone—to test them independently. But when creating your Zap, you’ll use one search step and choose the criteria.

3. Get Contact by Contact ID

Another new action allows you to retrieve a contact by their PhoneBurner contact ID. This is helpful if you store the contact ID in your CRM or database. For example, you might import new leads into PhoneBurner and want to later check the current status of those contacts. With the contact ID, you can fetch up-to-date details like name, folder, notes, and more.

This is particularly useful for systems syncing data back and forth with PhoneBurner to ensure data consistency.

4. Recap

These four updates make the PhoneBurner app in Zapier more versatile:

• You can use dial sessions as triggers to update external systems in near real-time.

• You can search for contacts by email or phone.

• You can fetch a specific contact by ID.

Thanks for watching! I hope these updates help your organization get more done in less time using the power of PhoneBurner.

Happy dialing!