> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to duplicate an automation instead of rebuilding it
- URL: https://blog.jestor.com/how-to-duplicate-an-automation/
- Published: 2026-09-16T18:51:01.000Z
- Updated: 2026-09-16T18:51:01.000Z
- Author: Bruno Bannach

Being able to **duplicate an automation** removes one of the most tedious tasks in process building: recreating a complex rule, step by step, because a second process needs something almost identical. In **Jestor**, duplication happens from the automation itself, with a notification when it completes.

## Why rules get rebuilt more often than they should

Most automations are not unique. A notification when a deadline passes, an entry created when a card reaches a stage, a message sent on approval: these recur across processes with small variations.

Rebuilding each one invites inconsistency, because the second version is never quite the same as the first.

Where duplication saves real time:

- The same rule applied to a parallel process
- A variation for a different department
- Testing a change without touching the working version
- Rolling a proven pattern out to several tables

## Duplicate or build again

| Situation                          | Duplicate   | Build new     |
| ---------------------------------- | ----------- | ------------- |
| Same logic, different table        | Yes         | No            |
| Testing a modification safely      | Yes         | No            |
| Similar trigger, different purpose | Consider it | Often clearer |
| Genuinely different logic          | No          | Yes           |

## Step by step to duplicate one

1. **Open the automations list** for the table or process.
2. **Find the automation** you want to copy.
3. **Choose duplicate** from its options.
4. **Wait for the notification**, since a large automation takes a moment to copy.
5. **Rename the copy** immediately, so the two are never confused.
6. **Adjust the parts that differ**, usually the target and the conditions.
7. **Test the copy** before enabling it.

## Why renaming immediately matters

Two automations with the same name are a future incident. Someone will edit the wrong one, and the symptom will appear in a process nobody was working on. Renaming takes five seconds and prevents an afternoon of confusion.

- **Duplicate from the list:** no rebuilding step by step
- **Notification on completion:** large automations copy in the background
- **Delete from the same place:** cleanup handled alongside
- **Consistency preserved:** the copy matches the original exactly

## Frequently Asked Questions

### Can I copy a complex automation?

Yes. Duplication handles large automations, notifying you when it finishes. See [jestor.com](https://www.jestor.com/?ref=blog.jestor.com).

### Should I always duplicate rather than rebuild?

No. When the logic genuinely differs, building fresh is usually clearer.

### Can I delete an automation from the same place?

Yes. Duplication and deletion are both available from the automation itself.

## Video Tutorial: Step by Step

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way, all without code and powered by **AI**. Discover Jestor at [jestor.com](https://www.jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.