Nextcloud events that start automations
· By Bee Flow · 3 min read
A new file, a tag, a calendar change or a submitted form can start an automation in Bee Flow. Which events exist, what they carry, what Nextcloud needs, and three made-up examples.

Most automations start on a timer. Every morning at nine, look at what changed. That works, but you wait, and a lot gets read that did not change. When Bee Flow runs inside Nextcloud through the Bee Flow app, Nextcloud itself can say that something happened.
This post is about those events. What the assistant does in Nextcloud when you ask it something directly is in an earlier post.
Which events there are
Once an administrator has connected Bee Flow, the connector subscribes to these events in Nextcloud:
- Files and folders: created, changed, renamed, copied, deleted, and restored where your Nextcloud has that event.
- Tags: a tag set on a file, or removed from it.
- Calendar: an event created, changed, moved or deleted.
- Forms: a submitted form, when the Forms app is installed.
- Tables: a row added, changed or deleted, when Tables is installed.
- Deck: a card created, changed or deleted, when Deck is installed.
Each of these can be the trigger of an automation you build in Bee Flow. Users and groups reach Bee Flow another way, through the regular sync.
What an event carries
Less than you might expect, and that is deliberate. A file event holds the file's id and path, whether it is a file or a folder, and who acted. A calendar event holds the identifiers of the event and its calendar, the owner and who it is shared with. Its title, time and text are not in it. A form submission says which form it was and who submitted it, without the answers. Table rows and Deck cards do arrive with their values.
When an automation needs more, a step fetches it, as the user and with that user's permissions.
Three examples
These are made up, to show the shape of it.
Invoices in a folder
A small office has a shared folder Purchasing/Incoming. Every new PDF there starts an automation. An AI step reads the supplier, invoice number, amount and due date. Those values go into a row in Nextcloud Tables, and the PDF moves to Purchasing/2026. When the step cannot read the amount, the file stays where it is and the bookkeeper gets a Talk message with a link to it.
A tag as a switch
A project team tags a contract review in Files. A first step checks that it really is that tag, so other tags do nothing. The automation then reads the document, puts a one-page summary of terms and deadlines next to it, and makes a Deck card on the team's board with the summary as its description.
A form for requests
An internal form for requesting equipment. Each submission starts an automation that fetches the answers, looks up the requested item in a table of what is in stock, and posts the request in the IT team's Talk conversation with a suggested reply.
What your Nextcloud needs
The events go through Nextcloud's Webhook Listeners app. It ships with Nextcloud but is not enabled by default:
sudo -u www-data php occ app:enable webhook_listeners
The connector registers its subscriptions within a minute. occ webhook_listeners:list should then show rows with the uri /hooks/nextcloud.
Nextcloud sends these events from background jobs. With the default cron interval an event can take up to five minutes to arrive. For invoices that hardly matters. For something a person is waiting on, it does. Dedicated workers bring it down to seconds:
sudo -E -u www-data php occ background-job:worker -v -t 60 \
"OCA\WebhookListeners\BackgroundJobs\WebhookCall"
For a permanent setup, run a few of them as systemd services. Nextcloud's documentation on Webhook Listeners has a template.
Nextcloud hands the events to the connector through AppAPI, so it does not need to reach its own public address. Triggers for Forms and Tables show up only once those apps are installed.
Where to build them
Automations are made in Bee Flow's automation builder. Pick the Nextcloud event as the trigger and add steps behind it. Before you switch an automation on, run a test. Nothing is sent or written during that run. Building automations for your own use is in every licence, and what sharing them across a team takes is on the plans page.
If your setup works differently from what is described here, tell us.