> For the complete documentation index, see [llms.txt](https://documentation.taskmaverick.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.taskmaverick.com/processes/how-to-guides/build-a-process.md). # Build a Process The Process Builder is a visual canvas where you design your workflow — add Activities, connect them with Conditions, and define where each step should land. ## Why use the Process Builder? The Builder is where your workflow takes shape. You define every step, every rule, and every destination in one visual interface — then publish it and let the system run it automatically. ## How to build a Process ### Create the Process 1. Go to **Missions → Within Processes → New Process** 2. Fill in the required fields:

Field	Required	Limits
Name	Yes	Max 36 characters, must be unique
Tag	Yes	Same tag system as Missions
Category	Yes	Same category system as Missions

3. You'll land in the **Process Builder**. ### Add Activities Activities are the steps in your Process. Click the **+** button to add one.

Type	What it does	Requirements
Mission	Posts a Task, Survey, Checklist, Media, or Test to a board	Must be Published
Ticket	Triggers an alert to a Ticket Board	Must be Published
Delay	Waits a set amount of time before the next step triggers	Define weeks, days, hours/minutes

Activities are arranged in **levels**. Level 1 runs when the Process starts. Level 2 runs when conditions on level 1 are met. And so on. You can have multiple Activities on the same level — they run independently. ### Set the destination Every Activity needs a destination — where it should appear on mobile.

Destination type	How it works
Specific value	You pick the exact team, person, or ticket board
From Trigger	Uses the team/unit/person from the Trigger — so the same Process adapts to different locations
From previous Activity	Routes to the same board as an earlier step
Performer of [Activity]	Routes to the personal board of whoever completed a specific earlier Activity

**Example:** A room cleaning Process uses "From Trigger" for the cleaning team's destination. When the Process runs for the Downtown Hotel, it goes to that hotel's cleaning team. When it runs for the Airport Hotel, it goes to theirs — same Process, different destinations. ### Add Conditions Conditions go between levels. They define the rules that decide which Activities trigger next. To add a Condition: select an Activity → click the condition area below it → define the rule.

Type	What it evaluates	Example
Mission Closed	The previous Activity was completed	"When the cleaning checklist is closed, trigger inspection"
Response	A specific answer was given	"If 'bottles in stock' < 5, trigger restock task"
Rating	The Mission received a certain rating	"If rating is below 3, trigger quality alert"
Timer	The Mission wasn't completed in time	"If not closed within 2 hours, trigger escalation ticket"
Test Score	A Test result crossed a threshold	"If score < 70%, trigger training media"

Conditions support **AND/OR** logic for complex branching. Each Activity can have multiple independent condition sections, creating different workflow branches. {% embed url="" %} ### Required vs. optional Activities

Setting	What it means
Required = Yes	The Process won't complete until this Activity is closed
Required = No	Choose what happens when the Process finishes: Cancel Activity (auto-cancel it) or Keep Activity (leave it active)

## Publishing and managing your Process When the workflow is complete: 1. The Builder validates everything — all destinations, connections, and condition fields must be filled 2. Fix any red-highlighted validation errors 3. Click **Publish**

Action	What it does
Publish	Makes the Process active — Triggers start firing
Unpublish (On Hold)	Pauses — no new instances, existing ones continue
Archive	Removes from active use — can be restored later
Duplicate	Creates a copy — useful for building similar workflows
Delete	Permanently removes (only Draft, Archived, or Broken)

## Good to know * All Activities must use [**Published** Missions or Tickets](/missions/how-to-guides/publish-a-mission.md) * Maximum **500 Activity instances** per Process (warning at 100) * Conditions **cannot** be added to the last-level Activity * Destinations must be fully defined before publishing * If a Mission or Ticket used in a Process is archived or deleted, the Process status changes to **Broken** * If the same Mission is already Open or Claimed on a board and the Process triggers it again, it **won't duplicate** — the Process info is added to the existing Mission --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://documentation.taskmaverick.com/processes/how-to-guides/build-a-process.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.