Overview
Cards that repeat, like recurring requests or similar tasks, can now be duplicated directly in Pipefy. The feature is already available to all accounts and removes the need to rebuild a card from scratch every time the process repeats.
What's new?
- Duplicate card: open any card, click the menu in the top right corner and select Duplicate (only visible to users with permission to create cards in that pipe).
- Choose the copy scope: decide whether to copy only the start form fields, or all fields and card attributes, including assignees, labels, and due dates.
- Duplicated cards always land in the first phase: every card created through duplication automatically starts in the pipe's first phase, following the normal process flow.
- First version limitation: for now, attachments and connections are not duplicated, with the exception of connection fields.
How does this help?
- Cuts repetitive typing: reuse data you already entered instead of rebuilding a similar card from scratch.
- Keeps the original card's context: copying all fields and attributes brings the assignee, labels, and due date along with the new card.
- Gives you flexibility of scope: choose a lighter copy with just the start form, or a full copy, depending on what each new request needs.
Use cases
1. Purchasing Analyst with a one off request outside the regular flow
A Purchasing Analyst gets a standalone request similar to a past one, but not part of a scheduled flow with the same supplier.
Instead of retyping everything, they duplicate that previous order card and only adjust item and value for this specific case.
This handles the exception at hand without building an automation for something that will not repeat on a cycle.
2. Onboarding Manager with a hire outside the calendar
An HR Manager needs to open onboarding for a hire that came up outside the regular admission calendar, but for a role already mapped before.
They duplicate a previous card for the same role, copying all fields and attributes, and only adjust the new person's details.
This covers the one off case without waiting for the next scheduled onboarding cycle.
3. Legal team with an unexpected contract
A lawyer receives a contract request from a client type they've handled before, with no expectation of it repeating.
They duplicate only the start form of a finished card, without inheriting old assignees or labels, and fill in the specifics of this new case.
This reuses an already structured base without treating the contract as part of a recurring flow.
4. Support team with a similar, isolated ticket
A support analyst gets a standalone ticket similar to one already resolved, with nothing pointing to a recurring pattern that would justify an automation.
They duplicate the previous ticket's card, reuse the problem and solution structure, and update the new customer's details.
This resolves the isolated case quickly, without manually copying information from one card to another.
Most relevant for
- Pipe Admins
- Builders
- Operations teams
- Users who create recurring cards
