Add PARENT TASK NAME Dynamic Variable for Subtask Automations
D
Daniel Matus
In the 'Change task name' action for an automation triggered by 'Subtask Created', the dynamic variable for Parent Task Name is missing from the list of available fields.
Use Case: Our video production workflow relies on creating parent "Batch" tasks with several subtask deliverables. For clarity and file management, it is essential that each subtask is automatically renamed to include the parent batch's name (e.g., "Batch 02 - Mixed Variation 1").
Without this variable, we have to manually rename every single subtask, which is time-consuming and prone to error. Adding the Parent Task Name variable would automate a critical step and ensure consistency across all our projects.
This seems like a very very simple addition that would take long, please HELP!!
Log In
Zach
Hey there, Dan. Is this what you're asking for? I think the wording of our action probably made it confusing, but this should update the title of the subtask.
D
Daniel Matus
Zach Hi Zack, really appreciate the quick response. Have a look here: It appears the "Task Name" is pulled from the trigger subtask itself. What I am referring to- is having another option there that can be called "Parent Task Name" so the full name of the parent task which the subtask is under can be inserted as a dynamic variable as well. And then presumably the "Task Name" variable currently would be changed to something like "Triggering Task Name" or "Subtask Name" Does that make sense at all?
D
Daniel Matus
Zach Our goal is to automate subtask naming to maintain a consistent naming convention from video production through to our final social media schedule.
Here is our current workflow and where the problem occurs:
Create a "Batch" Parent Task: We start by creating a parent task with a unique name, for example: RC_92725 - Batch 01.
Apply a Template: We apply a Task Template to this parent task. The template automatically creates several subtasks with generic names like Mixed Variation 1 and Mixed Variation 2.
The Manual Step (The Problem): We currently have to manually rename each subtask to match the parent (e.g., RC_92725 - Batch 01 - Mixed Variation 1). This is time-consuming and prone to human error.
Handoff to Social Media Manager: After a video is edited and approved, an automation moves the subtask to our "Content Calendar" list.
The Impact: Without the manual renaming, our social media manager receives multiple tasks all named "Mixed Variation 1" from different batches, making it impossible to distinguish which video is which.
The proposed feature—having the Parent Task Name dynamic variable available for a "Subtask Created" trigger—would allow us to completely automate Step 3, saving time and preventing errors in our publishing pipeline.
Hopefully, this gives you a clearer picture. It would be a huge workflow improvement for us.
D
Daniel Matus
Zach Hi just bumping this to the top of your inbox if you've had a chance to see the above. Thanks