Connectors

/

Chorus

/

Log Chorus emails on the HubSpot timeline
Write
Cross-Connector

Add Chorus emails to the HubSpot company timeline

For sales teams who want the emails Chorus captured with an account visible in HubSpot, by asking their AI assistant to log them.

Try PopdockAI free
Get a live demo
Log Chorus emails on the HubSpot timeline
Log the Chorus emails with Contoso from the last two weeks on HubSpot.
I found Contoso in HubSpot and 11 Chorus emails from the last 14 days; 2 private emails were left out. - 1. 2026-10-20, sent, Revised proposal, company only - 2. 2026-10-22, received, Re: Revised proposal, from Priya Shah - 3 to 6: four more, sent and received - Already logged: 3 Which should I log: numbers, all or none?
Chorus
Sample figures. Your results come from your own account.
hubspot-get-companies
chorus-get-emails
hubspot-get-contacts
hubspot-get-emails
hubspot-add-email
hubspot-add-engagement-email
hubspot-add-contact
hubspot-add-note

On this page

The problem

The problem

The prompt

Who it's for

How it works

Tools used

Connector

Chorus

Chorus
Run it on your own Chorus data.

Connect Chorus, pick your AI tool and paste the prompt.

Try PopdockAI free

The problem

Account emails captured in Chorus never reach HubSpot

Chorus captures emails with your accounts, but they do not show on the HubSpot company timeline unless someone logs them. Doing it by hand means working out direction, finding the contact, avoiding private emails and checking for ones already logged.

Without PopdockAI

  • Find the HubSpot company for the account
  • Work out which emails were sent or received
  • Leave out private emails
  • Check each one is not already logged

With PopdockAI

  • The one matching HubSpot company is found, never created
  • Chorus emails are read and private ones dropped
  • Direction is set and senders matched to contacts
  • Only emails you choose are logged and checked

The prompt

Use this prompt

Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.

Prompt
**Objective:** Log the emails Chorus captured with the account {account-name} over the last {lookback-days} days (default 14) onto the HubSpot timeline of the matching company and contacts, after I approve them. This only records emails that already happened; it sends nothing.

**Step 1: Find the company in HubSpot**

Call `hubspot-get-companies` with company-name = {account-name}, then company-name.contains with its distinctive part if nothing matched. If several match, list them (record-id, company-name, domain) and stop for me to choose. If none match, say so and stop; do not create one. Keep the record-id and domain.

**Step 2: Read the emails in Chorus**

Call `chorus-get-emails` with account-name.contains = the distinctive part of {account-name} and sent-time.from = today minus the lookback days. Drop emails whose private flag is true and list them only as a count. Keep email-id, name (the subject), sent-time, initiator-name, initiator-email, owner-email and body. If nothing comes back, say so and stop.

**Step 3: Direction and contacts**

An email whose initiator-email is the rep's owner-email, or on the rep's domain, was sent (direction EMAIL); otherwise it was received (direction INCOMING_EMAIL). For a received email, call `hubspot-get-contacts` with email = the initiator-email and keep the record-id if one matches. Chorus does not return recipients, so a sent email is associated with the company only.

**Step 4: Skip what is already logged**

For each email, call `hubspot-get-emails` with email-subject = the subject and activity-date.from / activity-date.to = the day before and the day after the sent-time. If a returned email has the same subject and email-from-address, it is already logged; drop it.

**Step 5: Review**

Show a numbered table: sent-time, direction, subject, from, and the company and contact it will be associated with. Ask which to log, by number, "all" or "none". Write nothing until I answer.

**Step 6: Log the approved emails**

For each approved email, call `hubspot-add-email` once with timestamp = the sent-time date, subject, direction, status SENT, from-email = the initiator-email, body = the email body (trimmed to 2,000 characters, ending with "Captured by Chorus, email <email-id>"), company-ids = the company record-id and contact-ids = the matched contact record-id if any. Report each returned id, then repeat the Step 4 read and confirm it appears.

**Rules & Guidelines:**

