Coming soon. The Wiki is in active development, so features and these docs may still change. Early adopters: contact us for access.

Events Reference

Every event the Wiki raises, for policies, automation and plugins: pages, spaces, Q&A, calendars and the platform

The Wiki raises an event for each important operation: a page published, a comment added, a question asked, a space imported, a user created. Policies, automation and plugins react to these events: a policy or plugin can stop an operation before it happens, and automation or a plugin can act after it has happened.

1. Before and after

PhaseWhenWhat subscribers can do
BeforeBefore the operation runsStop it with a message (on events marked *blocking*), or adjust the few fields the event allows. They have a few seconds at most.
AfterOnce the operation has succeededReact to it: send an alert, notify another system. They can't undo or slow down the operation.

Passwords, keys and similar secrets are never included in an event. Some events leave out who acted: a vote (qna.vote) doesn't say who voted.

2. Delivery

  • After-events are saved in the database together with the change that caused them, so they are never lost when a server restarts, and each is delivered once across all servers of a cluster.
  • They usually arrive within a few seconds.
  • A subscriber that fails is retried with increasing delays (up to 8 times by default, over several hours); after that the delivery is marked as failed and kept for 30 days. Administrators see deliveries under Settings → Advanced → Event deliveries (events:admin).
  • The same event can occasionally be delivered twice (for example after a server restart mid-delivery). Plugins and integrations must handle repeats.

In the tables, yes · policies marks events that also accept organization policies; plain yes events accept only platform policies and plugins. Events marked no can't be stopped.

3. Wiki events

What happens in spaces, pages, Q&A and calendars.

4. Spaces and imports

EventPhasesBlockingWhen it happens
space.createbefore, afteryes · policiesA wiki space is created. Policies can, for example, forbid internal or public spaces.
space.deletebefore, afteryes · policiesA wiki space is deleted, with its members' roles in it.
space.import.completeafternoAn import into a wiki space ended: done, failed or cancelled, with how many pages it created, updated and left out.
space.import.startbefore, afteryes · policiesAn import of another wiki's export (Confluence) or of Markdown files into a wiki space is started. Policies can refuse imports, for example outside some spaces.
space.archivebefore, afteryes · policiesA wiki space is archived: read-only for everyone until restored. Policies can, for example, keep certain spaces from being archived.
space.label.updatebefore, afteryes · policiesA wiki space's labels change (the same labels pages carry), with the labels added and removed.
space.restorebefore, afteryes · policiesAn archived wiki space is restored: its pages can be written again.
space.updatebefore, afteryes · policiesA wiki space's name, description, visibility, icon, category or status change (archiving and restoring also raise space.archive and space.restore).
space_categories.updatebefore, afteryesThe list of space categories (which group the space list) is saved. Removing a category leaves its spaces in none.

5. Mirror spaces

EventPhasesBlockingWhen it happens
mirror.convertbefore, afteryes · policiesA mirror space is converted into a normal space: its mirrors are removed and its pages can be edited in the wiki.
mirror.createbefore, afteryes · policiesA mirror is set up in a wiki space: the space's pages will follow a git repository's docs or uploaded archives. Policies can, for example, allow only some hosts or repositories.
mirror.deletebefore, afteryes · policiesA mirror is removed from a wiki space. Its pages stay.
mirror.failedafternoA sync of a mirror failed or was cancelled, with the reason.
mirror.suggestion.createafternoA reader suggested an edit to a mirrored page: a pull or merge request was opened on the source.
mirror.syncedafternoA sync of a mirror finished: how many pages it created, updated and removed.
mirror.updatebefore, afteryes · policiesA mirror's source, schedule or settings change.
mirror_settings.updatebefore, afteryesThe installation's mirror settings (mirrors allowed, who sets them up, the largest archive, internal git hosts) change.

6. Pages

