Falaah Falaah AI

Automations

Build no-code WHEN–IF–THEN automations: react to document events or schedules, filter with conditions, and notify, assign, escalate, or run AI agents.

Automations are Muin’s no-code rules engine: WHEN something happens, IF it matches your conditions, THEN take action. They handle the routine follow-through, notifications, assignments, escalations, so nothing waits on someone remembering to check a queue.

You’ll find them alongside your workflows at Workflows, where the gallery, your defined automations, and run history live together.

The Three Parts of Every Automation

WHEN · the trigger

  • Document events: a document is created, updated, or changes status
  • Schedule: run at a recurring time
  • Webhook: an external system calls in
  • Manual: you trigger it yourself (great for testing)

IF · the conditions

Narrow the trigger to exactly the cases you mean. Conditions can match on amount, status, business status, vendor name, document type, category, due date, and who submitted it: combine them to express rules like “invoices over $5,000 from new vendors.”

THEN · the actions

  • Notify: email, Slack, or in-app notification to the right people
  • Update the document: set status or fields
  • Assign or create a task: put the follow-up on someone’s plate
  • Run an AI agent: hand the item to an agent for processing
  • Call a webhook: push the event to an external system
  • Escalate: route to a manager when thresholds are crossed

Building One

  1. Open Workflows and create a new automation: start from scratch, from a template, or by describing what you want in one sentence (Growth and above).
  2. Pick the trigger, add conditions, choose actions. Conditions are rows in plain words, is, is not, is more than, is at least, is less than, is at most, contains, and anything the rows cannot say is written as an expression instead.
  3. Test it before you rely on it. A test run shows what each step would do on a sample; nothing is sent, assigned or posted. Manual test runs are rate-limited to protect your quota.
  4. Review, then switch it on. Before a rule goes live you see what starts it, what it will do and who it affects. Switching it on is refused if the rule changed after you reviewed it. You can switch it off any time without deleting: the rule keeps its configuration and history.

Need something a single rule cannot express? Open the Advanced editor: it is a change of view, not a conversion, and the rule you built is the document you land on.

Quotas and Limits

The number of active automations follows your subscription tier. If you hit the quota, deactivate rules you no longer need or consolidate overlapping ones: a single automation with good conditions often replaces several narrow ones.

Automations vs. Workflows

Automations are single-rule reactions: one trigger, one set of actions. For multi-step orchestration with stages, approvals, and branching, build a workflow instead, and let automations handle the simple reflexes around it.