Contact Activity Webhooks in PhoneBurner

📄 Summary:
This training video demonstrates how to set up and use activity-based webhooks in your PhoneBurner account. By enabling these webhooks, users can send real-time notifications to external systems (like CRMs or automation platforms) when specific actions occur within a contact's record. The tutorial walks through creating a webhook in PhoneBurner's integration settings, using Zapier to capture and test these events (such as emails sent, calls logged, voicemail logged, SmartSender interactions, and appointments scheduled), and then using Zapier to log that data into an external Google Sheet. The video also explains how to fetch full contact details from PhoneBurner using the contact ID and how to build conditional paths in Zapier based on different activities. This enables more sophisticated automations like updating CRM records or triggering external alerts.

🏷️ Tags:
webhooks, activity logging, integrations, Zapier, contact tracking, automation, CRM sync, SmartSender, inbound calls, appointment scheduling, contact activities, PhoneBurner settings, external systems, Google Sheets, custom workflows, call tracking

🧹 Cleaned-Up Transcript:

Look at all this activity associated with this specific contact. Wouldn't it be nice to be able to trigger a webhook on some of these activities so that you can get notified—or your external systems could get notified—about specific actions being taken? Well, you're in luck! In this training, I'm going to show you how you can trigger a webhook when certain activities are logged to a specific contact. It's super easy to do. So, let's get into it.

From your PhoneBurner account, go to the upper right-hand corner and click on the settings menu. Typically, you'll see your initials there, unless you’ve uploaded an image. I’m going to open the Integrations page in a new tab—I'll hold down Control and click "Integrations" so I can bounce between tabs more easily.

On the Integration Settings page, click “Webhooks” on the left-hand side. Here, you’ll see a list of the different webhook options PhoneBurner currently offers. Scroll down to the Automated Activity Webhooks section. What we’re interested in is Contact Activities.

Just enter the webhook URL—this is where PhoneBurner will send the payload whenever any of the selected activities are logged for that specific contact. Everyone’s webhook URL will be different. For this demo, I’ll use Zapier.

In another tab, I’ve opened Zapier and started a new Zap. For the trigger, choose Webhook and for the trigger event, choose Catch Hook. Skip the “Pick off a Child Key” option (sounds a bit harsh, doesn’t it?). Proceed to the test step to get your webhook URL, then copy it.

Now back in PhoneBurner, paste the webhook URL into the Contact Activities section.

Let’s decide which activities should trigger the webhook. Under Email, you can trigger when an email is sent, clicked, opened, or when someone resubscribes. Under SmartSender, you can trigger on SmartPack pickup, link pickup, document pickup, or image pickup. I’ll choose SmartPack Pickup.

In the Dialing section, you can trigger when a call is placed or transferred. I’ll select Call Transfer.

Under Inbound, you can trigger when an inbound call or voicemail is logged. I’ll check Voicemail.

For Manually Logged Activities, options include manually logged emails (sent or received), replies, calls, and “Other.” I’ll select all four so I can demo those for you.

Lastly, under Other, I’ll check Appointment Scheduled.

Now, hit “Save Changes.” Remember, you don’t have to select every option—just what matters for your workflow.

Let’s test this setup. Go back to a contact record and log a manually logged email activity. Select “Log Activity,” choose “Email,” and click “Save.”

Jump back to Zapier and click Test Trigger. You should now see data sent from PhoneBurner. You’ll see the activity code, timestamp, message, the user who performed the action, and the associated contact. If you’re using external CRM data or lead ID, those will be included as well.

Let’s log another activity: a call. Back in PhoneBurner, log a call under “Activity.” Refresh in Zapier and you'll see it’s been triggered. Again, the payload gives enough information to find the full contact record via API if needed.

Let’s try an “Other” activity. When logging it, you can include a comment. Once logged, that activity appears in the feed, but the custom comment is only visible within PhoneBurner—it's not in the webhook payload.

Now, let’s send an email and include a SmartSender video. After sending, check the activity feed—it shows a one-click email was sent. Go to your inbox, click on the SmartSender video link, and you'll see the SmartPack pickup trigger fire. Refresh Zapier, and you’ll see it was captured.

Let’s schedule an appointment. Don’t worry that I scheduled it in the past—it’s just for demo purposes. Refresh Zapier again, and the appointment-scheduled activity will eventually appear (Zapier might take a moment).

Why is this useful? Because the webhook provides the activity event code and message, you can filter these events in Zapier. For example, you can create different Paths in Zapier. Path A might trigger on "Appointment Scheduled." You set the condition to “Exactly Matches” and input “Appointment Scheduled.” Once matched, you can route that event through its own set of actions.

But what if you need more contact info? No problem. Use the PhoneBurner app in Zapier to “Get a Contact.” Use the contact ID from the webhook payload to fetch full contact details like name, phone number, notes, etc.

Let’s go further and log this in Google Sheets. I’ve created a new sheet tab called “Activities.” Fields include Contact Name, Contact ID, Lead ID, Notes, and Activity Event. These fields can be mapped from the webhook and the API response.

Now in Zapier, choose “Create Spreadsheet Row,” select your Google Sheet and worksheet, and map your data. Once you test the step, you should see your new row added to the sheet.

Let’s repeat the process for another path—Path B—this time for SmartPack Pickup. Same steps: set the condition to match that event code, fetch the full contact from PhoneBurner, and log the data into the Google Sheet. Don’t forget to include the event name or code so you know what triggered it.

Be sure to rename your paths (e.g., “Appointment Scheduled” or “SmartPack Pickup”) to keep things organized. Publish your Zap, and now anytime those activities occur, they will trigger your desired workflow.

Of course, you don’t have to use Zapier—this is just one example.

So, as you can see, it’s super easy to start using activity-based webhooks in PhoneBurner. Anytime a selected activity is logged, you can push that information into external systems or notify your team.

Thanks for watching—and happy dialing!