Template tickets for recurring work
Clone a model ticket with its associations whenever a maintenance cycle starts.
The challenge
Recurring maintenance means recreating the same ticket structure each cycle, and details drift between cycles.
How AuPerate solves it
Clone Record duplicates a model ticket with its associations whenever the cycle starts, so each one begins identically configured.
How to build it
- 1Keep one model ticket configured the way each cycle should start.
- 2Enrol it when the maintenance cycle begins.
- 3Add Clone Record, copy all properties, and carry the associations across.
- 4Rename the clone with the cycle date using the name field.
What the action gives you
- Copy all properties or a selected set
- System fields and unique identifiers are never copied
- Name the clone or append a suffix
- Optionally copy every association
Related
Other patterns teams build
Trigger a provisioning pipeline
Call your CI or provisioning webhook when an onboarding ticket reaches a stage, with retries for flaky endpoints.
Order dedupe on a custom object
Match a custom order object on order_number:exact and keep the most complete record.
Swap a discontinued SKU
Remove line items matching the old SKU and add the replacement in the same workflow.
Build this in your own workflows
Install AuPerate once and every action appears in your HubSpot workflow editor.
Get Started