DupliCat Documentation

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

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

Search DupliCat docs

Find setup, troubleshooting, limitations, scopes, changelog, and operational guides from this docs hub.

Showing 8 of 8 DupliCat docs.

DupliCat · Guide
DupliCat Documentation
Operator docs for DupliCat: setup, limitations, scopes, troubleshooting, and changelog.
/apps/duplicat/docs
DupliCat · Setup
DupliCat Setup
Install DupliCat, configure templates/defaults, and validate one controlled clone before rollout.
/apps/duplicat/docs/setup
DupliCat · Guide
DupliCat Workflow Cloning
Configure and run DupliCat from HubSpot workflows with clear setup steps and operator outcomes.
/apps/duplicat/docs/workflow-cloning
DupliCat · Guide
DupliCat Enhanced Overrides
Use advanced template overrides for date shifts, owner rules, and pipeline/stage mapping with clear precedence.
/apps/duplicat/docs/enhanced-overrides
DupliCat · Limitations
DupliCat Known Limitations (v1)
Intentional v1 boundaries for DupliCat, why they exist, and what to do when you hit one.
/apps/duplicat/docs/limitations
DupliCat · Troubleshooting
DupliCat Troubleshooting
Operator triage for common DupliCat issues (auth, cards, templates, and workflow runs).
/apps/duplicat/docs/troubleshooting
DupliCat · Scopes
DupliCat Scopes and Permissions
Scope-by-scope justification for DupliCat with least-privilege and data-handling principles.
/apps/duplicat/docs/scopes
DupliCat · Changelog
DupliCat Changelog
Release notes for DupliCat.
/apps/duplicat/docs/changelog

DupliCat is a CleverCat operational utility for HubSpot: duplicate CRM records with templates and explicit boundaries.

This docs hub is written for operators. Start with what you want to clone, then use the rollout notes below to choose the right path for your team.

DupliCat supports deals, contacts, companies, tickets, orders, projects, quotes, notes, tasks, calls, meetings, emails, and custom objects. Default naming still honors the standard [Duplicate] prefix when inherited settings keep it in place.

Operator index

Additional guides

What it does (today)

Supported objects: deals, contacts, companies, tickets, orders, projects, quotes, notes, tasks, calls, meetings, emails, and custom objects.
Use DupliCat in HubSpot record views, with preview support when configured.
Workflow cloning currently supports CONTACT, COMPANY, DEAL, TICKET, ORDER, and PROJECT.
Activity-record cloning and related-activity copying are supported; attachments stay out of scope.
Duplicate count: Number of duplicates (1-10) per run.
Templates + defaults: templates per object type, plus portal defaults and personal defaults (“my default”).
Association handling: re-links selected associations; deals can deep-clone line_items (new line item records).
Enhanced overrides (optional): date shift, owner rules, pipeline mapping, and stage mapping where supported.
Verification: HubSpot Property history is the field-level source of truth for “what changed.”

Rollout matrix

Use this matrix to match the object type you care about with the path you plan to roll out first.

Object type / family	Card support	Workflow support	Related-activity behavior	Caveats
Core CRM records Deals, Contacts, Companies, Tickets	Yes: sidebar + preview	Yes: CONTACT, COMPANY, DEAL, TICKET	Can copy selected related activities from supported source records.	Best first-run slice for rollout validation.
Extended standard records Orders, Projects, Quotes	Orders + Projects are available in current record-view placements.	Orders + Projects are available in the current workflow action.	Projects/Quotes can participate in related-activity copy rules where configured.	Use a test slice before broader rollout on less-common object types.
Activity objects Notes, Tasks, Calls, Meetings, Emails	Supported when activity records are part of the workflow you are standardizing.	Validate workflow expectations in a test slice before rollout.	Activity-record cloning and related-activity copying both fit repeatable operational workflows.	Keep attachments explicitly out of scope.
Custom objects Custom objects	Supported with rollout and configuration validation.	Validate workflow expectations before depending on them in production.	Keep defaults conservative and validate object-specific rules in a test slice.	Treat custom-object rollout like any other schema-specific implementation: test first.

First-run validation (recommended)

Start small. Validate one object type, one template, and one surface before you widen access.

Install DupliCat and complete OAuth authorization.
Create one template for one object type.
Set a portal default template, and optionally a personal default (“my default”) for one test user.
Add the DupliCat card to one record sidebar and one preview surface for that object type.
Run one clone with Number of duplicates (1-10) set to 1, then repeat with 2.
Validate naming, key properties, selected associations, and deal line_items behavior where relevant.
If you plan to use automation, validate one workflow run with DupliCat: Clone through workflow.
Review limitations, scopes, and troubleshooting before wider rollout.

Boundaries (read this before rollout)

DupliCat does:

Support cloning across standard objects, activity objects, and custom objects.
Keep rollout guidance explicit so teams can validate the path they plan to use.
Copy writable properties, re-link selected associations, and deep-clone deal line_items when selected.
Support activity-object cloning and related-activity copying.

DupliCat does not:

Clone attachments.
Replace rollout validation for your exact portal, schema, and process.
Run unlimited bulk jobs; card runs are sequential and capped at 1-10 duplicates per execution.

Support intake checklist

When you contact support, include:

Portal ID
Object type or object family you were cloning
Source record URL
Surface used (record view, preview, or workflow)
Template name (or whether you used Use effective default)
Number of duplicates value
Whether you selected association copy, related activities, and/or deal line_items
Timestamp with timezone
Screenshots of the result panel / workflow output