Skip to content

Launching

Process launching in Tallyfy

Launching transforms templates into active, trackable processes with specific assignments and deadlines. When you launch a process, you create a running instance that team members work on.

Templates are reusable blueprints. Launched processes are specific instances executing those instructions. Each process operates independently with its own timeline, participants, and progress tracking.

Why use process launching?

Launching turns documented procedures into active work with tracking and accountability. Task assignments reach team members at the right time with context.

Templates vs. processes

  • Templates - Reusable master workflow designs with standardized step sequences (e.g., “Client Onboarding” template)
  • Processes - Individual workflow instances executing template instructions for specific cases (e.g., “Coca-Cola Client Onboarding” launched today)

Each process needs a unique name for tracking and monitoring multiple concurrent executions.

Launch a process every time you need to run the workflow from a template.

Key concepts

Process independence from template changes

Template modifications only affect future launches. Running processes continue with their original instructions - they won’t change mid-flight. This protects active workflows while enabling continuous template improvement.

Launch methods

  • Manual launching - From the Templates interface
  • Automatic triggers - API calls, webhooks, or scheduled automation
  • Cascade launching - When tasks in other processes complete
  • Web form integration - Through form submissions
  • Email triggers - Send messages to designated addresses
  • Magic links - External stakeholders can initiate without login

How launch methods work together

This diagram shows how all launch methods converge to create an active process from a template.

Diagram

Diagram description: This diagram demonstrates the six different methods available to launch a process from a master template in Tallyfy, with all paths converging to create a single active process instance. The visual structure emphasizes that regardless of the launch method chosen (manual, API, task trigger, web form, email, or magic link), the result is always the same: an independently running process with its own timeline and assignments.

What to notice:

  • All six launch methods lead to the same outcome - an active process instance
  • Every launch method allows optional customization before the process starts
  • The template remains unchanged while each process runs independently with its own timeline

Customization during launch

When launching a process, you can:

  • Set a unique process name
  • Change task assignments
  • Adjust deadlines
  • Add guest participants
  • Fill in the kick-off form with relevant data

Alternatively, set up auto-naming to automatically generate process names from kick-off form field values.

Next steps

Learn how to manually launch a process for full control over process details. For automation, explore launch triggers that start workflows automatically based on external events.

Launching > Launch manually

Manual process launching in Tallyfy allows you to initiate workflow instances from templates with complete control over timing and customization by selecting a template naming the instance and clicking launch to create an active trackable process.

Tutorials > Launch a process

This tutorial demonstrates launching workflow processes in Tallyfy by selecting templates from the sidebar completing optional kick-off forms naming the process instance and clicking launch to create active trackable workflows with automatic notifications and progress monitoring.

Tracking And Tasks > An overview of processes

A process in Tallyfy is a running instance of a template that transforms your workflow blueprint into actual trackable work with unique naming audit trails and the ability to add one-off tasks while maintaining independence from template updates.

Launching > Triggers

Tallyfy offers seven flexible process launch triggers including manual buttons API calls email triggers magic links scheduled automation task completion chains and kick-off forms to accommodate different organizational needs and technical capabilities while enabling automatic data pre-population for seamless workflow initiation.