Skip to main content

How to clone HubSpot records in workflows | DupliCat

Last updated: March 22, 2026 (America/Los_Angeles)

This guide reflects current shipped behavior.

HubSpot’s native clone is a manual record action. Workflows are automation. If you want cloning in workflows — whether for one-off automation or recurring renewal cycles — it’s worth using a tool that makes inputs and outputs explicit.

DupliCat is a CleverCat operational utility for HubSpot that adds a dedicated workflow action for controlled record duplication.

Fast answer

Native HubSpot baseline (manual)

  • HubSpot’s documented clone path is a manual record action flow.
  • Operators clone from a record, review values, and save.
  • Native clone docs do not describe a dedicated native “clone record” workflow action.
  • Reference: HubSpot Clone a record.

When native is enough

Native clone is enough when clone frequency is low and manual execution is acceptable.

Where native breaks

  • Manual clone does not scale cleanly for recurring automation workloads.
  • Operators can’t rely on “everyone clicked the same boxes.”
  • You lose workflow-history outputs for clone runs.
  • Repetitive manual renewal runs create process drift.

Operational utility path

Use DupliCat workflow cloning when clone behavior must run from workflow enrollment with repeatable controls.

Why this is harder than it sounds

  • Creating a record is not the same as cloning a full object graph with consistent rules.
  • Association and line-item behavior needs explicit handling per run.
  • Operational teams need clear run outcomes for follow-up and audits.
  • Renewal cycles require repeated consistency, not one-off copy success.

What you’ll get (DupliCat workflow action)

  • Supports workflow action entry: DupliCat: Clone through workflow.
  • Workflow cloning currently supports CONTACT, COMPANY, DEAL, TICKET, ORDER, and PROJECT.
  • Inputs for templates/defaults, association targets, and advanced controls (including deal line-item deep clone).
  • Workflow history output fields for clone status, warnings, cloned record ID/URL, request ID, and errors.

Renewal deal automation

Renewal workflows are the most common use case for workflow cloning. DupliCat supports:

  • Template-driven consistency so naming, association targets, and copy behavior stay the same across renewal runs.
  • Optional deep clone deal line items when your renewal needs new line item records.
  • Workflow history outputs (clone status + cloned record links) for operational follow-up.
  • Controlled scaling: enroll a small batch (3-5) and review outputs before widening triggers.

Prerequisites

  • DupliCat installed in your portal.
  • HubSpot Workflows access for the object type you want to enroll.
  • A test workflow and a test record for first-run validation.
  • For renewals: a dedicated renewal template and a test deal.

Boundaries and limitations

Does

  • Run clone logic from workflow enrollment for supported object types.
  • Give you visible run outputs in workflow history.
  • Support repeatable renewal clone operations with explicit, template-driven rules.

Does not

  • Remove the need to validate required fields, uniqueness, and associations in your portal.
  • Guarantee safe scale without your own enrollment gates and monitoring.
  • Make “set and forget” safe by default; use controlled batches and review outputs.

Validation slice checklist (before rollout)

  • Build a test workflow with manual enrollment and one enrolled record.
  • Configure the action with one known template (or portal default) and minimal options.
  • Run once; review workflow history outputs.
  • Verify the cloned record’s required fields and associations (and line items for deals if enabled).
  • Only then add advanced overrides or broader triggers.
  • For renewals: enroll a small batch (3-5) and review outputs before widening triggers.

Support-intake checklist

When contacting CleverCat support, include:

  • HubSpot portal ID.
  • Workflow ID + enrollment record ID/URL.
  • Screenshot of the DupliCat action configuration (inputs).
  • Template selection + action inputs (association targets, deepCloneLineItems, overrides).
  • Workflow history outputs (cloneStatus, warningCount, requestId, errorCode/errorMessage, clonedRecordUrl).
  • Cloned record ID(s)/URL(s) and screenshots.

Fallback: use Known limitations and attach workflow run context in Support.

Next steps

FAQ

Is there a native HubSpot workflow action specifically for record cloning?

HubSpot’s clone docs cover manual clone behavior from record context. For workflow cloning, use DupliCat’s workflow action path.

Which object types are supported for workflow clone runs?

CONTACT, COMPANY, DEAL, TICKET, ORDER, and PROJECT.

Can I control line-item behavior in workflow runs?

Yes. Deal workflow runs support line-item controls through documented action inputs.

Can I create next-year renewal deal copies automatically?

Yes. DupliCat supports workflow-triggered duplicate creation for supported object types. Use a dedicated renewal template for consistent behavior.

Can I apply template defaults in workflows?

Yes. Template/default behavior is part of the workflow clone model.

What do workflow outcomes mean?

Workflow history includes clone status, warning count, cloned record ID/URL (when created), request ID, and error fields. Use those outputs to decide whether to continue, retry, or escalate.

Are attachments and activities cloned in workflow runs?

Attachments are not cloned. If activity behavior matters for your workflow, validate that expectation in a test slice before rollout.

What should I validate before scaling renewal runs?

Validate template behavior, association handling, and critical fields in a test slice first.