EventPhasesBlockingWhen it happens
html_block.createbefore, afteryes · policiesA space admin saves an HTML block for a wiki space's pages (new or changed: every save is a new block). Policies can, for example, refuse HTML that loads scripts.
page.attachment.createbefore, afteryes · policiesA file (an image, a video or subtitles) is uploaded to a wiki page. Policies can, for example, refuse uploads in some spaces.
page.attachment.deletebefore, afteryes · policiesA file (an image, a video or subtitles) is deleted from a wiki page, also from the published versions that showed it.
page.comment.createbefore, afteryes · policiesSomeone comments on a wiki page: a new thread on the page or on a stretch of its text (inline), or a reply in a thread.
page.comment.deletebefore, afteryes · policiesA comment on a wiki page is deleted by its author or a space admin; deleting a thread's first comment deletes its replies.
page.comment.updatebefore, afteryes · policiesA comment on a wiki page is changed by its author (action edit), or a comment thread is resolved or reopened (resolve, reopen).
page.createbefore, afteryes · policiesA wiki page is created (as a draft): blank, from one of its space's templates (template), or as a copy of another page (copied_from). A whiteboard is created the same way with kind board (live at once, no draft).
page.deletebefore, afteryes · policiesA wiki page and the pages under it go to the space's trash.
page.label.updatebefore, afteryes · policiesLabels are added to a wiki page or removed from it.
page.lock.createbefore, afteryes · policiesA wiki page is locked, with the pages under it: in mode view only the people and groups on the lock see them; in mode edit everyone who reads the space sees them and only those on the lock as Can edit change them. A lock only narrows what space roles allow.
page.lock.deletebefore, afteryes · policiesA wiki page's lock is removed: by someone who may edit the page, or from the space's Locked pages settings by a space or super admin (from_settings, with their note). The pages fall back to the lock above them, if any.
page.lock.updatebefore, afteryes · policiesA wiki page's lock changes mode (previous_mode) or who is on it.
page.movebefore, afteryes · policiesA wiki page moves to another parent in its space (a change of order among siblings raises nothing).
page.publishbefore, afteryes · policiesA wiki page is published: its draft becomes its next version, which every reader of its space sees. Policies can, for example, require a review first.
page.purgebefore, afteryes · policiesA deleted wiki page and the pages deleted with it are removed for good: by a space admin (before and after), or by the trash retention job (after only).
page.reactionafternoSomeone likes or dislikes a published wiki page ("Was this page helpful?"), changes their answer or takes it back.
page.restorebefore, afteryes · policiesA wiki page comes back from the trash with the pages deleted with it.
page.review.decidebefore, afteryes · policiesA review request on a wiki page is answered by its reviewer (state approved or changes) or cancelled by the person who asked or a space admin (cancelled).
page.review.requestbefore, afteryes · policiesSomeone who edits a wiki page asks another editor of the space to review its draft, optionally by a date (one event per reviewer).
page.review_by.setbefore, afteryes · policiesSomeone who edits a wiki page sets the date it should be reviewed by, or clears it.
page.schedule.cancelbefore, afteryes · policiesSomeone who edits a wiki page cancels its scheduled publish, or the scheduled publish is dropped without being made (its draft or title changed, its maker no longer edits the space, the publish was refused); a drop raises the after-event only.
page.schedule.setbefore, afteryes · policiesSomeone who edits a wiki page schedules its draft to be published at a time (or moves the time). The publish itself raises page.publish, as the person who scheduled it.
page.template.createbefore, afteryes · policiesA wiki template is made, in a space or in the template library (scope): written in the template editor, from a page (from_page), with the pages under it when asked, as a customised copy of a library template, or of a whiteboard (kind board, from_board).
page.template.deletebefore, afteryes · policiesA template of a wiki space or of the template library (scope) is deleted. Pages and whiteboards made from it keep their content.
page.template.switchbefore, afteryes · policiesA wiki space turns a library template on or off for its new pages (enabled).
page.template.updatebefore, afteryes · policiesA template of a wiki space or of the template library (scope) is renamed, described, grouped, switched on or off for every space, saved in the template editor, given a page's or a whiteboard's content, or reset to the original (reset).
page.updatebefore, afteryes · policiesA wiki page's title or status changes. Publishing also raises page.publish.
page.version.restoreafternoAn older version of a wiki page is published again, as the page's newest version (after page.publish).
wiki.label.deletebefore, afteryesA site admin removes a wiki label from every page.
wiki.label.updatebefore, afteryesA site admin renames a wiki label, or merges it into another label.

7. Blogs

