Clone Record
Clone Record creates a copy of the enrolled record, custom objects included. Copy everything writable or pick exact properties from a live multiselect, rename the clone, and optionally carry the source's associations across. Available from the Pro plan.
Input fields
| Field | Shown for | What it does |
|---|---|---|
| What to copy | always | Copy all properties (default) or copy only selected properties, which reveals a searchable multiselect of the record type's writable properties. |
| Properties to copy | selected mode | The multiselect. System fields and unique identifier properties are never copied in either mode; uniqueness is detected per object type from your portal schema. |
| Name for the clone | always | Exact name for the copy. Leave empty to reuse the source name plus the suffix. |
| Name suffix | always | Appended to the source name when no name is given. Default: (copy). |
| Also copy associations | always | Link the clone to every contact, company, deal, ticket and line item the source is linked to. |
Output fields
| Output | Meaning |
|---|---|
| Success / Status | cloned or error. |
| New Record ID | The clone's ID, usable in later workflow steps. |
| Properties Copied | How many properties carried over. |
Worked examples
Create next year's renewal deal on close
- 1Workflow: deal based, enrolled on Closed won.
- 2What to copy: Copy all properties.
- 3Name suffix: " - Renewal".
- 4Also copy associations: Yes, so the renewal keeps its contacts and company.
- 5Follow with Date Calculator: add 12 months to the close date on the clone via the New Record ID output.
Good to know
- Never copied: record IDs, create and modify dates, source metadata, and every unique identifier property. Uniqueness is read from the object type schema, so contact email and custom object unique keys are excluded automatically.
- Deal, company and ticket clones get a name automatically; custom objects keep their own naming property untouched unless you include it.
Use cases
Create next year’s renewal deal
When a deal closes won, clone it with associations, name it Renewal 2027, then shift the close date with Date Calculator.
Template tickets for recurring work
Clone a model ticket with its associations whenever a maintenance cycle starts.
Spin off a child record on a custom object
Clone a project record, copy selected properties only, and associate it to the original.
Frequently asked questions
What happens to unique properties such as email?
They are never copied. AuPerate reads your portal schema and excludes properties marked unique for that object type, plus contact email, so the clone cannot collide with the source record.
Can the clone keep the original record's associations?
Yes. Turn on Also copy associations and the clone is linked to every contact, company, deal, ticket and line item the source is linked to.
Does cloning work on custom objects?
Yes. The object type comes from the workflow enrollment, so any object type that supports workflows can be cloned, custom objects included.