* `chorus-get-emails` is on the Chorus server. `hubspot-get-companies`, `hubspot-get-contacts`, `hubspot-get-emails` and `hubspot-add-email` are on the HubSpot server.
* `hubspot-add-email` only logs the email on the timeline; it does not send it. Say so if I ask to send anything.
* The only write is `hubspot-add-email`, once per approved email. Call no other write tool: no other hubspot-add, hubspot-update, hubspot-rename, hubspot-remove, hubspot-subscribe, hubspot-unsubscribe or hubspot-import tool (including `hubspot-add-engagement-email`, `hubspot-add-contact` and `hubspot-add-note`).
* Never call a Chorus write tool (`chorus-add-moment`, `chorus-update-moment`, `chorus-add-playlist-moment`, `chorus-update-playlist-moment`, `chorus-create-playlist`, `chorus-update-playlist`, `chorus-export-recordings`, `chorus-export-scorecards`).
* Never log an email Chorus marks as private.

**Validation:**

* If an email body is empty, log the subject and date only, and say so.
* If a write fails, report it and continue with the next email; do not retry it.

Who it's for

One answer, three teams that use it

Account executives

Show the full email trail on the account

Emails with the account appear on the timeline, so anyone picking it up sees the history.

Log the Chorus emails with Fabrikam from the last month on HubSpot.

Customer success managers

Keep handovers complete

Before handing over an account, make sure the email history is on the HubSpot timeline.

Log all Chorus emails with Northwind Traders this quarter on their HubSpot company.

Revenue operations

Log emails without duplicates

Emails already on the timeline are skipped and private ones are never logged.

Log Chorus emails with Contoso since October 1 on HubSpot, skipping any already logged.

How it works

What PopdockAI does when you ask

You name the account and your AI assistant lines up its Chorus emails for the HubSpot timeline. Emails are logged, not sent, and nothing is written until you choose.

01

Find

It finds the HubSpot company for the account you name.

Your AI tool

02

Read

It reads the Chorus emails with that account and drops private ones.

chorus-get-emails

03

Check

It sets each email's direction, matches the sender, and skips ones already logged.

hubspot-get-contacts
hubspot-get-emails

04

Review

You choose which to log, then it logs them and checks each appears.

Your AI tool

What PopdockAI provides

The tools behind the answer

Ready made tools for Chorus and one secure connection to your AI tool. No code, no exports.

get-data

hubspot-get-companies

Returns company records from HubSpot CRM, with domain, industry, lifecycle stage, owner, location and revenue from the HubSpot connector. Filter by record id, company domain name, industry, lifecycle stage, annual revenue, state region, company owner, company name, create date, country region.
get-data

chorus-get-emails

Returns emails captured by Chorus, including the subject, body, sender, owner, account and sent time. Filter by account or date range to read the written trail alongside the calls.
get-data

hubspot-get-contacts

Returns contact records from HubSpot CRM, with email, phone, company, lifecycle stage, lead status, owner and location from the HubSpot connector. Filter by company id, state region, contact owner, email, last name, create date, company name, record id, lifecycle stage, lead status.
get-data

hubspot-get-emails

Returns one-to-one sales emails logged in HubSpot, with subject, direction, status, sender, recipients and associated records from the HubSpot connector. Filter by email to address, contact id, email from address, email send status, email subject, activity date, email direction, activity assigned to.
run-action

hubspot-add-email

Logs an email in HubSpot's activity timeline (it does not send the email) and returns the new email's ID. Required: Date. Optional: Subject, Body, Direction, Status, To, From, Owner ID, Company IDs, Contact IDs, Deal IDs. Writes to HubSpot.
run-action

hubspot-add-engagement-email

Logs an email in HubSpot's activity timeline (it does not send the email) and returns the new engagement email's ID. Required: Date. Optional: Subject, Body, Direction, Status, To, From, Owner ID, Company IDs, Contact IDs, Deal IDs. Writes to HubSpot.
run-action

hubspot-add-contact

Creates a contact in HubSpot and returns the new contact's ID. Requires email. Optional: phone, last name, company name, first name, lead status, lifecycle stage, owner id, job title.
run-action

hubspot-add-note

Creates a note in HubSpot and returns the new note's ID. Required: Date. Optional: Note, Owner ID, Company IDs, Contact IDs, Deal IDs. Writes to HubSpot.
Read only.Nothing in Chorus Changes

This report is built from Get data tools only. PopdockAI applies the row, field and parameter rules your admin sets, and every query is written to the audit trail.

How Popdock AI secures your data

The outcome

Account email history on the HubSpot timeline

Try PopdockAI free
Get a live demo

Related use cases

More ways to put this data to work

All Ramp use cases

One prompt template with infinite possibilities.

‍

Your AI assistant adapts its approach, tone, and capabilities to match each unique context while you maintain a single, manageable workflow.

Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.

Try PopdockAI Free
See Documentation