Connectors

/

Chorus

/

Turn Chorus next steps into HubSpot tasks
Write
Cross-Connector

Turn Chorus call next steps into HubSpot tasks

For sales reps who want the next steps from a Chorus conversation tracked in HubSpot, by asking their AI assistant to create the tasks.

Try PopdockAI free
Get a live demo
Turn Chorus next steps into HubSpot tasks
Create HubSpot tasks for the next steps from my Chorus call with Contoso yesterday, conversation 48213.
The Chorus summary for Contoso pricing review, 2026-10-29, has 4 next steps. - 1. Send revised pricing, you, due 2026-10-31, EMAIL, MEDIUM - 2. Follow up with Priya Shah on security review, due 2026-11-03, TODO, HIGH - 3. Book technical deep dive, you, due 2026-10-31, CALL, MEDIUM - Already tracked: Share case study All link to Contoso, the Contoso expansion deal and Priya Shah. Which should I create: numbers, all or none?
Chorus
Sample figures. Your results come from your own account.
chorus-get-engagements
chorus-get-conversation-participants
hubspot-get-companies
hubspot-get-deals
hubspot-get-contacts
hubspot-get-tasks
hubspot-add-task
hubspot-add-engagement-task
hubspot-update-deal
hubspot-add-deal-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

Next steps agreed on calls get missed

Next steps agreed on a call live in the Chorus summary, and turning them into HubSpot tasks means deciding who owns each one and linking it to the company, deal and attendees. Steps get missed, or become a second task for something already tracked.

Without PopdockAI

  • Read the summary for next steps
  • Decide who owns each one
  • Link each task to company, deal and contacts
  • Create a second task for something already tracked

With PopdockAI

  • Each next step is listed with its owner and any date
  • No step is invented beyond the summary
  • Company, deal and contacts are matched and tracked steps dropped
  • Only tasks you choose are created 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:** Turn the next steps agreed on Chorus conversation {conversation-id} into HubSpot tasks associated with its company, deal and customer-side attendees. Steps with no stated date are due {due-in-days} days after the conversation (default 2). Nothing is written until I approve the list.

**Step 1: Read the conversation in Chorus**

Call `chorus-get-engagements` with conversation-id = {conversation-id}. If nothing comes back, say so and stop. Keep date, subject, account-name, opportunity-name, user-name and meeting-summary. Call `chorus-get-conversation-participants` with conversation-id = {conversation-id} for the attendees.

**Step 2: Extract the next steps**

From the meeting-summary, list each next step, commitment or follow-up, with who owns it and any date stated. If the summary states none, say "No next steps in the Chorus summary" and stop.

**Step 3: Find the records in HubSpot**

* Call `hubspot-get-companies` with company-name = the account-name, then company-name.contains with its distinctive part. If none or several match, say so and continue with no company.
* If there is an opportunity-name and a company, call `hubspot-get-deals` with company-id = the record-id and deal-name = the opportunity-name (then deal-name.contains). Use the deal only if exactly one matches.
* For each external participant with an email, call `hubspot-get-contacts` with email = that email and keep the record-id.

**Step 4: Check for existing tasks**

For each step, call `hubspot-get-tasks` with task-title.contains = a distinctive word from the step and contact-email = the related attendee's email if there is one. Drop steps that already have an open task and list them as "Already tracked".

**Step 5: Review**

Show a numbered table: subject, owner, due-date, priority (HIGH only if the call called it urgent, otherwise MEDIUM), type (CALL, EMAIL or TODO), and the company, deal and contacts it will be associated with. Steps the customer owns become "Follow up with <name> on <step>". Ask which to create, by number, "all" or "none". Write nothing until I answer.

**Step 6: Create the approved tasks**

For each approved step, call `hubspot-add-task` once with subject, body (the step, the owner, and "From Chorus conversation <conversation-id>, <date>, <subject>"), due-date as an ISO date, status NOT_STARTED, priority, type, and company-ids, deal-ids and contact-ids as comma-separated record-ids. Report each returned id, then call `hubspot-get-tasks` with task-title.contains = the subject and confirm it exists.