EventPhasesBlockingWhen it happens
blog.followafternoSomeone starts or stops following a wiki space's blog (followers are told about new posts).
blog.feed.createbefore, afteryes · fail closedSomeone makes a personal feed address for the wiki's blogs (the old one stops). A policy can refuse it.
blog.feed.deleteafternoA personal feed address for the wiki's blogs is stopped: by its owner, or by signing out of their other sessions.
blog.post.featurebefore, afteryes · policiesA space admin pins a post to the top of the space's blog, or unpins it.
blog.post.publishbefore, afteryes · policiesA blog post is published for the first time (later publishes are page.publish only). After it, the blog's followers are told unless its authors turned that off.
blog.post.updatebefore, afteryes · policiesA blog post's summary, cover, co-authors, comment setting or whether followers are told changes. Its title and content are page events (page.update, page.publish with kind blog).
blog.settings.updatebefore, afteryes · policiesA wiki space's blog settings change: the blog is turned on or off, who may write posts, whether new posts take comments, whether posts show on the company Blogs page, review before publishing, the public feed.

8. Whiteboards

EventPhasesBlockingWhen it happens
board.resetbefore, afteryes · policiesAn editor resets a wiki whiteboard that stopped taking changes (over its item or image limit, or unreadable) to one of its versions: changes after that version are dropped, and everyone drawing on it reloads it.
board.updateafternoPeople changed a wiki whiteboard and stopped for two minutes: one event per session of changes, with who changed it and how many items it holds. The board's watchers are told.
board.version.createbefore, afteryes · policiesSomeone names a version of a wiki whiteboard: the board as it is now, or one of its automatic versions (renaming one too). Named versions are kept.
board.version.deletebefore, afteryes · policiesSomeone deletes a named version of a wiki whiteboard.
board.version.restorebefore, afteryes · policiesSomeone restores a version of a wiki whiteboard: the board is first kept as an automatic version, then the version's items are put back as a new change everyone sees.

9. Calendar

EventPhasesBlockingWhen it happens
calendar.event.createbefore, afteryes · policiesAn event or someone's leave is added to a wiki space's calendar. Policies can refuse it; automation can, for example, copy events to another calendar.
calendar.event.deletebefore, afteryes · policiesAn event or leave is removed from a wiki space's calendar.
calendar.event.updatebefore, afteryes · policiesAn event or leave in a wiki space's calendar is changed: its title, times, repeat or person.
calendar.feed.createbefore, afteryes · policiesSomeone makes a secret address that lets calendar apps read their wiki calendars without signing in (replacing any earlier one). Policies can refuse it.
calendar.feed.deleteafternoSomeone turns off their secret calendar address; calendar apps can't read it any more.

10. Q&A

EventPhasesBlockingWhen it happens
qna.answer.acceptbefore, afteryes · policiesThe asker or a moderator accepts an answer as the one that solved the question, moves the accept to another answer or takes it back.
qna.answer.createbefore, afteryes · policiesA question gets an answer.
qna.answer.deletebefore, afteryes · policiesAn answer is deleted, by its author or a moderator.
qna.answer.updatebefore, afteryes · policiesAn answer is edited, by its author or a moderator.
qna.comment.createbefore, afteryes · policiesSomeone comments on a question or an answer.
qna.comment.deletebefore, afteryes · policiesA comment on a question or an answer is deleted, by its author or a moderator.
qna.comment.updatebefore, afteryes · policiesA comment on a question or an answer is edited, by its author or a moderator.
qna.image.createbefore, afteryes · policiesSomeone uploads an image to show in a question or an answer. Policies can refuse it by type or dimensions.
qna.question.closebefore, afteryes · policiesA moderator closes a question (no new answers), marks it a duplicate of another question (no new answers either) or opens it again.
qna.question.createbefore, afteryes · policiesA question is asked in the wiki's Q&A. Policies can refuse questions; automation can, for example, post new questions to a chat channel.
qna.question.deletebefore, afteryes · policiesA question is deleted with its answers, by the asker (while it has no answers) or a moderator.
qna.question.lockbefore, afteryes · policiesA moderator locks a question's comments (only moderators comment then) or unlocks them.
qna.question.updatebefore, afteryes · policiesA question's title, text or tags are edited, by the asker or a moderator.
qna.settings.updatebefore, afteryes · policiesA moderator changes the organization's Q&A settings, such as allowing public questions (readable by anyone while anonymous access is on). Policies can keep public questions off.
qna.tag.mergebefore, afteryes · policiesA moderator merges a tag into another: its questions and followers move to the other tag and the tag goes.
qna.voteafternoSomeone votes a question or an answer up or down, or takes their vote back. The voter isn't in the event.

