Search Projects
copper.search_projects
ActionCRM & salesconnection required
Calls the Copper API with the connection's credentials.
List or search Project records in Copper, one page at a time, using the search criteria the API documents.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Copper
- Secret shape
- the API key, or {"api_key": "…"}
- Config it needs
- user_email, base_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
5 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
criteria Copper search criteria as a JSON object (name, emails, assignee_ids, tags, minimum_created_date …), exactly as the search endpoint documents them. | object | No | — | — | — |
page_number Which page of results to fetch; Copper numbers pages from 1. | number | No | 1 | ≥ 1 | — |
page_size How many records to return per page; Copper's documented maximum is 200. | number | No | 20 | 1–200 | — |
sort_by The Copper field to sort by, such as name, date_created or date_modified. | string | No | — | — | — |
sort_direction Sort ascending or descending. | string | No | asc | one of "asc", "desc" | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"page_number": 1,
"page_size": 20,
"sort_direction": "asc"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
items The page of records Copper returned, in sort order. | array | — |
count How many records are on this page — not the size of the whole result set. Keep asking for the next page until a short page comes back. | number | — |
page_number The page number that was requested. | number | — |
page_size The page size that was requested. | number | — |
{
"count": 0,
"items": [],
"page_number": 0,
"page_size": 0
}See Search Projects run in a workflow.
In a technical demo we add the Copper connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.