DupliCat Setup

This setup runbook is written for HubSpot operators. It assumes you want predictable cloning behavior, not surprises.

Start with a small validation slice (one portal, one object type, one template), then widen only after outputs match expectations.

Quick links

• Docs Home
• Known Limitations
• Scopes and Permissions
• Troubleshooting
• Workflow Cloning
• Enhanced Overrides

Prerequisites

• HubSpot Super Admin or App Marketplace install permissions.
• Portal ID for the HubSpot account you are connecting.
• At least one test record for the object type you plan to validate first.
• Browser access to your HubSpot account and DupliCat settings UI.

Recommended rollout slice (before you install)

• Pick one object type to validate first (start with Deals or Tickets).
• Pick 1–3 source records that represent “normal” data (not your messiest edge cases, and not your cleanest).
• Decide whether deal line_items should be deep-cloned for your workflow (deals only; optional).
• If you plan to claim quotes, activity objects, or custom objects internally, validate those only after a core-object slice is stable.
• Decide whether you need workflow automation cloning (optional).

1. Install and authorize

1. Open Install app.
2. Select the HubSpot account where the app should be installed.
3. Confirm the requested permissions and continue.
4. Complete authorization.

Expected result: install completes and the app is connected for the portal.

2. Configure defaults and templates

Templates are saved per object type and are designed for repeatable runs.

1. Go to Marketplace > Connected Apps > DupliCat > Settings.
2. Configure settings defaults for your target object type (name prefix, empty-value handling, writable-only mode, skipped fields, and association defaults).
3. Open Duplication Templates.
4. Choose object type for the template you are validating first (for example deals, contacts, companies, or tickets).
5. Configure template options and save with a clear template name.
6. Configure enhanced overrides when needed (date shift, owner rules, and pipeline/stage maps for deals/tickets).
7. Optionally set one template as the default template for that object type at portal scope.
8. Optionally set one personal default (“my default”) for that object type.
9. Save settings.

Expected result: settings save succeeds, defaults reload correctly, and portal/personal default choices persist.

3. Add cards to record views and previews

1. For each card-supported object type you are validating first (deal/contact/company/ticket/order/project), open a record and click Customize record view.
2. Add the DupliCat sidebar card.
3. Save and publish the record view.
4. Open that object type's record preview customization and add the DupliCat preview card.
5. Save and publish preview changes.

Expected result: DupliCat cards appear on supported object records and in configured preview surfaces.

4. First clone walkthrough (card path)

1. Open the DupliCat card on a source record.
2. Confirm the proposed clone name (default prefix behavior is typically [Duplicate]).
3. Turn on Advanced Options to reveal duplicate count, template, and related-record controls.
4. Set Number of duplicates (1-10).
5. Choose a template in the template selector, or choose Use effective default. Portal default behavior: my default -> portal default -> settings defaults.
6. Confirm clone options loaded as expected for this run.
7. Select related records to copy.
8. For deals, select line_items only if you intend to deep-clone line items (new line item records).
9. Click Duplicate record (or Duplicate N records).
10. Open the resulting record link(s) and verify key properties and associations.
11. Confirm each cloned record includes a source-reference note (enabled by default).
12. In HubSpot, open Property history on a copied field and verify the source and timestamps match your run.

Expected result: selected/default template behavior is applied, clone succeeds, and each clone returns a record ID/link.

5. Optional: configure workflow cloning

Use workflow cloning when you need repeatable cloning inside HubSpot automation.

1. Open a HubSpot workflow for a supported workflow object type (CONTACT, COMPANY, DEAL, TICKET, ORDER, or PROJECT).
2. Add action DupliCat: Clone through workflow.
3. Choose a template (or choose the default option to inherit your saved defaults).
4. Publish the workflow and run on a test record.

Expected result: workflow runs return a clone result link plus any warnings.

See Workflow Cloning for detailed inputs/outputs.

Validation checklist (before wider rollout)

• Number of duplicates (1-10) produces the expected clone count.
• [Duplicate] name prefix and numbering are acceptable for your naming conventions.
• Template selection/default resolution behaves as expected (including Use effective default).
• Key properties copy correctly (and empty values stay empty unless you enabled empty-value copying).
• Selected association re-linking matches your expectations.
• Deal line_items deep clone behaves as expected (if you enable it).
• Source-reference note is present on clones (enabled by default).
• HubSpot Property history shows expected change sources for copied fields.

Boundary check

• DupliCat supports quotes, activity records, and custom objects, but those rollouts should still be validated deliberately in your own portal.
• Templates are object-type specific; cross-object templates are not supported.
• Activity-object cloning and related-activity copying are supported, but attachments are not cloned.
• Card runs are sequential and capped at 1-10 duplicates per execution.
• Verification lives in HubSpot: use the record timeline plus Property history.

Need help?

Contact support and include:

• Portal ID
• Object type and source record URL
• Surface used (card vs workflow) and template name (or “Use effective default”)
• `Number of duplicates` value
• Whether deal `line_items` deep clone was selected
• Expected behavior vs actual behavior
• Timestamp with timezone
• Screenshots of the result panel / workflow output