Content events out of the box
create, update, publish, unpublish, discardDraft and delete, one event per locale, sent after the transaction commits.
Socket.IO events for your content, delivered only to the roles and API tokens that may read it. With admin settings, monitoring and live presence built from the Strapi Design System.
npm install @strapi-community/plugin-io// config/plugins.js
module.exports = {
io: { enabled: true, config: { contentTypes: ['api::article.article'] } },
};Give the Public role find on Article, then:
import { io } from 'socket.io-client';
const socket = io('http://localhost:1337');
socket.on('article:publish', ({ data }) => console.log('Published:', data.attributes.title));Settings and Monitoring live under Settings > Socket.IO and follow the layout of Strapi's own settings pages: Save in the header, an unsaved-changes guard, inline validation, confirmation dialogs and RBAC-aware actions, in light and dark mode and five languages.



The homepage gets two widgets through Strapi's Widget API, and the Content Manager edit view shows who else is editing.


Screenshots come from a local test host with synthetic data.
| Client | Joins | Receives |
|---|---|---|
| No token | io-role-public | Types the Public role may find (unless authentication is required) |
| Users & Permissions JWT | io-role-<role type> | Types the user's role may find |
| Content API token | io-token-<id> | Read-only and full-access: all watched types; custom: types it may find |
| Admin (presence panel) | io-admin-<id> | Presence only, never content events |
strapi transfer) keeps working next to Socket.IO (#112).socket.io-client)Made with ❤️ by @ComfortablyCoding and @hrdunn. Updated and made better by @Schero94.