Creating Blueprints
Design automated processes in the visual Blueprint Editor. Available to managers and admins.
Create a Blueprint
- Go to Blueprints
- Click New Blueprint
- Enter a Name, optional Description, and a Department
- Click Create & Edit
You start in the editor with a Start and End node already placed.
The Visual Editor
The editor is a drag-and-drop canvas.
Adding Steps
Drag a step from the palette on the left onto the canvas. (Only one Start and one End are allowed.)
Connecting Steps
Drag from a step's bottom point to the next step's top point. Some steps have labeled outputs — for example If/Else shows Yes and No, and Loop shows Loop and Exit.
Configuring a Step
Click a step to open its settings panel. Depending on the step type you can set:
| Setting | Description |
|---|---|
| Title / Description | What the created task is called and its instructions |
| Department | Which department the task belongs to (or inherit from the blueprint) |
| Priority | Low, Medium, High, Critical |
| Dynamic assignee | Auto-assign at launch — the starter, their manager, or a chosen executive |
| Time Limit (hours) | Deadline for the step |
| Done Conditions | Requirements to complete the task (see Step Types) |
| Form Template | Pre-fill the task's conditions from a saved form |
| Attached Files | Files copied read-only into each created task |
| Visibility | Share the created task read-only with others |
Step-specific fields also appear — the If/Else decision question, Timer/Approval-Gate timeouts, Loop iterations, Auto-Assign position, and Webhook URL/headers.
Saving and Publishing
| Action | What It Does |
|---|---|
| Save | Saves your design (shows Saved when there's nothing new) |
| Publish | Makes the blueprint launchable |
| Unpublish | Returns it to Draft |
| Archive | Hides it from the list (restore later) |
Save before publishing — you can't publish with unsaved changes. Test a blueprint with a small group before rolling it out widely.
Import and Export
You can Export a blueprint to a file and Import one from a file — handy for reusing a process across projects. Importing replaces the current design.
Tips
- Keep it simple — start with a few steps, add complexity later
- Name steps clearly — the step name becomes the task title when the process runs
- Set time limits so steps don't stall silently
- Use dynamic assignees for processes anyone might start