Workflows
How to build and manage Muin's automated workflows (triggers, actions, approvals, and troubleshooting) to automate the repetitive steps across your operation.
18 questions
How do I create my first workflow?
Creating a workflow in Muin is straightforward: 1. Go to **Workflows** in the left sidebar 2. Click **Create Workflow** 3. Give your workflow a name and description 4. Choose a **trigger**: the event that starts the workflow (e.g., form submitted, document uploaded, invoice approved) 5. Add **actions**: the steps that execute when the trigger fires (e.g., send email, create task, notify team) 6. Configure conditions if you want actions to run only when certain criteria are met 7. Click **Activate** to turn the workflow on Start with a simple workflow like "When a form is submitted, send a confirmation email" and build from there. You can also browse **Templates** for pre-built workflows covering common scenarios.
What types of triggers can start a workflow?
Muin workflows support four core trigger types plus event-based triggers across all platform modules: | Trigger Type | Examples | |-------------|----------| | **Schedule** | Daily, weekly, monthly, or custom cron schedule with business hours and holiday support | | **Webhook** | HMAC-secured webhook calls from external systems | | **Manual** | Start on demand from the dashboard or via API | | **Event-Based** | Document uploaded, form submitted, payment received, vendor added, and more | Event-based triggers span all modules: | Module | Events | |--------|--------| | **Documents** | Document uploaded, processing complete, anomaly detected | | **Forms** | Form submitted, form updated | | **Finance** | Invoice created, payment received, payment overdue | | **Vendors** | Vendor added, compliance expired, contract renewal due | | **HR** | Employee onboarded, time-off requested, review due | | **Communications** | Message received, ticket created, SLA at risk | Each trigger can include conditions to narrow when it fires. For example, "When an invoice is created AND amount is over $5,000" ensures the workflow only runs for high-value invoices.
What actions can a workflow perform?
Workflow actions are the steps that execute when a trigger fires. Available actions include: - **Send Email**: send a templated email to specific recipients or dynamic contacts - **Send Notification**: push in-app, SMS, or email notifications to team members - **Create Task**: create a task and assign it to a team member or team - **Update Record**: change fields on a contact, vendor, invoice, or other record - **Create Record**: create a new vendor, contact, invoice, or document record - **Assign to Team**: route an item to a team for review or action - **Webhook**: send data to an external URL for integration with third-party tools - **Wait**: pause the workflow for a specified duration before the next step - **Condition**: branch the workflow based on field values or other criteria Actions can be chained together in sequence, and you can add multiple branches using conditions.
What happens when a workflow encounters an error?
When a workflow step fails, Muin handles it gracefully: 1. **The failed step is logged**: you can see exactly which action failed, when, and why on the run's page, opened from **Automation > Overview** 2. **The run stops as Failed**: later steps do not run (unless you have configured the workflow to continue on error) 3. **You are notified**: by default the person who started the run and the workflow owner get an in-app notification and an email. Change this under **Settings → Workflow Settings → Alerts & publishing** 4. **You can retry**: open the failed run from **Automation > Overview** (`/workflows`), review the error, and click **Retry** to re-execute from the failed step Common failure reasons include invalid email addresses, permission issues, or external webhook timeouts. The error message in Run History tells you exactly what went wrong so you can fix the root cause.
Are there pre-built workflow templates?
Yes. Muin includes a library of 25 pre-built workflow templates for common business processes: - **Vendor Onboarding**: document collection, risk assessment, compliance checks, and approval routing - **Invoice Approval**: route invoices by amount with auto-approval thresholds, notify on decision - **Document Processing**: notify the team when a document finishes processing, flag anomalies - **Form Follow-Up**: send confirmation email on submission, create task for review, notify assignee - **Payment Reminder**: send reminders at 7 days, 3 days, and 1 day before invoice due date - **Employee Onboarding**: create tasks for IT setup, HR orientation, and manager check-in - **Expense Approval**: smart routing based on amount, category, and department - **Grant Application Review**: committee review, board vote, and applicant notification Plus 17 more templates across Finance, HR, Vendors, Contracts, Compliance, Procurement, and Nonprofits. Browse templates at **Workflows** --> **Templates**. Click **Use Template** to create a copy you can customize with your own recipients, messages, and conditions.
What's the difference between an automation and a workflow?
An **automation** is a single WHEN–IF–THEN rule: one trigger (a document event, schedule, webhook, or manual run), optional conditions (amount, status, vendor, type, due date…), and one set of actions (notify, assign a task, update the document, run an agent, call a webhook, escalate). A **workflow** is multi-step orchestration: stages, approvals, branching. Use workflows for processes, automations for reflexes around them. Both live on the **Workflows** page.
How do I test an automation before turning it on?
Use the **manual trigger** while the automation is still inactive: it runs the rule once so you can confirm the conditions match what you expect and the actions land where they should. Manual test runs are rate-limited, so test deliberately rather than in a loop. When you're satisfied, **activate** it. You can deactivate any time without losing the configuration or its run history.
Is there a limit on how many automations I can have?
The number of **active** automations follows your subscription tier. Deactivated automations don't count against it, so keep experimental rules off until you need them. If you hit the quota, look for overlap first: one automation with well-chosen conditions often replaces several narrow ones.
I turned my workflow on but it never runs. Why?
A workflow runs only when it has a **published** version. Switching it to Active is not enough on its own. To publish it: 1. Open the workflow in the builder 2. Click **Review & publish** 3. Read the four sections - **Starts when**, **It will**, **Who feels it**, **Tested** 4. Click publish Two things to know about that gate: - **Publish stays disabled until the summary has rendered.** You cannot publish a summary nobody has seen. - **If the workflow changed after you opened the review**, publishing is refused with "This workflow changed since you reviewed it. Reload the review." Nothing goes live until you have read the current version. Runs already in flight finish on the version they started on, so publishing never changes a run mid-way.
My workflow is stuck waiting on a person. How do I find out who?
Open the run from **Sidebar → Automation → Overview** and click it. The step reads **Waiting on <name> · assigned <duration>**, so you can see both who holds it and how long it has been there. If it reads **Waiting - unassigned**, the step has no owner and nobody will ever act on it. Fix the definition: 1. Open the workflow in the builder 2. Select the **Wait for a person** step 3. Set who acts - a role or a specific person 4. Review and publish Saving a person step with no assignee and no assignment step before it is refused, so this only happens on older definitions. To unblock the run you already have, use **Advance Workflow** on the run page.
Can I turn our written procedure document into a workflow?
Yes. **Sidebar → Automation → Workflow Catalog → Build with AI** reads a procedure document and drafts what it describes. 1. Drop in a **PDF**, **.docx** or **.doc** file - up to 10 MB - or type a description of at least 10 characters 2. Muin splits it into procedures and drafts each one 3. Each row gets a kind: **Workflow**, **Agent**, **Policy**, or **Manual** (a step a person does, recorded so it is not missed) 4. Review each row, then **Approve** or **Discard** it There is deliberately no "Approve all" - each approval creates a real object in your organization. **Everything it creates is inactive.** An approved workflow still has to go through the normal review gate before it runs, and an approved agent still has to be set up. Nothing imported starts working on its own. Limits: up to 40 procedures per document, and 5 imports per organization per hour.
A workflow run failed. Can I retry it?
Yes, when the run is **failed**, **timed out** or **cancelled**. Open it from **Sidebar → Automation → Overview** and click **Retry** (on a cancelled run the button reads **Restart**) and confirm. A failed or timed-out run resumes from the step it stopped on; a cancelled run starts over from the first step. On any other status there is no Retry button, and a step's **Retry from this step** stays disabled with "Only a failed, timed-out or cancelled run can be retried." Before you retry, read the failed step. The run page shows each step with its input, its output, and the error code, message and detail - which is usually enough to tell whether retrying will help or whether the definition needs fixing first. **A retry executes the remaining steps for real**, with real side effects. It is not a simulation. If a step already sent an email or made a payment before failing, retrying from a later point will not undo it. A run that is still going offers **Cancel Workflow** instead. Cancelling stops it; anything it already did stays done.
How do I reuse one validation rule across several workflows?
Save it once as a business rule set, then pick it by name in each workflow step that needs it. 1. Go to **Sidebar → Automation → Business Rules** and create a rule set: rules that check form data, or a decision table that picks an outcome. 2. Under **Test with sample data**, enter sample field values and click **Run test**. Nothing is saved; you see what the rules decide. 3. In a workflow step, choose the set from **Choose a rule set**. Editing a rule set changes every workflow step that uses it, so test the change before you save it. When **Require a second person to publish** is on and the set is in use, your edit waits until someone else publishes it.
How do I find or export past workflow runs?
Go to **Sidebar → Automation → Overview**. The run list filters by status, automation, start date, who started it and how it started, and **Search runs** matches text in the automation name, the document, the step or the error. **Export CSV** downloads the runs that match your current filters, up to 5,000 rows. On a run page, **Export steps CSV** downloads that run's step log. Run data retention (365 days by default) clears the inputs and outputs of completed and cancelled runs after that window. The run itself, its steps, timings, errors and audit trail stay, so they still appear in the list and the export. Failed and timed-out runs keep their data so they can be retried.
Who gets told when a workflow fails?
By default, the person who started the run and the workflow's owner. The owner is the workflow's owner, or its author when no owner is set, plus whoever last edited it. Change it under **Settings → Workflow Settings → Alerts & publishing → Failure alerts**: add a role (everyone with that role) or a named person. One alert reaches at most 25 people. Alerts of the same kind for the same workflow are sent at most once every 15 minutes; the next alert says how many failures were held back.
Can I require a second person to publish a workflow?
Yes. Turn on **Require a second person to publish** under **Settings → Workflow Settings → Alerts & publishing → Publishing**. It is off by default. When it is on, anyone who has edited the workflow's content, not only the last editor, cannot publish it; someone else with edit access reviews and publishes it. Only a workspace owner or admin can turn the setting on or off, and every change is recorded in the workflow audit trail.
How do I retry many failed workflow runs and trigger starts at once?
Go to **Administration → Async Failures**. Tick each workflow failure you want, or **Select every retryable failure**, then click **Retry selected** and confirm. A failed run resumes from the step it stopped on, and a failed trigger start fires again with the payload it received. Steps that send messages or write records run again. The result reads "Retried N of M"; any that could not be retried stay selected with the reason beside each one. A run that stops again is listed as not retried, with "The run was retried but stopped again:" and the new error. A trigger start that works while its trigger is still suspended carries a note: resume the trigger on the workflow's Triggers panel, or new events will not start it.
Why can't I approve this workflow step?
Two rules keep a second pair of eyes on every approval: - **The person who started the run cannot approve its Approval step.** Only the owner can, and only by adding a note saying why; the note stays on the record. - **In an Approval step set to "Each approver, in order", a person who approved an earlier level cannot approve a later level.** Only the owner can, again with a note. Anyone else is refused, and the task waits for another approver. Ask one of the other approvers, or the owner, to decide it.
Other FAQ Categories
Didn't find your answer?
Our support team is happy to help with any questions.
Contact Support