Update Project
copper.update_project
ActionCRM & salesconnection required
Calls the Copper API with the connection's credentials.
Update one Project in Copper. Only the fields you supply are changed; anything you leave out keeps its current value.
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
4 fields, 1 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 |
|---|---|---|---|---|---|
project_id The Copper Project id, as returned by a create or search node. | string | Yes | — | — | — |
name A new name for the Project. | string | No | — | — | — |
details A new description for the Project. | string | No | — | — | — |
fields The Copper fields to change, as a JSON object of Copper field names (status, assignee_id, custom_fields …). These are merged over the fields named above, so this node can change anything the API accepts. | object | No | — | ≥ 1 characters | {"assignee_id":12345} |
- At least one of fields, name, details must be set.
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"fields": {
"assignee_id": 12345
}
}Output
One shape.
result
The provider's response object, as returned.
Extra keys beyond the ones listed can appear.
{}See Update Project 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.