Skip to main content

DupliCat Workflow Cloning

Last updated: February 23, 2026 (America/Los_Angeles)

Applies to version/build: DupliCat v0.1.6 (released February 16, 2026)

Use DupliCat: Clone through workflow when you want repeatable cloning inside HubSpot automation.

Workflow cloning currently supports: CONTACT, COMPANY, DEAL, TICKET, ORDER, PROJECT.

Setup path

  1. Open a HubSpot workflow for a supported object type.
  2. Add action DupliCat: Clone through workflow.
  3. Choose template and clone options for your use case.
  4. Publish and run on test records before wider rollout.

Action inputs

All inputs are optional unless HubSpot marks one as required in your portal.

Input areaPurposeNotes
Template selectionChoose which template behavior to apply.Use templateIdSelect for the normal picker; legacy definitions may still send templateId.
Related-record selectionChoose which related records are carried over.Leave empty to follow template/default behavior.
Advanced options toggleTurn advanced controls on for the run.Keep off for simpler, default-driven runs.
Name behaviorOverride clone naming for this run.Useful when you need a temporary naming convention.
Empty-value handlingControl whether blank source values are copied.Use carefully to avoid unwanted blanks in destination records.
Writable-field behaviorLimit cloning to writable-safe fields.Recommended when you want safer runs in strict portals.
Deal line-item behaviorControl deal line-item handling.Applies to deal workflows only.
Skip fieldsExclude specific fields from cloning.Use when a field should never be copied for this workflow.
Field-value overridesSet explicit values during clone creation.Use for controlled overrides in repeat automation.
Legacy compatibility fieldsSupport older workflow definitions.Keep only when older saved workflows still rely on them.

Action outputs

Workflow runs provide a result summary that can include:

  • overall clone result
  • warning summary
  • cloned record link (when created)
  • applied template/default context
  • hs_execution_state: SUCCESS, FAIL_CONTINUE, or BLOCK
  • support-trace details when available

Outcome types

Workflow runs typically resolve to one of three outcomes:

  • Completed: clone finished successfully.
  • Needs attention: run completed but validation issues require operator review.
  • Temporary issue: run could not complete and should be retried after conditions stabilize.

Runtime precedence

When multiple settings overlap, DupliCat applies them in this order:

  1. System defaults
  2. App settings defaults
  3. Template/default resolution
  4. Workflow-level overrides
  5. Direct field-value overrides

Boundaries

  • Workflow cloning currently supports CONTACT, COMPANY, DEAL, TICKET, ORDER, and PROJECT.
  • Template resolution depends on your portal and personal defaults (or a specific template selection).
  • Attachments are not cloned. If you want activity-record behavior in a workflow rollout, validate it in a test slice first.

Troubleshooting

  • Template missing: confirm the selected template still exists and matches the workflow object type.
  • Advanced options not applying: confirm advanced options are enabled for that run.
  • Validation issues: review object type, input values, and selected fields.
  • Temporary failure: retry after a short wait.
  • Unexpected results: compare workflow run details and contact support with portal ID and run context.

Support intake checklist

When you contact support, include:

  • Portal ID
  • Workflow name + enrolled object type
  • Source record URL (or record ID)
  • The template selection mode (explicit template vs default)
  • Any visible workflow output/errors
  • Timestamp with timezone