Falaah Falaah AI

Triggers & Schedules

Understand the event triggers and scheduled times that start Muin workflows: from real-time events to cron-based schedules.

Every workflow starts with a trigger: the condition that causes it to fire. Muin supports real-time event triggers and scheduled (time-based) triggers.

Event Triggers

Event triggers fire when something happens in Muin. Choose one when you want an immediate, condition-based response.

Finance Events

Trigger Fires when
Invoice created A new invoice is saved
Invoice approved Invoice moves to Approved status
Invoice overdue Invoice passes its due date unpaid
Bill created A new bill is received
Payment received An inbound payment is recorded
Expense submitted An employee submits an expense report

Document Events

Trigger Fires when
Document uploaded A new document is added to the library
Document processed AI processing completes
Document expiring A document’s expiry date is N days away
Signature requested An e-signature request is sent
Signature completed All signatories have signed

HR Events

Trigger Fires when
Employee created A new employee record is added
Employee offboarded An employee’s status is set to Terminated
Certification expiring A certification expires within N days
Policy published A new compliance policy is activated

Vendor Events

Trigger Fires when
Vendor created A new vendor record is added
Vendor verified Verification status changes to Verified
Vendor document expiring A vendor-submitted document nears expiry

Nonprofit Events

Trigger Fires when
Donation received A new donation is recorded
Pledge fulfilled A pledge payment is completed
Grant awarded A grant application is approved
Volunteer registered A new volunteer signs up

Form Events

Trigger Fires when
Form submitted A public form receives a new submission

Scheduled Triggers

Scheduled triggers fire on a time-based cadence regardless of activity. Use them for regular summaries, compliance checks, and periodic reminders.

Schedule Options

Option Example use
Every hour Check a shared inbox at a set minute past each hour
Every day Send a daily cash-flow summary every morning at 8:00 AM
Every weekday Post a standup reminder Monday to Friday at 9:00 AM
Every week Send a weekly invoice aging report every Monday
Every month Generate a monthly compliance report on the 1st
Custom Anything else, written as a cron expression

Setting Up a Schedule

  1. In the workflow builder, select Scheduled as the trigger type
  2. Pick how often: Every hour, Every day, Every weekday, Every week, Every month or Custom
  3. Pick the day and time. The form says the schedule back in words, for example “Every Monday at 8:00 AM”
  4. For Custom, enter a cron expression (e.g., 0 9 * * 1-4 for Monday to Thursday at 9 AM). The form names anything wrong with it before you can save

Times are your organization’s local time, set in Settings under your organization’s time zone. A schedule at 8:00 AM runs at 8:00 AM there, before and after daylight saving time changes. Automations can use a different time zone when they need one.


Trigger Conditions (Filters)

After selecting a trigger, add conditions to filter which events actually fire the workflow:

  • Amount: e.g., only fire for invoices over $10,000
  • Category / Type: e.g., only for “IT Vendor” category vendors
  • Status: e.g., only when an invoice moves to “Overdue” (not just any status change)
  • Assigned user: e.g., only for records assigned to a specific team member
  • Custom field value: filter on any custom field

Conditions use AND logic by default. Add OR groups for more complex logic.


Testing a Trigger

Before activating a workflow, test it with a real event:

  1. Click Test Trigger in the workflow builder
  2. Select a recent record that matches your trigger conditions
  3. Muin simulates the workflow run and shows what each step would do
  4. Confirm the output looks correct, then Activate

Trigger Health and Auto-Suspend

A trigger can fire and still fail to start its workflow: the start can raise an error, or the workflow can refuse it. Muin records every failed start, so a stopped automation does not go unnoticed.

Open Sidebar → Automation → Overview, find the workflow, and click Triggers. Each trigger shows its health:

Badge Meaning
OK The last start worked
N failed starts The last N starts failed in a row. “Last start failed: …” shows the most recent error
Suspended The trigger is off and no longer fires. The panel shows the reason
  • One successful start resets the count to zero.
  • After 5 failed starts in a row, Muin turns the trigger off. The reason reads “Auto-suspended after 5 consecutive failed starts. Last error: …” and the workflow’s alert recipients are told (see Failure Alerts).
  • Each failed start is also listed with your organization’s async failures under the source Workflow triggers, with the data the trigger had built. From there it can be re-fired with the same data. Only a failed event can be re-fired. After the run data retention window that data is cleared, and the event shows “This failed start is older than the run data retention setting, so its input was cleared and it cannot be re-fired.” Submit or trigger it again instead.
  • A re-fire that fails again shows its new error on that event, but it does not add to the trigger’s failure count and never suspends the trigger. Only new starts count.
  • Editing a workflow’s trigger keeps its health: the failure count, the last error and any suspension carry over to the edited trigger. Failed starts from before the edit can still be re-fired; they start the workflow through its current trigger of the same kind.

Resuming a suspended trigger

Fix the cause first, using the last error in the reason. Then click Resume trigger on the suspended trigger. The trigger turns back on and its failure count goes back to zero. Resuming needs permission to manage workflow triggers; without it the button is not shown.

Resume trigger appears only on a trigger that Muin suspended because its starts kept failing. A trigger that is off for another reason, for example because its module or your organization’s workflows are paused, is turned back on by whoever owns that pause.


Next Steps