When an external call recording is received in GHL (for example via Zapier or Twilio), the current trigger fires as soon as the call begins and a recording object is created. At that moment, the Twilio recording is still in a "processing" state and the actual audio file is not yet available to be retrieved. Because the trigger activates too early, automations cannot reliably fetch the recording URL, which results in errors, delays, and the need for unnecessary workarounds.

Technical explanation:

Twilio sends an initial webhook at the start of the recording, but the recording is not ready until Twilio later updates the status to "completed". The GHL trigger listens only to the initial webhook, not to the completion event. As a result, the system reacts at the wrong time.

Requested improvement:

GHL should trigger the call recording event only once the recording status changes to "completed", or alternatively provide a dedicated trigger such as "Call Recording Completed". This would ensure that the recording file is fully available when automations run, eliminating the need for delays or repeated polling in Zapier or other integrations.

This change would make call recording workflows far more reliable and consistent across all call types.