Bandeja, Formularios y Alertas (@vicacha-devs/strapi-plugin-inbox)
Package:
@vicacha-devs/strapi-plugin-inbox· Plugin ID:inbox· Category:Community & Engagement· Version:1.1.4· Routes:25
Constructor de formularios dinámicos, bandeja de atención con seguimiento SLA, suscriptores con doble opt-in y cintillos de alerta global.
pnpm add @vicacha-devs/strapi-plugin-inbox

1. Características Principales y Arquitectura
Sección titulada «1. Características Principales y Arquitectura»- Explorar Entidades Content-Type y Casos de Uso (con Diagramas Interactivos)
- Explorar la Guía de Desarrollo y Admin UI
- Explorar la Referencia Interactiva OpenAPI
2. Entidades Content-Type, Ubicación y Esquemas (strapi.documents)
Sección titulada «2. Entidades Content-Type, Ubicación y Esquemas (strapi.documents)»Registers three Collection Types (plugin::inbox.submission, plugin::inbox.subscriber, and plugin::inbox.alert-banner). Submissions capture dynamic form payloads and service-desk tickets; Subscribers manage double opt-in topic lists; Alert Banners drive time-bounded site-wide urgent tickers.
Dónde Encontrar las Entidades Content-Type en Strapi v5
Sección titulada «Dónde Encontrar las Entidades Content-Type en Strapi v5»- Content Manager:
/admin/content-manager/collection-types/plugin::inbox.submission,plugin::inbox.subscriber, andplugin::inbox.alert-banner(visible: true) - Content-Type Builder:
/admin/plugins/content-type-builderunder Collection Types (Inbox Submission,Inbox Subscriber,Inbox Alert Banner) - Plugin Workspace & Settings:
/admin/plugins/inbox(Service Desk Inbox, Subscribers, Alert Banners) and/admin/settings/inbox - Database Tables:
inbox_submissions,inbox_subscribers, andinbox_alert_banners
plugin::inbox.alert-banner — Inbox Alert Banner
Sección titulada «plugin::inbox.alert-banner — Inbox Alert Banner»Time-bounded multi-language urgent announcement ticker / banner
Kind:
collectionType· DB Table:inbox_alert_banners· Admin Location:/admin/content-manager/collection-types/plugin::inbox.alert-banner· Draft & Publish:No· i18n:No
| Atributo | Tipo en Strapi | Requerido | Restricciones / Relación |
|---|---|---|---|
code |
string |
Yes | — |
title |
string |
Yes | — |
message |
text |
Yes | — |
severity |
enumeration |
Yes | enum: info, warning, urgent, celebration; default: "info" |
ctaLabel |
string |
No | — |
ctaUrl |
string |
No | — |
dismissible |
boolean |
No | default: true |
active |
boolean |
No | default: true |
priority |
integer |
No | default: 10 |
startsAt |
datetime |
No | — |
endsAt |
datetime |
No | — |
translations |
json |
No | default: {} |
plugin::inbox.submission — Inbox Submission
Sección titulada «plugin::inbox.submission — Inbox Submission»Form submission & Service-Desk Casework ticket
Kind:
collectionType· DB Table:inbox_submissions· Admin Location:/admin/content-manager/collection-types/plugin::inbox.submission· Draft & Publish:No· i18n:No
| Atributo | Tipo en Strapi | Requerido | Restricciones / Relación |
|---|---|---|---|
referenceCode |
string |
Yes | — |
formSlug |
string |
Yes | — |
formTitle |
string |
No | — |
category |
enumeration |
No | enum: contact, service_desk, inquiry, application, volunteer, custom; default: "contact" |
status |
enumeration |
Yes | enum: new, read, under_review, scheduled, completed, rejected, archived; default: "new" |
priority |
enumeration |
Yes | enum: low, normal, high, urgent; default: "normal" |
department |
string |
No | default: "general" |
locale |
string |
No | default: "es" |
applicantName |
string |
No | — |
applicantEmail |
email |
No | — |
applicantPhone |
string |
No | — |
data |
json |
Yes | default: {} |
checklistItems |
json |
No | default: [] |
staffNotes |
text |
No | — |
assignedTo |
string |
No | — |
linkedBookingId |
string |
No | — |
linkedCertificateNumber |
string |
No | — |
formBuilderSubmissionId |
integer |
No | — |
ipAddress |
string |
No | private: true |
userAgent |
string |
No | private: true |
submittedAt |
datetime |
Yes | — |
secondaryDate |
json |
No | — |
plugin::inbox.subscriber — Inbox Subscriber
Sección titulada «plugin::inbox.subscriber — Inbox Subscriber»Double Opt-In newsletter and community topic subscriber
Kind:
collectionType· DB Table:inbox_subscribers· Admin Location:/admin/content-manager/collection-types/plugin::inbox.subscriber· Draft & Publish:No· i18n:No
| Atributo | Tipo en Strapi | Requerido | Restricciones / Relación |
|---|---|---|---|
email |
email |
Yes | — |
fullName |
string |
No | — |
phone |
string |
No | — |
locale |
string |
No | default: "es" |
topics |
json |
No | default: ["announcements"] |
status |
enumeration |
Yes | enum: pending, confirmed, unsubscribed; default: "pending" |
confirmToken |
string |
No | private: true |
unsubscribeToken |
string |
Yes | private: true |
confirmedAt |
datetime |
No | — |
unsubscribedAt |
datetime |
No | — |
sourceFormSlug |
string |
No | — |
Integración con el Content Manager de Strapi v5 (/admin/content-manager)
Sección titulada «Integración con el Content Manager de Strapi v5 (/admin/content-manager)»Grupo en la Barra Lateral del Content Manager:
Inbox & Omnichannel Broadcasts
Entidades y Componentes en el Content Manager
Sección titulada «Entidades y Componentes en el Content Manager»plugin::inbox.submission(Inbox Submission —/admin/content-manager/collection-types/plugin::inbox.submission)plugin::inbox.subscriber(Inbox Subscriber —/admin/content-manager/collection-types/plugin::inbox.subscriber)plugin::inbox.alert-banner(Inbox Alert Banner —/admin/content-manager/collection-types/plugin::inbox.alert-banner)