11. Wiki settings

EventPhasesBlockingWhen it happens
html_block_settings.updatebefore, afteryesThe HTML blocks setting changes: on or off, who may add blocks, and the sites blocks may reach. Taking a site off stops it in every block.
import_settings.updatebefore, afteryesThe installation's wiki import settings (imports allowed, largest export) change.
robots.updatebefore, afteryesWhat the wiki's robots.txt tells search engines changes (block all, allow public spaces, or custom text).
video_sites.updatebefore, afteryesThe sites wiki pages may embed videos from change (YouTube, Vimeo, other hosts). Embeds from a site taken off stop playing in every page.

12. Platform events

Sign-in, people, settings and the running of the installation. The Wiki shares these with every product built on its platform.

13. Sign-in, tokens and access

EventPhasesBlockingWhen it happens
access.grantbefore, afteryes · policiesA user or group is given a role on a resource, such as a space, or their role there changes.
access.revokebefore, afteryes · policiesA user's or group's role on a resource, such as a space, is removed.
ai_agents.mcp_keys.updatebefore, afteryesThe installation's switch for MCP keys changes. While off, no MCP key works and none can be made; turning it off keeps the keys.
apitoken.createbefore, afteryes · policiesA user creates an API token.
apitoken.org_policy.updatebefore, afteryes · policiesAn admin changes the organization's API token rules (maximum lifetime, count, blocked permissions).
apitoken.revokeafternoAPI tokens are revoked by their owner or an admin.
apitoken.rotatebefore, afteryes · policiesA user replaces an API token's secret.
apitoken.updatebefore, afteryes · policiesA user renames an API token or changes its IP allowlist.
applink.connectbefore, afteryes · policiesA person connects their own account on a linked installation: requests through the link then act as them there.
applink.createbefore, afteryesA link with another installation is created, from this side or accepted from the other one: the two then trust each other's applications.
applink.deletebefore, afteryesA link with another installation is removed, with the application made here for it and people's connections through it.
applink.updatebefore, afteryesA link with another installation becomes active or gets new credentials.
auth.loginbefore, afteryes · policiesA user signs in, with a password or through single sign-on (method).
auth.login.failedafternoA sign-in is refused (wrong credentials, inactive or locked account).
auth.logoutafternoA user signs out.
auth.session.revokeafternoSessions are ended (by the user, an admin or the system).
mcp.key.createbefore, afteryes · policiesA person makes an MCP key: a static key an AI agent without OAuth uses on one plugin's MCP server, acting as that person until it expires.
mcp.key.revokebefore, afteryes · policiesAn MCP key is revoked by its owner or an administrator; it stops working at once on every server.
oauth.client.createbefore, afteryesAn OAuth application is registered: it can then ask people to let it act for them.
oauth.client.deletebefore, afteryesAn OAuth application is removed; every connection to it and its tokens stop working.
oauth.client.updatebefore, afteryesAn OAuth application is changed (scopes, redirect addresses, approval, lifetimes), enabled, disabled or gets a new secret.
oauth.consent.grantbefore, afteryes · policiesA person allows an OAuth application to act for them (or it is pre-approved for them), or allows more scopes.
oauth.consent.revokeafternoA connection to an OAuth application is revoked by the person, an administrator, or because the application was removed.
oauth.federation.createbefore, afteryesAn OAuth application starts trusting tokens from an outside issuer (a CI system) in place of its secret.
oauth.federation.deletebefore, afteryesA workload identity trust rule is removed.
oauth.federation.updatebefore, afteryesA workload identity trust rule changes (issuer, audience, conditions) or is enabled or disabled.
oauth.workload_token.exchangebefore, afteryes · policiesA CI system's identity token is exchanged for an access token acting as an application's service account (workload identity).
service_account.createbefore, afteryes · policiesA service account is created: a non-human user OAuth applications can act as (client credentials).
service_account.deletebefore, afteryes · policiesA service account is deleted; applications acting as it stop working.
service_account.updatebefore, afteryes · policiesA service account is renamed, gets another role, or is disabled or enabled.
sso.enforcement.updatebefore, afteryesRequiring single sign-on is turned on or off, or the super-admin password exception changes.
sso.provider.createbefore, afteryesAn identity provider for single sign-on is added.
sso.provider.deletebefore, afteryesAn identity provider is removed; its users can no longer sign in through it.
sso.provider.updatebefore, afteryesAn identity provider is changed, enabled or disabled.

