Write

Cross-Connector

Log your Chorus calls in Nutshell without retyping them

For operations teams who want recorded calls in the CRM, just by asking their AI assistant.

Log Chorus calls as Nutshell activities

Find last week's Chorus calls for Northwind Traders that are not logged in Nutshell and log them.

2 Chorus calls for Northwind Traders are not in Nutshell. - Oct 7, 30 min: Renewal discussion with Dana Whitfield - Oct 9, 15 min: Pricing question with Luis Ortega - 1 call has no usable start time and was skipped Nutshell activities cannot be edited or deleted once logged. Which of these should I log?

Chorus

Sample figures. Your results come from your own account.

nutshell-get-account

chorus-get-engagements

nutshell-get-activity

nutshell-add-activity

On this page

The problem

The prompt

Who it's for

How it works

Tools used

Connector

Chorus

Run it on your own Chorus data.

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

The problem

Calls retyped into the CRM late, twice or never

Calls recorded in Chorus have to be retyped into Nutshell, and that happens late, twice or not at all. A Nutshell activity cannot be edited or deleted once it is created, so a wrong entry stays.

Without PopdockAI

List recorded calls for the rep or account
Check which are already in Nutshell
Retype each one as an activity
Live with a wrong entry you cannot delete

With PopdockAI

Chorus calls and existing Nutshell activities are read
Calls missing from Nutshell are listed
You pick the exact rows, warned that activities cannot change
Only approved calls are logged

The prompt

Use this prompt

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

Prompt

**Objective:** For the account `{account-name}`, find Chorus calls from the last `{lookback-days}` days (default 14) that have no matching Nutshell activity, and log the ones the user approves.

**Step 1: Find the account in Nutshell**

Call `nutshell-get-account` (Nutshell server) with `name.contains` set to `{account-name}`. If more than one account matches, list them and stop. If none match, say so and stop.

**Step 2: Read the Chorus calls**

Call `chorus-get-engagements` (Chorus server) with `account-name` set to the Nutshell account `name` and `date.from` set to the start of the window. Note `date`, `subject`, `duration` and `conversation-type` for each call.

**Step 3: Find what is already logged**

Call `nutshell-get-activity` (Nutshell server) with `start-time.from` set to the window start and `name.contains` set to the account name. Treat a call as already logged if an activity starts on the same day and its name contains the call subject or the account name.

**Step 4: Propose, then confirm**

Show a table of the calls with no matching activity: date, subject, duration, and the activity you would create. Also say that Nutshell activities cannot be edited or deleted after they are created. Ask the user which rows to log and wait. Do not write anything before they answer.

**Step 5: Log the approved calls**

For each approved row call `nutshell-add-activity` (Nutshell server) once with `name` set to the subject, `activity-type` set to the call or meeting type the user confirmed, `start-time` set to the call time and `end-time` set to the start plus the duration. Report each result.

**Rules & Guidelines:**

* `nutshell-get-account`, `nutshell-get-activity` and `nutshell-add-activity` are on the Nutshell server; `chorus-get-engagements` is on the Chorus server.
* `nutshell-add-activity` is the only tool that may write, and only in Step 5 after explicit approval. Do not call any update or delete tool on Nutshell, or any add, update, create or export tool on Chorus.
* Never log a call twice; if unsure whether it is already logged, ask.

**Validation:**

* If Chorus has no calls for the account, report that and stop without writing.
* If a call has no usable start time, skip it and list it as skipped.

Who it's for

One answer, three teams that use it

Sales operations

Bring activity up to date safely

Only the rows you approve are logged, which matters when activities cannot be edited.

Find Chorus calls for Contoso in the last 30 days that are not in Nutshell.

Account executives

Log your missing calls

Get your unlogged calls for the week and log the ones you choose.

Which of my Chorus calls last week are missing from Nutshell? Log the ones I pick.

Sales managers

Check a rep's logging

See how many of a rep's calls never reached Nutshell.

List Jordan Lee's Chorus calls this month that have no Nutshell activity.

How it works

What PopdockAI does when you ask

You name a rep or account and a period, and your AI assistant finds the calls missing from Nutshell. Calls with no usable start time are skipped.

Ask

You name the rep or account and the period.

Your AI tool

Compare

It reads Chorus calls and the Nutshell activities already logged.

nutshell-get-account

chorus-get-engagements

nutshell-get-activity

Approve

You pick the exact calls to log, after a warning that activities cannot be changed.

No items found.

Log

It adds the approved calls as Nutshell activities.

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

nutshell-get-account

Returns Nutshell companies (accounts) with their contact details, owner and related fields. Filter by name, owner and other company fields.

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

nutshell-get-activity

Returns logged Nutshell activities such as calls and meetings, with the records they relate to and when they happened.

run-action

nutshell-add-activity

Logs a call, meeting or other activity in Nutshell. Activities cannot be edited or deleted afterwards through the Nutshell API. Tested live against a Nutshell account.

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.

The outcome

Recorded calls in Nutshell once, only as approved

Related use cases

More ways to put this data to work

Build a Chorus coaching playlist

Ask your AI to build a Chorus coaching playlist on a topic and it picks up to five calls from different reps, proposes clip timings and adds them after you approve.

Learn More

Check a Chorus call's issues against Zendesk tickets

Ask your AI to check a Chorus call against Zendesk and it lists each problem the customer raised with its matching ticket, or none, without changing anything.

Learn More

Chorus account conversation briefing

Ask your AI for a briefing on an account and it reads its Chorus conversations and emails to show where things stand, who is involved, open threads and questions to ask.

Learn More

Chorus and Teamwork.com client briefing

Ask your AI for a client brief and it puts Teamwork.com project health and late milestones next to recent Chorus calls and emails, without changing anything.

Learn More

Chorus and Zendesk customer briefing

Ask your AI for a customer brief and it combines unresolved Zendesk tickets with recent Chorus calls and emails, matching issues both sides are hearing about.

Learn More

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.