Trellus for Pipedrive

Call the Pipedrive People list you already filtered

Use the current filtered People list as a Trellus power or parallel calling queue. Keep the Person, Organization, and phone choice attached, then save the result as a note on the right Person.

This limited workflow writes a Pipedrive Person note. It does not create or complete a native call Activity, and it does not create a callback.

Where Trellus works in Pipedrive

Starts in: a People list or Person record
Queue: current filters across pages
Phone choice: the right person number
After the call: a Person note
Current limit: no Activity completion or callback
Where it works

The Pipedrive surfaces Trellus uses

The page is deliberately scoped to People. It does not stretch one workflow across every Pipedrive object.

Filtered People list

Start from the People list with the Pipedrive filter and sort the team already chose. Trellus keeps that live list context instead of asking for a CSV.

Additional People-list pages

Continue through the current filtered results while retaining the non-page parts of the list request.

Person detail

On a Person record, resolve the available phone choices and linked Organization for a one-off call.

Rep workflow

The filter survives the call block

01

Open the filtered People list

Use the territory, owner, label, or activity filter your RevOps team already maintains in Pipedrive.

02

Review the phone choices

Trellus deduplicates values and identifies primary, work, mobile, home, and other phone types while keeping the Person and Organization visible.

03

Choose power or parallel

Work one number at a time or use an Trellus parallel session around the same filtered audience.

04

Save the call to the Person

Return the summary, disposition text, numbers, duration, and Trellus transcript link as a Person note.

What returns

A useful Person note—without pretending it is an Activity

the write-back keeps human-readable call context on the Person. It does not populate Pipedrive's structured call-Activity reporting.

Summary
Disposition as note text
Called phone number
Calling number
Call duration
Trellus transcript link
Concrete example

A shared filter stays recognizable

Sam opens “Midwest — no activity in 30 days.” One Person has work and mobile numbers, another belongs to a different Organization, and a third has no usable number. Trellus preserves the list, presents the recognized phone types, and continues through the available pages.

After the connected call
The summary, selected disposition text, dialed number, duration, and Trellus transcript link appear in a note on Sam's resolved Pipedrive Person.
Fit

Use the note-based workflow intentionally

Trellus fits a team that organizes outbound work as filtered People lists and is comfortable keeping the call record in a Person note. It is a poor fit when every call must be a native Pipedrive Activity or when a future callback must be created in Pipedrive automatically.

FAQ

Pipedrive and Trellus

Where does Trellus work in Pipedrive?

Trellus is built around Pipedrive People lists and Person detail records.

Can Trellus dial a filtered Pipedrive People list?

Yes. Trellus keeps the People-list filter context and can continue through additional pages without exporting the audience to a CSV.

Can Trellus call a single Pipedrive Person?

Yes. On a Person detail record, Trellus can present available phone values and linked Organization context for a one-off call.

How does Trellus handle multiple phone numbers?

It deduplicates normalized values and recognizes primary, work, mobile, home, and other phone types. It does not promise to preserve every custom label verbatim.

What does Trellus write to Pipedrive?

Trellus can attach a note to the resolved Person with the available summary, disposition text, called number, calling number, duration, and transcript link.

Test one real People filter

Bring the filter, sort, and phone fields your reps use. See how Trellus saves each result as a Person note.