Por Qué Este Plugin Crea e Integra Entidades en el Content Manager
Sección titulada «Por Qué Este Plugin Crea e Integra Entidades en el Content Manager»@vicacha-devs/strapi-plugin-inbox registers all three of its entities (Inbox Submission, Inbox Subscriber, and Inbox Alert Banner) with pluginOptions['content-manager'].visible = true so service-desk coordinators, newsletter managers, and editors can combine the operational triage board in /admin/plugins/inbox with Strapi v5’s native Content Manager:
- Structured Casework & Cross-Entity Linking: In Content Manager,
Inbox Submission(plugin::inbox.submission) exposesreferenceCode,category,status,priority,department,checklistItems,linkedBookingId, andlinkedCertificateNumberwhile keepingipAddressanduserAgentprotected (private: true). - Subscriber Topic & GDPR Compliance Management: Filter
Inbox Subscriber(plugin::inbox.subscriber) bystatus(pending,confirmed,unsubscribed),locale, andtopicswhileconfirmTokenandunsubscribeTokenremain private. - Time-Bounded Urgent Alert Authoring: Author and schedule
Inbox Alert Banner(plugin::inbox.alert-banner) records (severity:info,warning,urgent,celebration,startsAt,endsAt,translations) directly in Content Manager.
Cómo Usarlo en el Content Manager de Strapi (Paso a Paso)
Sección titulada «Cómo Usarlo en el Content Manager de Strapi (Paso a Paso)»- Open in Content Manager: In the left sidebar, navigate to Content Manager -> Collection Types -> Inbox & Omnichannel Broadcasts and select Inbox Submission, Inbox Subscriber, or Inbox Alert Banner.
- Manage Urgent Alert Banners: Open Inbox Alert Banner (
/admin/content-manager/collection-types/plugin::inbox.alert-banner) to create or toggle site-wide announcements (RAMADAN-HILAL-1447,JUMUAH-LIVE-KHUTBAH,WINTER-BLANKET-CAMPAIGN). - Filter & Assign Service-Desk Submissions: Open Inbox Submission (
/admin/content-manager/collection-types/plugin::inbox.submission) to filter tickets bypriority = urgent,department, orstatus = under_review, and updateassignedToandstaffNotes. - Workspace vs. Content Manager: Use Content Manager for bulk filtering, alert banner scheduling, and subscriber list audits; use the Inbox Workspace (
/admin/plugins/inbox) for dynamic form schema design and interactive service-desk SLA triage.
Sincronización entre el Content Manager y el Espacio del Plugin
Sección titulada «Sincronización entre el Content Manager y el Espacio del Plugin»Casos de Uso en el Content Manager y Flujos Editoriales
Sección titulada «Casos de Uso en el Content Manager y Flujos Editoriales»Content Manager Use Case 1 — Scheduling Multilingual Urgent & Celebration Alert Banners
Sección titulada «Content Manager Use Case 1 — Scheduling Multilingual Urgent & Celebration Alert Banners»- Para qué sirve y por qué usarlo: Publish time-bounded header banners for Ramadan Hilal confirmation (
severity: 'celebration'), Friday live khutbah streams (info), or emergency relief appeals (urgent). - Cómo ejecutarlo en el Content Manager: Open
/admin/content-manager/collection-types/plugin::inbox.alert-banner, click + Create new entry, setcode,title,message,severity,startsAt,endsAt, andtranslations, and save.
Content Manager Use Case 2 — Auditing Service-Desk Submissions & Linking Bookings/Certificates
Sección titulada «Content Manager Use Case 2 — Auditing Service-Desk Submissions & Linking Bookings/Certificates»- Para qué sirve y por qué usarlo: Filter high-priority counseling or matrimonial requests in Content Manager and link them to an appointment (
linkedBookingId) or certificate (linkedCertificateNumber). - Cómo ejecutarlo en el Content Manager: Open
/admin/content-manager/collection-types/plugin::inbox.submission, filter bypriority = high, and update the record.
3. Casos de Uso y Flujos de Trabajo
Sección titulada «3. Casos de Uso y Flujos de Trabajo»Use Case 1 — Dynamic Public Form Builder & Service-Desk Casework Triage
Sección titulada «Use Case 1 — Dynamic Public Form Builder & Service-Desk Casework Triage»- What it is for: Render multi-step contact, matrimonial, counseling, or volunteer forms on the frontend and triage submissions with SLA priorities and staff checklists.
- How it works: Fetch form schemas via
GET /api/inbox/forms/{slug}, submit viaPOST /api/inbox/submit(creatingplugin::inbox.submissionwith areferenceCode), and track status viaGET /api/inbox/track/{referenceCode}.

