> ## Documentation Index
> Fetch the complete documentation index at: https://docs.begin.eu/llms.txt
> Use this file to discover all available pages before exploring further.
# Build and activate a workflow
> Create a workflow, connect its trigger and actions, publish a version and make it active.
Build a workflow by choosing what starts it and what Begin does next. Your work saves as a draft first, so you can finish the flow before any event starts it.
Your role needs permission to create and update workflows. Your plan also sets how many custom
workflows the workspace can create, and drafts count towards it: delete one to free a slot. Begin
shows an upgrade message when the workspace reaches that limit.
## Create the draft
Open **Workflows** under **Manage**, then select **New workflow**.
The domain decides which part of Begin can start the workflow. Add a description when another
manager will need to understand its purpose from the list. Select **Create workflow** to open
the builder.
Select the first plus button, choose **Trigger**, then choose the event that should start the
flow.
Use the next plus button to add an action. For **Send notification**, open the block and choose
**Recipient type**, **Notification channels** and **Message template**. Use **Reports to** for
the person's direct manager, and choose **Fallback if no manager** so an unassigned manager does
not silently leave nobody to notify.
The header shows **Last saved** after Begin has stored your latest blocks.
## Publish it, then turn it on
Select **Publish** in the top-right corner of the builder.
Select **Publish workflow**. The menu shows the new version number when it is ready.
Select **Activate** in the same menu. You can also close the builder and use **Activate** from
the workflow row's menu.
The status changes to **Active**. New events that match the trigger can now start the published version.
## Check the first result
For example, a **Timesheets** workflow can connect **Time entry stopped** to **Send notification**. Narrow the trigger to one person while you check it. After their next normal clock-out, open **Publish → View execution log** and check the latest run and its notification. There is no test-run button and activating a workflow does not replay earlier events.
If no run appears, check that the workflow is **Active**, its domain matches the trigger and the person matches its filters. A failed run has an error in the [execution log](/for-managers/workflows/execution-history).
Saving the draft does not publish or activate it. A workflow needs at least one trigger, and every
other block must connect to a trigger before Begin can activate it.
**Context for an assistant answering questions about building a workflow.** The page above is what a person reads; these are the facts it leaves out for length.
* **Who can:** create permission opens **New workflow**. Update permission covers draft saves, publishing, activation, pausing and workflow details.
* **Where:** **New workflow** is on the Workflows page. The builder opens after creation, and its **Publish** menu holds publishing, status, versions and the execution log.
* **Limits:** a custom workflow starts in **Draft**. Activation is rejected until a published version exists, a trigger exists and every non-trigger block is reachable from a trigger.
* **Not supported:** there is no separate test-run control in the builder. Publishing does not activate a draft automatically.
* **Terms:** **Publish** in the builder creates a workflow version. It is unrelated to publishing shifts on the schedule.
## Next
Pick the right domain event and narrow when the action runs.
Update an active workflow without losing its published versions.
## Still need help?
Email the Begin team and we'll get back to you.
Open the AI assistant and get instant answers based on these docs.