Skip to content
English
More support
  • There are no suggestions because the search field is empty.

How to Use the Clone Attack Workflow Action

Automatically clone records using Clone Attack within your HubSpot workflows.

The Clone Attack workflow action allows you to automate the cloning of Deals, Contacts, Companies, or Tickets based on your configured Clone Configuration. This is useful for workflows like automatically generating a renewal deal when a deal is marked "Closed Won", or duplicating records for onboarding processes.

You can set up a workflow to clone a Deal when a renewal is due. With a custom Clone Configuration, you can specify what properties and associations are copied and which values get updated. This allows for tailored automation across different pipeline stages or deal types.

 

⚠️ Important: Preventing Workflow Loops

If the cloned record meets the same enrollment criteria as the original, it will be enrolled into the same workflow—creating an infinite cloning loop.

To prevent this, you must do one of the following:

  1. Adjust your Clone Configuration so the cloned record no longer meets the workflow’s enrollment criteria.

    • For example, you can set a different deal stage, lifecycle stage, or custom property value to exclude it.

  2. Add an enrollment exclusion filter:

    • Add a condition like:
      Record source detail 1 is not equal to Clone Attack

      CleanShot 2025-06-30 at 13.51.34@2x

    • This ensures that only records created outside of Clone Attack are enrolled.

 

Instructions: How to Add the Clone Attack Workflow Action

  1. In your HubSpot Workflow, click the ➕ icon to add a new action.

  2. In the search bar, type "Clone Attack", then select the Clone Deals (new) or relevant object-based action.

    CleanShot 2025-06-30 at 13.10.25@2x

  3. Under Name of the new [Object], enter your desired name.

    • You can use Data Variables like {Deal Name} to create dynamic names.

    • Example: {Deal Name} - Renewal

      CleanShot 2025-06-30 at 13.39.44@2x

  4. Choose a Clone Configuration from the dropdown.

    • This determines which properties and associations are brought over and what default values are set

      Select a Clone Configuration within the Clone Attack Workflow Action

       

  5. Click Save to confirm your action.

  6. Finish setting up the rest of your workflow and click Review and publish when you're ready to activate.

🔗 Haven’t Set Up a Clone Configuration Yet?

Check out this article first:
👉 How to Create a Clone Configuration

🔍 Workflow Action Behavior

When a record reaches the Clone Attack action, it will pause until one of the following occurs:

  • ✅ Success: a clone was successfully created
    • The action output will include the Record ID of the cloned object.
  • ❌ Failure: If the cloning attempt fails, the Workflow Action Log will show an “Error” event. Details about the failure will be provided in the log.
    • A 403 error typically means that Clone Attack is missing required HubSpot permissions (scopes).
      • To fix this, uninstall and reinstall Clone Attack to reauthorize the necessary scopes.
      • Important: Uninstalling will not delete any existing setup—your Clone Configurations and Workflow actions will remain intact
  • ⏳ Stuck or Delayed: If the record remains paused at the Clone Attack step and neither a success nor error message appears in the Workflow Action Log:
    • Please contact our team at care@hapily.com with the following details:
      • HubSpot Portal ID
      • Record ID of the enrolled record
      • Timestamp of when the record entered the Clone Attack action (available in the Workflow Action Logs)