14. Users, groups and directories

EventPhasesBlockingWhen it happens
avatar.deleteafternoA user removes their avatar.
avatar.updatebefore, afteryes · policiesA user sets their avatar to a preset or an uploaded image.
directory.createbefore, afteryesA directory is added; it starts last in the order.
directory.deletebefore, afteryesAn empty directory is deleted.
directory.reorderafternoDirectories are reordered; when a person has accounts in several, the highest wins.
directory.syncafternoA directory sync finished, failed or was blocked by a safety check.
directory.updatebefore, afteryesA directory is renamed, enabled or disabled. Users in a disabled directory can't sign in.
group.createbefore, afteryes · policiesAn administrator creates a group.
group.deletebefore, afteryes · policiesAn administrator deletes a group. Groups are never deleted by directory sync.
group.member.addbefore, afteryes · policiesAn administrator adds users to a group.
group.member.removebefore, afteryes · policiesAn administrator removes a user added by hand from a group.
group.updatebefore, afteryes · policiesA group is renamed or its description changes.
user.anonymizebefore, afteryes · policiesA disabled user is anonymized (GDPR erasure): personal data is removed everywhere and the account can never sign in again. Subscribers should erase what they hold about user_id.
user.createbefore, afteryes · policiesAn administrator creates a user account.
user.disablebefore, afteryes · policiesA user account is disabled: it can't sign in and its sessions end.
user.enablebefore, afteryes · policiesA disabled user account is enabled again.
user.invitation.acceptafternoAn invited user chooses a password; the account becomes active.
user.password.changeafternoA user changes their own password; their other sessions end.
user.password.recoverafternoA user sets a new password from a password reset email; their sessions end.
user.password.resetbefore, afteryes · policiesAn administrator sets a new password for a user; the user's sessions end.
user.role.changebefore, afteryes · policiesA user's role changes.
user.unlockafternoAn administrator unlocks an account locked after failed sign-ins.
user.updatebefore, afteryes · policiesA user's email or name is changed.

15. Security

EventPhasesBlockingWhen it happens
auth.session_policy.updatebefore, afteryesThe session policy (idle timeout, maximum length, Remember me, sessions per person) changes.
security.captcha.updatebefore, afteryesThe CAPTCHA settings change: provider, keys, or which events ask for a CAPTCHA.

16. Settings

