Clay Icon
Join the Community
02 Support

Optimizing Gong Calls Filtering with HubSpot Properties

Avatar of Kevin E.Kevin E.
·
·

Hey! I used the new Clay x Gong feature to pull all calls from Gong and already added call details and call transcripts. It would be great if I could find a way to filter the calls based on Hubspot properties (those are either in Hubspot or also in the relevant CRM fields in Gong). For now I have two ideas:

  1. 1.

    Use the lookup object to extract contact information based on call participant's mail adress. Then use the domain from the contact level to lookup the related company level data from Hubspot and pull the properties needed for filtering. Problems: Not sure if I have an unique identifyer for each call with the email plus the for some occassions, the [0] party is our internal rep and not the customer and it would be needed to refer to the mail in the [1] party.

  2. 2.

    Create separate Sheets/Workbooks with a webhook: I thought about creating a webhook in Gong based on my filter criteria and let clay pull that data. Problems: This does not work to pull historical information at a change is needed to trigger the webhook (could be solved with a workaround via a dummy property, but not optimal)

Is there a better solution to pull the relevant HS data? Thanks!

6 comments

  • Avatar of Channeled
    Channeled
    APP
    ·
    ·

    Yes, you can use Hubspot's Lookup Object action to filter your Gong calls more effectively. Here's a better approach: 1. First, use the Lookup Object action to find the Hubspot contact based on the call participant's email address. 2. Then use the same action to find associated company information by setting: • From Object Type: Contact • To Object Type: Company • From Object ID: [ID from first lookup] 3. This will return all company properties that you can use for filtering your Gong calls. This method is more reliable than your proposed solutions because it: ** Uses Hubspot's native association capabilities ** Works with historical data (no webhook limitations) * Handles cases where internal reps are in different positions in the call data You can implement this as a multi-step enrichment process in your Clay table.

  • Avatar of Kevin E.
    Kevin E.
    ·
    ·

    How can I ensure that the right email address is used (the client's one, not the internal one)?

  • Avatar of Kevin E.
    Kevin E.
    ·
    ·

    For some calls, the relevant mail is in 0, for others in 1

  • Avatar of Channeled
    Channeled
    APP
    ·
    ·

    To handle cases where the client email might be in either position 0 or 1 of your Gong call data, you can use a formula column in Clay to determine which email to use before looking up Hubspot data: 1. Create a formula column that checks both positions and identifies the client email: LBKSIF(CONTAINS(email_position_0, "[[yourcompanydomain.com](http://yourcompanydomain.com)]([https://yourcompanydomain.com](https://yourcompanydomain.com))"), email_position_1, email_position_0)LBKS2. Use this formula result as input for your Hubspot Lookup Object action, setting: • Object Type: Contact • Field to filter by: Email • Filter Field Input: Your formula column 3. Once you have the contact, use another Lookup Object action to find the associated company: • From Object Type: Contact • To Object Type: Company • From Object ID: ID from first lookup This approach ensures you're always using the client's email regardless of its position in the Gong data.

  • Avatar of Kevin E.
    Kevin E.
    ·
    ·

    For Step 3 -> I do not see the "To Object Type" Option

  • Avatar of Channeled
    Channeled
    APP
    ·
    ·

    It sounds like you're using the "Lookup Object" action instead of the "Retrieve associated objects" action. To find associated company information from a contact: 1. Use the "Retrieve associated objects" action in Clay (not "Lookup Object") 2. Select your Hubspot account 3. Set "From Object Type" to Contact 4. Set "To Object Type" to Company 5. Enter the Contact ID in the "From Object ID" field This action specifically retrieves associations between objects, like finding companies linked to a contact. The "Lookup Object" action is for finding a single object by ID, while "Retrieve associated objects" is for finding relationships between objects.