How to automate Moodle without a new plugin for every job

Every way to automate Moodle in 2026: core event monitoring, Workplace dynamic rules, Catalyst's plugins, Zapier and n8n, and a node editor inside Moodle.

Drawing of three blue machines connected by belts, with a person beside them reading a clipboard.

You have five real options, and which one fits depends on one question: does the automation need to act inside Moodle, or only tell another system that something happened?

  • Only notify people: core Event monitoring. It is free and already installed, but it can only send messages.
  • Act inside Moodle, and you pay for Workplace: dynamic rules.
  • Push Moodle events to another system: an event plugin such as Catalyst’s Event Trigger, or a webhook plugin, feeding Zapier, Make or n8n.
  • Pull from Moodle on a schedule: Zapier’s Moodle app or n8n calling Moodle’s web services.
  • Build workflows that act inside Moodle, on the free LMS: a workflow engine that runs in Moodle. We built an open source one, Autoflow, and it is the reason for this post.

Each one is below, with what it can’t do.

Why is this a problem at all?

Every school on Moodle has the same list. Enrol students in Year one when they finish the foundation course. Email a learner who hasn’t logged in for two weeks. Add new staff to the right cohort. Tell the CRM when someone completes a paid course.

Moodle has the raw parts. Almost everything that happens fires an event, and almost everything you can do is a web service function. What it doesn’t have, in the free LMS, is a place to wire “when this happens” to “do that” without writing PHP. So each item on the list becomes a small custom plugin, and each plugin is one more thing to review and upgrade.

What can core Event monitoring do?

Moodle ships with Event monitoring (tool_monitor). A teacher or admin picks an event, for example a forum post, sets a threshold such as five times in 30 minutes, and users who subscribe get a notification.1

That is all it does. It sends messages. It can’t enrol anyone, change a grade or call another system. It is also off by default, and MoodleDocs says why: performance. Turn it on for alerts, not automation.

What are Workplace dynamic rules?

Moodle Workplace, the paid edition sold through Moodle Partners, has the closest thing to a built-in automation tool. A dynamic rule is “IF conditions THEN actions”, checked against the users in a tenant. Most conditions are event based, such as course completion. Others are checked on every cron run.2 Workplace plugins add their own conditions and actions, and features like certificates and badges use the same rules underneath.

It is a good design. But it only exists in Workplace, conditions are combined with AND, and you get the conditions and actions Workplace ships, not your own.

What about Catalyst’s Event Trigger and Dataflows?

Catalyst IT wrote Event Trigger (tool_trigger), an admin tool that starts a workflow when a Moodle event fires. Steps look up extra user or course data, filter on conditions, then send an email or an HTTP POST.3 It is the usual way to push Moodle events to an outside service. It has a branch for Moodle 4.4 and later.

It only reacts to events, so nothing time-based. For scheduled work Catalyst points people to its newer plugin, Dataflows (tool_dataflows), a general processing engine built from connector, flow and trigger steps, with conditional steps that branch.4 Dataflows is aimed at data jobs: query something, transform it, send it somewhere, retry if the API is down.

Both are open source and both are made by people who know Moodle well. They are tools for integration engineers, and they are configured that way.

Can Zapier, Make or n8n do it instead?

Yes, for anything where Moodle is the source of data and the action happens elsewhere. Two ways in:

  • Pull. Zapier has a Moodle app. Its Moodle triggers poll, which means Zapier asks Moodle every few minutes whether something changed, rather than Moodle telling it.5 n8n has no built-in Moodle node that we could find, so you call Moodle’s REST web services with n8n’s HTTP Request node and a token.
  • Push. Install a plugin that fires a webhook on Moodle events, such as Event Trigger or Poodll’s Trigger plugin, which covers user created, quiz submitted, course enrolment and course completed.6 Point it at a Zapier, Make or n8n webhook.

The catch is the other direction. When the workflow needs to do something in Moodle, it calls a web service function with a token, and that token belongs to a Moodle user. Give it a site admin’s token and every Zap that runs has admin rights over your LMS. The safe setup is a dedicated user, a custom external service that only exposes the functions you need, and a token restricted by IP and expiry. Skip any of the three and the integration becomes the weakest point of your site.

You are also now running part of your LMS logic on someone else’s platform, with its own pricing and its own outage days.

What does a workflow engine inside Moodle look like?

That is what we wanted, so we built it. Autoflow is a GPL admin tool for Moodle 4.5 to 5.3. You build a workflow in a node editor, the same idea as n8n, and Moodle runs it:

  • Triggers: by hand, on a schedule (cron, in the site’s timezone), or on any Moodle event.
  • Steps: conditions with Yes and No branches, variables, notifications, enrol or unenrol a user, add to a group or a cohort, an HTTP request to another service, and one node that calls any web service function installed on the site.
  • Data between steps: placeholders such as {{trigger.relateduserid}} in any setting.
  • Run history with each step’s output or error.

The design choices matter more than the feature list, because this is a tool that lets admins call Moodle functions from a diagram:

  • A workflow runs as a real Moodle user, the person who saved it unless they pick someone else, and picking someone else needs the “log in as” permission. Every step goes through the same capability checks as Moodle’s web services.
  • Events are caught with one cached lookup and the workflow runs later as a background task, so no page gets slower.
  • HTTP requests go through Moodle’s own curl class, so the site’s blocked hosts apply, including to redirects.
  • A workflow that triggers itself stops after three levels.

It is stable (1.0). The code and every test report are public, from PHPUnit on six Moodle and PHP combinations to mutation testing and Playwright runs in a real browser. The Autoflow page has screenshots and the live results.

Which one should you pick?

You want toUse
Alert a teacher when something happens oftenCore Event monitoring
Rules inside Moodle and you run WorkplaceDynamic rules
Push events to your CRM or data warehouseEvent Trigger or a webhook plugin
Nightly data jobs with retriesCatalyst Dataflows
Moodle data into Slack, Sheets or email toolsZapier, Make or n8n, with a scoped token
Workflows that change things inside free MoodleA workflow engine in Moodle, such as Autoflow
One rule that is central to how you runA small custom plugin, still

The last row is not a joke. If one automation carries real business logic, like how a university awards credit, it deserves code with tests, not a diagram someone can edit on a Friday afternoon. Tools like these are for the long tail of small jobs. For the rule that matters, get it built properly.

Sources

  1. MoodleDocs, Event monitoring. ↑

  2. MoodleDocs, Dynamic rules (5.3). ↑

  3. GitHub, catalyst/moodle-tool_trigger README, checked 2 November 2026. ↑

  4. Catalyst, Dataflows plugin for Moodle. ↑

  5. Zapier, Moodle and Webhooks integrations. ↑

  6. Poodll, Introduction to Poodll Trigger and Zapier. ↑

Need a Moodle plugin built or rescued?

Tell the scoping assistant what you need. You get a fixed price and a timeline in a few minutes, and an engineer reviews it within one business day.

Get a fixed quote