EventPhasesBlockingWhen it happens
banner.createbefore, afteryesAn announcement banner is created.
banner.deletebefore, afteryesAn announcement banner is deleted.
banner.updatebefore, afteryesAn announcement banner's title, text, level, audience, schedule or switch changes.
branding.updatebefore, afteryesThe installation's branding changes: app name, brand colors, logos or favicons.
log_alert_rule.createbefore, afteryesA log alert rule is added.
log_alert_rule.deletebefore, afteryesA log alert rule is removed.
log_alert_rule.updatebefore, afteryesA log alert rule is changed, enabled or disabled.
logging.settings.updatebefore, afteryesThe logging settings change: levels, temporary levels, or the log file.
mail.settings.updatebefore, afteryesThe email settings change (SMTP server or Amazon SES API, sender, Wiki's address).
security.anonymous_access.updatebefore, afteryesAnonymous access is turned on or off: whether people who aren't signed in can read public spaces.
security.rate_limit_override.createbefore, afteryesA rate limit override is added: a different request budget for a role, org, user, API token or AI app.
security.rate_limit_override.deletebefore, afteryesA rate limit override is removed; the scope gets the installation's limits again.
security.rate_limit_override.updatebefore, afteryesA rate limit override's budget, exemption or dry run changes.
security.rate_limits.updatebefore, afteryesThe installation's request rate limits are saved (Settings → Security → Rate limits).
site.help.updatebefore, afteryesThe links in the Help menu (documentation, feedback, bug reports, support) change or are reset to the defaults.
site.settings.updatebefore, afteryesThe Wiki's address (used in email links and single sign-on) changes.
storage.settings.updatebefore, afteryesThe storage settings change: where files are kept, credentials, or upload limits.
system_check.settings.updatebefore, afteryesWho is notified about system check changes, and how, changes.

17. Alerts

EventPhasesBlockingWhen it happens
alert.createbefore, afteryes · policiesAn alert is sent to users (by an admin, a plugin or a platform rule).
alert.incident.resolvedafternoEverything a grouped alert (system health) reported is OK again.
alert.silence.createbefore, afteryesAn administrator mutes notifications (a source, a check, an item or a server), for a while or until removed.
alert.silence.endedafternoA mute ended: removed by an administrator, ran out, or its check is OK again.
alert.silence.updatebefore, afteryesAn administrator changes how long a mute lasts, or its reason.
alert.tuning.updatebefore, afteryesAn administrator changes a check's thresholds or when it notifies (or resets them to the defaults).

18. System health

EventPhasesBlockingWhen it happens
cluster.health.changedafternoThe cluster health status changed (ok, warn, fail) and held for two evaluations.
log.alert.firedafternoA log alert rule matched enough log lines and fired.
system.check.changedafternoA system check found something worse than the previous run, or recovered.
system.check.completedafternoA system check run finished (scheduled or on demand).

19. Scheduled jobs

EventPhasesBlockingWhen it happens
scheduler.job.recoveredafternoA job that was failing ran successfully again.
scheduler.job.runbefore, afteryesA scheduled job runs. Blocking subscribers can skip the run.
scheduler.job.triggerbefore, afteryesAn admin runs a job by hand.
scheduler.job.unhealthyafternoA job failed several times in a row (SCHEDULER_UNHEALTHY_THRESHOLD).
scheduler.job.updatebefore, afteryesAn admin enables or disables a job, or changes its schedule or parameters.

20. Backups

EventPhasesBlockingWhen it happens
backup.createbefore, afteryesA backup of the database and platform files is taken (by a person, an API token or the daily job). The after-event carries the archive's SHA-256.
backup.deletebefore, afteryesA backup is deleted by a person or by the cleanup job after its retention period.
backup.downloadbefore, afteryesA backup archive is downloaded. It holds the whole database, so a policy or plugin may refuse it.
backup.failafternoA backup failed: it couldn't be written, or it failed its integrity check.
backup.restorebefore, afteryesA backup is restored over the whole installation: the database and platform files are replaced (a safety backup is taken first). The after-event says whether it worked or failed and was rolled back.
backup.settings.updatebefore, afteryesThe backup settings change: whether new backups are encrypted, to which public keys, that the passphrase changed (never the passphrase itself), or whether backups count rows for test restores.
backup.target.updatebefore, afteryesThe backup target changes: archives go to the installation's storage or to a storage location of their own (where, and whether its credentials changed; never the credentials).
backup.test_restorebefore, afteryesA backup is test-restored into a scratch database and its row counts compared with the backup's; the after-event says whether it passed.
backup.updatebefore, afteryesA backup is marked to keep permanently (the cleanup job skips it) or no longer, or its note changes.
backup.uploadbefore, afteryesA backup file is brought in from outside to restore from: uploaded in chunks, registered from the import folder, or given to the offline restore command. The after-event is the backup it became, with its SHA-256.
backup.verifyafternoA backup's integrity check finished: the archive read back with its published SHA-256, its signature and entry checksums, and pg_restore reading the dump.

21. Platform

EventPhasesBlockingWhen it happens
ai_agents.settings.updatebefore, afteryesThe installation's settings for AI agents change: whether MCP tools that change something (write tools) may run at all. While off, no plugin setting or AI application can turn them on.
cluster.node.renamebefore, afteryesAn admin changes a cluster node's display name.
license.applyafternoAn admin applies a new license.
plugin.data.deletebefore, afteryesA plugin's stored data (its database schema, key-value keys and, unless it is reset, its secrets) is deleted: when it is uninstalled with its data, restarted with its data reset, or its leftover data is deleted.
plugin.settings.updatebefore, afteryesA plugin's settings are changed on its page: the values of its own settings, its call limits (calls per second, each caller's share, per AI application), and for an MCP plugin whether its write tools are on (read-write) and which tools are switched off.

22. Using events

  • Stop something: write a policy on a blocking event's before phase, for example require a review before page.publish, or refuse space.import.start outside some spaces.
  • Be told or tell another system: write an automation rule on the after phase, for example post every qna.question.create to a chat channel with a webhook.
  • Anything else: a plugin can receive both phases with its own logic.