Automations Overview
Build workflows, including smarter Document completed conditions
Vaasu Guduguntla
Last Update 4 days ago
Overview
Automations connect triggers, conditions, waits, and actions so the repetitive work in your business runs on its own. Document completed conditions can now watch several file sources, not only the previous send step.
📁 Document completed – Select file
When a condition checks that a file is completed, choose how TalleFlow picks which file counts:
- Previous steps – A file sent earlier in the same automation.
- Specific templates – One or more document templates on the project.
- Any project file – Any completed file on the project.
- Staff Teams: assign groups on projects and tasks
If the file is not finished yet, the automation can wait and continue when the matching document completes.
🔧 Contact Form Submitted conditions
Automations triggered by Contact Form Submitted can now filter on Project stage, the same way brochure and questionnaire triggers do.
👥 Staff Team targets in the builder
- Save and reload – Create task and Assign team member to Project keep the Staff Team you picked.
- Deleted team warning – If a step still points at a removed Staff Team, you see an inline warning without losing the automation.
- Edit anyway – You can fix other steps even when a Staff Team reference is stale; save is not blocked solely for a missing team.
- Staff Teams: assign groups on projects and tasks
👥 Assign a create-task action to a team and one person
In the automation builder, a Create task action can target a Staff Team and also name one teammate on that team.
- Runtime – TalleFlow assigns the task to the named person and still respects the staff team on the action.
- Canvas – The action card shows both the team and the chosen assignee.
✅ Approval gates before actions run
📚 Learn More
- Staff Teams: assign groups on projects and tasks
- Automation triggers and client notifications
- Using Smart Tags in Automations
Approve automation steps before they run
