Workflow action types

What an action does

After the trigger enrolls a record, Kanopee follows the connected action graph.

An action can change HubSpot data, create new data, route ownership, branch the workflow or pause it.

Select an action node in the workflow editor to configure its fields. The fields available depend on the action and, in some cases, the workflow object or target record.

Update properties and ownership

Property actions include setting a value, clearing a value and copying a value between supported record references.

Owner actions can assign a specific HubSpot owner, rotate across a selected owner pool or team, and support region-based owner routing for supported records.

Writable-property and owner choices depend on the HubSpot metadata synced into Kanopee.

Create HubSpot records, tasks and notes

Kanopee can create new HubSpot records from workflow actions.

Creation actions can also expose the newly created record as an output that later steps can reference.

Tasks and notes can be associated with relevant records. Deal and Ticket creation requires portal-specific values such as pipelines and stages where applicable.

Work with associations and lists

Association actions let a workflow work beyond the enrolled record.

Depending on configuration, later actions can target associated records or records created by earlier actions. Kanopee also supports static-list membership actions.

Association behaviour depends on the relationship definitions available in the connected HubSpot portal, so keep metadata synced if association labels change.

Control workflow logic

Use If/then branch to send a run down the first branch whose conditions match, with a fallback path when none match.

Use Delay for or Delay until date to pause a run before the next action.

These are workflow-control actions: they change how the automation proceeds rather than simply changing a CRM property.

Validation and runtime failures

Before publishing, Kanopee checks many action requirements such as writable properties, required owners, pipeline/stage selections and delay values.

A workflow can still encounter a runtime failure after publication—for example, if a referenced HubSpot item is later removed or an API request cannot be completed.

If an action that used to work starts failing, sync HubSpot metadata and review that action's current configuration.

---