Call the rows you already qualified in Clay
Open the Clay table and view your team intends to work. Trellus maps the phone columns, uses those current-view rows as the queue, and returns bounded call state to the same source records.
Where Trellus works in Clay
Watch Trellus call a Clay table
The recording shows the Clay Tables starting surface and the Trellus calling workflow. The mapping, source-row write, callback, and connected-CRM boundaries remain the contract.
Verified Trellus walkthrough for Clay. It does not prove every Clay cell type, downstream automation, or workspace permission.
The Clay surface is one exact table view
Trellus does not treat the whole workspace as a prospect pool. The workspace, table, view, and row order define the call list.
The visible view supplies the source record IDs and their order. Switching views changes the population instead of quietly merging two audiences.
At least one phone column is required. Trellus can retain name, title, company, URLs, industry, research, and other nonempty row context alongside the phone choices.
Each queue row keeps its Clay record ID, table, row position, source URL, original fields, and mapped values attached to the active call.
A row marked Trellus Callback Task with a due date can return as follow-up work. The reviewed callback scan is capped at 250 records.
A label such as “Mobile” is useful evidence, not certainty. Review renamed, generated, and multi-provider phone fields before the first production block.
From a qualified view to the same-row result
Build the audience in Clay
Source, enrich, score, and filter the records into the exact view the rep should call.
Map the phone and context columns
Choose one or more phone fields plus the research the rep needs when a person answers.
Review exclusions
Rows marked Do not call again (Trellus) remain visible but do not enter the callable set. Recorded wrong numbers return with negative status.
Work the supported call block
The current Clay row stays attached to each attempt; the team does not have to export and reconcile a second copy of the list.
Inspect the updated row
Verify the outcome, attempt, conditional fields, history, and callback on the exact record before broad rollout.
Named columns, not a hand-wavy “sync”
The reviewed workflow creates or updates Trellus-owned fields on the source record. A reached-human timestamp is written only when the call state says a human was reached.
Several fields are updated in sequence. A later rejected update does not prove earlier successful writes were rolled back. Test the failure path in a sandbox.
“Writes to Clay” is not “writes through Clay”
What the page can promise
Call context comes from the current Clay view. Supported results go to named Trellus columns on the exact source row. A callback remains row state that Trellus can retrieve later.
What needs another test
No native Clay task is completed. No Salesforce or HubSpot activity is promised. No downstream sequencer step, provider-wide DNC, or all-or-nothing rollback is implied.
Seventeen rows, two phone fields, one source of truth
Maya filters a fictional event table to 17 US accounts with verified mobiles and an ICP score above 80. She maps Mobile, Direct dial, and the research columns. One DNC row stays out; one known-wrong mobile leaves the direct line available.
After a live answer, Trellus writes Interested, the attempted and reached-human times, a history line, and the available summary to that same row. Tuesday at 10:00 becomes callback title-and-due-date state on the row.
The callback is not an assigned Clay task, calendar event, or CRM activity. Teams that require one should build and test that downstream workflow separately.
Clay and Trellus
Can I call directly from a Clay table?
The reviewed Trellus workflow reads the current Clay table view, requires a mapped phone column, and uses eligible rows as the calling context.
Does Trellus require a CSV export?
No CSV is required in the reviewed table-view path. Trellus reads the current view and returns bounded result fields to the source rows.
Which Clay columns do I need to map?
At least one phone column. Name, title, company, URLs, industry, and research fields can make the active conversation more useful. Human review is still important.
What does Trellus write back?
The core is outcome, attempted time, and call history. Reached-human time, summary, wrong-number state, DNC state, and callback fields are conditional on the corresponding action or call state.
Does Trellus create a Clay task?
No. The reviewed workflow stores a callback title and due date on the source row. It does not create or complete a native Clay task or Sequencer step.
Does the result automatically reach my CRM?
Not by this page's evidence. A separate Clay automation may send data elsewhere, but its triggers, permissions, schedules, and acknowledgements require an end-to-end test.
Does Trellus remember wrong numbers and DNC?
It can store wrong-number and Do not call again (Trellus) state in Trellus-owned Clay columns. Those controls do not replace the team's wider compliance and data-governance process.
Bring the Clay view your reps would actually call
We will review the phone map, research fields, result columns, callback rule, and downstream expectations before rollout.
