Before
A team member likely had to identify whether an updated ticket had child tickets, open the related records, and manually copy or reconcile notes between them. Tickets without child records also required a manual check before deciding that no update was needed.
How it works
- Receive an updated ticket event and retrieve its related ticket information.
- Check whether the ticket has child tickets; if none exist, end the workflow without changes.
- Process each child ticket and synchronize notes between the parent and child records.
Workflow details
- Trigger: The workflow starts when updated ticket data is received through the webhook.
- Child-ticket lookup: It retrieves the related ticket information and checks whether the updated ticket has child tickets.
- No-child handling: If no child tickets are found, the automation ends without performing an update.
- Note synchronization: When child tickets exist, the workflow processes each one and synchronizes notes between the parent ticket and the child ticket.
- Completion: After all child tickets have been processed, the workflow completes successfully.
What changed
A ticket update now automatically triggers the child-ticket lookup, the no-child decision, and the note synchronization for every related child ticket, replacing a manual record-by-record handoff.
Work removed
Manually checking for child tickets, opening each related child record, copying or reconciling notes between parent and child tickets, and deciding whether to stop when no children exist.
Expected outcome
For each updated ticket, the workflow removes at least one manual child-ticket lookup and one note-update action per related child ticket.
