Home/HighLevel/Features/Conversations/How to configure Log External Call in HighLevel

Conversations and Inbox

How to configure Log External Call in HighLevel

In short

The Log External Call workflow action lets a business record calls made through a third party phone system in a contact’s activity feed. By mapping details such as direction, date, numbers, status and recordings, the call shows up alongside native HighLevel interactions.

AreaConversations · Conversations
Used forReal estate agency, Dental practice, SaaS startup
Setup steps20 steps in 1 task
Last updatedNovember 16, 2026

01Who this is for

  • Sales teams that dial out from an external dialer can keep every outbound conversation attached to the right prospect.
  • Customer support centers using a separate call platform can see inbound help calls in the contact timeline.
  • Marketing agencies that schedule reminder calls through a third party service can track those calls in HighLevel for reporting.

02Log external calls, explained

Log External Call is a workflow action that creates a call record in a contact’s Conversations area. The action stores data you map from the workflow, including call direction, timestamp, phone numbers, status and an optional recording reference.

The action works inside a workflow that already has a contact context. A common pattern is to receive call data via an Inbound Webhook trigger, split inbound and outbound flows, identify or create the contact, and then run Log External Call.

You find the action in Automation > Workflows. After adding the Log External Call step, each field displays a custom value picker so you can pull the appropriate webhook values into the call record.

03How businesses use log external call workflow action

  • Real estate agency. The agency routes all client calls through a VoIP provider. It configures the provider to POST call details to a HighLevel Inbound Webhook, then maps those values in Log External Call so each client’s call history includes both inbound inquiries and outbound follow ups.
  • Dental practice. The practice uses an external reminder call service. The service sends call time, status and recording link to the webhook. The workflow creates or finds the patient contact, logs the reminder call and attaches the recording for staff review.
  • SaaS startup. A sales team dials prospects from a third party sales dialer. The dialer posts outbound call data to the webhook. The workflow identifies the prospect by the To number, logs the outbound call, and saves the call recording for later quality checks.

04The numbers and rules that matter

  • International E.164 style phone formatting such as +15551234567 is recommended for contact matching.

05Before you start

  • Access to Automation > Workflows to create or edit a workflow.
  • An external calling system that can send HTTP POST requests to a URL.

06How to set up and use log external call workflow action in HighLevel

Set up Log External Call using an Inbound Webhook

  1. Open Automation > Workflows in HighLevel.
  2. Create a new workflow or open an existing one.
  3. Add the Inbound Webhook trigger to the workflow.
  4. Copy the webhook URL that HighLevel generates.
  5. Configure your external calling system to POST call data to that URL.
  6. Send a sample request from the external system to the Inbound Webhook.
  7. Confirm that HighLevel receives the sample payload.
  8. Review the list of values that the webhook makes available.
  9. Add an If/Else action after the webhook trigger.
  10. Set the condition to evaluate the incoming call direction value.
  11. Create a branch for inbound calls.
  12. Create a branch for outbound calls.
  13. In the inbound branch, map the From number to the Phone field of a Create Contact action.
  14. In the outbound branch, map the To number to the Phone field of a Create Contact action.
  15. Add the Log External Call action after the contact identification step.
  16. Map Direction, Date, To, From, Call Status and Attachment fields to the corresponding webhook values.
  17. Save the Log External Call action.
  18. Test the workflow with representative inbound and outbound payloads.
  19. Verify that the call appears in the contact’s Conversations area with all mapped details.
  20. Publish the workflow once testing confirms the expected behavior.

07What it looks like in HighLevel

08Settings that matter

  • Direction. Specifies whether the logged call was inbound or outbound.
  • Date. Records the exact date and time the call took place.
  • To. Stores the destination phone number for the call.
  • From. Stores the originating phone number for the call.
  • Call Status. Captures the outcome or status reported by the external system.
  • Attachment. Links a compatible recording reference so the call recording can be accessed.

09Things to know before you rely on it

  • Field values must match the formats supported by the Log External Call action; custom dispositions are not automatically converted.
  • Use international E.164 formatting for phone numbers to ensure proper contact matching.
  • The Attachment field works only when the external system provides a recording reference that HighLevel can read.

10If something goes wrong

  • External call does not appear in Conversations. Check the workflow execution logs to confirm the webhook received data, the correct If/Else branch ran, the contact was identified or created, and all Log External Call fields were populated. Refresh the webhook mapping if the payload structure changed.

11How it connects to the rest of HighLevel

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

Adding external call logs is a small convenience that keeps your contact timeline honest. If your team already uses a separate phone service, pulling those calls into HighLevel means no one has to switch screens to see what happened on a call.

A real estate office that routes all inbound leads through a call center platform can map the call data to Log External Call, create the contact on the fly, and have the recording right in the contact record. The first thing I’d do is fire a test payload through the webhook and watch the call show up in Conversations before I let any live leads flow through.

Get More InformationOpens on HighLevelPublished November 2, 2026 · Updated November 16, 2026

Common questions

Common questions about log external call workflow action.

Is an Inbound Webhook required to use Log External Call?

An Inbound Webhook is a common way to supply third party call data, but the action can use any values available in the workflow context.

Does Log External Call need a contact?

Yes. The workflow must have the correct contact context before the Log External Call action runs, typically by identifying, finding or creating the contact first.

Should I use Create Contact or Find Contact?

Use Create Contact when you want the workflow to create or update a contact based on matching rules. Use Find Contact when you need explicit control over how to handle an existing or missing contact.

Can I include a third party call recording?

Yes. Map the compatible recording reference into the Attachment field, then test to confirm the recording is accessible from the logged call.

What should I map into Call Status?

Map the value that represents the system recorded outcome of the call. Do not map a custom disposition unless your integration translates it to the expected status.

Why isn’t the external call appearing in Conversations?

Verify that the webhook delivered the expected data, the correct branch executed, the appropriate contact was identified, and all required fields were mapped. Update the mappings if the external payload changed.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.