Use Case 2 — Double Opt-In Newsletter & Topic Subscription Management
Sección titulada «Use Case 2 — Double Opt-In Newsletter & Topic Subscription Management»- What it is for: Collect GDPR-compliant newsletter and community topic subscribers with tokenized confirmation and 1-click unsubscribe.
- How it works:
POST /api/inbox/subscribecreates aplugin::inbox.subscriberinpendingstatus;POST /api/inbox/confirmandPOST /api/inbox/unsubscribeverifyconfirmToken/unsubscribeToken(private: true).

Use Case 3 — Time-Bounded Multilingual Site-Wide Alert Banners
Sección titulada «Use Case 3 — Time-Bounded Multilingual Site-Wide Alert Banners»- What it is for: Publish urgent announcements (e.g., Ramadan Hilal sighting, weather closure, live stream alert) in the website header ticker.
- How it works: Create
plugin::inbox.alert-bannerrecords withseverity(info,warning,urgent,celebration),startsAt,endsAt, andtranslations; fetch active banners viaGET /api/inbox/alerts.

4. Endpoints REST API (content-api y admin)
Sección titulada «4. Endpoints REST API (content-api y admin)»| Método | Ruta del Endpoint | Ámbito | Controlador | Autenticación |
|---|---|---|---|---|
GET |
/api/inbox/forms |
content-api |
inboxController.listForms |
Public |
GET |
/api/inbox/forms/{slug} |
content-api |
inboxController.getFormBySlug |
Public |
POST |
/api/inbox/forms/{slug}/submit |
content-api |
inboxController.submitForm |
Public |
POST |
/api/inbox/subscribers |
content-api |
inboxController.subscribe |
Public |
GET |
/api/inbox/subscribers/confirm/{token} |
content-api |
inboxController.confirmSubscription |
Public |
GET |
/api/inbox/subscribers/unsubscribe/{token} |
content-api |
inboxController.unsubscribe |
Public |
GET |
/api/inbox/public/unsubscribe |
content-api |
inboxController.unsubscribe |
Public |
GET |
/api/inbox/alerts |
content-api |
inboxController.getActiveAlerts |
Public |
GET |
/inbox/settings |
admin |
inboxController.getSettings |
Bearer JWT |
PUT |
/inbox/settings |
admin |
inboxController.updateSettings |
Bearer JWT |