Log Activity
copper.create_activity
ActionCRM & salesconnection required
Calls the Copper API with the connection's credentials.
Log an activity or note against a Copper record, using an activity type id from copper.list_activity_types.
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
6 fields, 3 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 |
|---|---|---|---|---|---|
parent_type The kind of record the activity is logged against. | string | Yes | — | one of "person", "company", "lead", "opportunity", "project", "task" | — |
parent_id The id of that record. | string | Yes | — | — | 27140359 |
activity_type_id An activity type id from copper.list_activity_types; 0 is Copper's Note type. | string | Yes | — | — | 0 |
activity_type_category Whether the activity type is a user type or a Copper system type. | string | No | user | one of "user", "system" | — |
details The body of the note or activity. | string | No | — | — | — |
activity_date When the activity happened, as a Unix timestamp in seconds; Copper defaults to now. | string | No | — | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"activity_type_category": "user",
"activity_type_id": "0",
"parent_id": "27140359"
}Output
One shape.
result
The provider's response object, as returned.
Extra keys beyond the ones listed can appear.
{}See Log Activity 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.