Search Activities
copper.search_activities
ActionCRM & salesconnection required
Calls the Copper API with the connection's credentials.
List or search activities logged in Copper, one page at a time.
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
3 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 activity search criteria as a JSON object (parent, activity_types, minimum_activity_date …). | object | No | — | — | — |
page_number Which page of results to fetch; Copper numbers pages from 1. | number | No | 1 | ≥ 1 | — |
page_size How many activities to return per page. | number | No | 20 | 1–200 | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"page_number": 1,
"page_size": 20
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
items The page of activities Copper returned. | array | — |
count How many activities are on this page. | number | — |
{
"count": 0,
"items": []
}See Search Activities 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.