**Rules & Guidelines:**

* `chorus-get-engagements` and `chorus-get-conversation-participants` are on the Chorus server. `hubspot-get-companies`, `hubspot-get-deals`, `hubspot-get-contacts`, `hubspot-get-tasks` and `hubspot-add-task` are on the HubSpot server.
* The only write is `hubspot-add-task`, once per approved step. 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-task`, `hubspot-update-deal` and `hubspot-add-deal-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`).
* Do not set owner-id unless I give a numeric HubSpot owner ID; the owner's name goes in the body. Never invent a next step that the summary does not state.

**Validation:**

* If no HubSpot company matches, the tasks can still be created unlinked; say they will not appear on any record and ask before creating them.
* If a create fails, report it and continue with the next step; do not retry it.

Who it's for

One answer, three teams that use it

Account executives

Turn calls into a task list

Every next step lands as a task on the right records, so nothing agreed is forgotten.

Create HubSpot tasks for the next steps from today's Chorus call with Fabrikam.

Customer success managers

Track what customers owe you

Steps the customer owns become follow-ups, so you chase them on time.

Turn the next steps from the Northwind Traders onboarding call in Chorus into HubSpot tasks.

Sales managers

Avoid duplicate tasks

Steps that already have an open task are dropped, so task lists stay clean.

Create HubSpot tasks from Chorus conversation 7731 for Contoso, skipping anything already tracked.

How it works

What PopdockAI does when you ask

You give the Chorus conversation and your AI assistant turns its next steps into proposed HubSpot tasks. Steps the customer owns become follow-ups for your team, and nothing is written until you choose.

01

Read

It reads the Chorus conversation summary and attendees.

Your AI tool

02

Extract

It lists each next step with its owner and any date stated.

No items found.

03

Match

It finds the HubSpot company, deal and contacts, and drops steps already tracked.

hubspot-get-companies
hubspot-get-deals
hubspot-get-contacts
hubspot-get-tasks

04

Review

You choose which to create, then it creates them and checks each exists.

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

chorus-get-engagements

Returns recorded calls and meetings from Chorus, with the subject, date, duration, participants and the account each conversation relates to. Filter by date range, owner or account to pull the conversations behind a deal or a period.
get-data

chorus-get-conversation-participants

Returns the people who took part in Chorus conversations, with their name, email, title and company. Use it to see who was on a call, and which side they were on.
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

hubspot-get-deals

Returns deals from HubSpot CRM, with amount, stage, pipeline, close date, owner and associated company and contact from the HubSpot connector. Filter by pipeline name, close date, deal stage name, deal type, record id, company id, deal name, amount, deal owner.
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-tasks

Returns tasks in HubSpot, with title, status, priority, type, due date, assignee and related contact from the HubSpot connector. Filter by assigned to, is overdue, due date, task title, task status, task type, contact email, priority.
run-action

hubspot-add-task

Creates a task in HubSpot and returns the new task's ID. Required: Due date. Optional: Subject, Notes, Status, Priority, Type, Owner ID, Company IDs, Contact IDs, Deal IDs. Writes to HubSpot.
run-action

hubspot-add-engagement-task

Creates a task in HubSpot and returns the new engagement task's ID. Required: Due date. Optional: Subject, Notes, Status, Priority, Type, Owner ID, Company IDs, Contact IDs, Deal IDs. Writes to HubSpot.
run-action

hubspot-update-deal

Changes an existing HubSpot deal. Only the fields you pass are changed; pass an empty value to clear a field. Requires id. Optional: deal name, deal type, amount, deal stage, owner id, pipeline, description, close date.
run-action

hubspot-add-deal-note

Adds a note to a HubSpot deal's timeline. Requires note, deal id.
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

Every commitment from the call becomes a tracked task

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