Omnichannel Broadcasts (@vicacha-devs/strapi-plugin-broadcasts)
Omnichannel Community Broadcasts & EventHub Automation Engine for Strapi v5:
- Multi-Channel Transports:
- Email Newsletters: Dispatches via
strapi.plugin('email')(and optionalstrapi-plugin-email-designer-5templates) withList-Unsubscribeheaders and per-subscriber{{unsubscribeUrl}}. - Telegram Bot & Channel/Supergroup Broadcasts: Dispatches rich HTML messages with inline CTA buttons (
InlineKeyboardMarkup) and optional Forum topic thread (message_thread_id) routing. - WhatsApp Broadcasts: Supports Meta WhatsApp Cloud API (
meta-cloud— WABA templates & text) and self-hosted gateways (rmyndharis/OpenWAviaPOST /api/sessions/{sessionId}/messages/send-textwithX-API-Key+Authorization: Bearer, WAHA, and Evolution API) with E.164 phone normalization and HTTPS SSRF guards. - Dry-Run Sandbox Mode: Automatically records simulated deliveries when
dryRun: trueor when external provider tokens are not configured.
- Email Newsletters: Dispatches via
- Ecosystem Bridges:
@vicacha-devs/strapi-plugin-inboxBridge: Segments confirmed double opt-in subscribers (plugin::inbox.subscriber) bytopicandlocale, selecting each subscriber’s localized campaign copy (es,en,ar,tr, etc.).@vicacha-devs/strapi-plugin-calendarBridge: Computes Hijri (islamic-umalqura) or other secondary calendar dates on every campaign (secondaryDateLabel).
- EventHub Automation Rules:
- Trigger automatic Telegram/WhatsApp/Email broadcasts when Strapi
eventHubevents fire (e.g.,inbox.alert.published,api::event.eventpublished,plugin::media-feeds.episodesynced).
- Trigger automatic Telegram/WhatsApp/Email broadcasts when Strapi
- Idempotent & PII-Masked Delivery Ledger:
- Deduplicates dispatches via deterministic SHA-256
idempotencyKeyand masks recipient emails/phones (j***@example.com,+57***4567) inplugin::broadcasts.delivery-log.
- Deduplicates dispatches via deterministic SHA-256
Quick Installation & Configuration
Section titled “Quick Installation & Configuration”pnpm add @vicacha-devs/strapi-plugin-broadcastsEnable the plugin in config/plugins.ts:
export default () => ({ "broadcasts": { enabled: true, },});Content-Type Entities & Where to Find Them
Section titled “Content-Type Entities & Where to Find Them”Registers three Collection Types (plugin::broadcasts.campaign, plugin::broadcasts.automation-rule, plugin::broadcasts.delivery-log). Campaigns store multi-channel message payloads; Automation Rules subscribe to Strapi eventHub events (e.g., entry.publish); Delivery Logs store idempotent (idempotencyKey), PII-masked (recipientMasked) audit trails. Supports schemaExtensions in config/plugins.ts.
- Content Manager:
/admin/content-manager/collection-types/plugin::broadcasts.campaign,plugin::broadcasts.automation-rule, andplugin::broadcasts.delivery-log(visible: true) - Content-Type Builder:
/admin/plugins/content-type-builderunder Collection Types - Plugin Workspace & Settings:
/admin/plugins/broadcasts(Campaigns, Automation Rules, Delivery Audit) and/admin/settings/broadcasts - Database Tables:
broadcast_campaigns,broadcast_automation_rules, andbroadcast_delivery_logs
Strapi v5 Content Manager Integration (/admin/content-manager)
Section titled “Strapi v5 Content Manager Integration (/admin/content-manager)”Content Manager Sidebar Group:
Inbox & Omnichannel Broadcasts
Content Manager Entities & Components
Section titled “Content Manager Entities & Components”plugin::broadcasts.campaign(Broadcast Campaign —/admin/content-manager/collection-types/plugin::broadcasts.campaign)plugin::broadcasts.automation-rule(Broadcast Automation Rule —/admin/content-manager/collection-types/plugin::broadcasts.automation-rule)plugin::broadcasts.delivery-log(Broadcast Delivery Log —/admin/content-manager/collection-types/plugin::broadcasts.delivery-log)

Why This Plugin Creates & Integrates Content Manager Entities
Section titled “Why This Plugin Creates & Integrates Content Manager Entities”@vicacha-devs/strapi-plugin-broadcasts exposes all three of its entities (Broadcast Campaign, Broadcast Automation Rule, and Broadcast Delivery Log) in the Strapi v5 Content Manager so communication teams can author rich campaign payloads, audit PII-masked delivery logs, and govern access via native RBAC:
- Structured Campaign Authoring & Review: Draft
bodyHtml,bodyText,telegramParseMode,whatsappTemplateName, andctaUrlin Content Manager with collaborative@vicacha-devs/strapi-plugin-notesannotations before dispatching from/admin/plugins/broadcasts. - Declarative EventHub Rule Management: Inspect and bulk-toggle
Broadcast Automation Rule(plugin::broadcasts.automation-rule) triggers (entry.publish,entry.create) and Mustache templates ({{title}},{{slug}}) in Content Manager. - Compliance & Delivery Log Auditing: Filter
Broadcast Delivery Log(plugin::broadcasts.delivery-log) bychannel,status(sent,failed,skipped_duplicate),idempotencyKey, andrecipientMaskedusing Content Manager’s native search and pagination. - Role-Based Access Separation: Grant copywriters Content Manager permission to draft
plugin::broadcasts.campaignrecords while restricting actual live dispatch (POST /broadcasts/campaigns/{id}/send) to senior administrators.
How to Use in Strapi Content Manager (Step-by-Step)
Section titled “How to Use in Strapi Content Manager (Step-by-Step)”- Open in Content Manager: Navigate to Content Manager -> Collection Types -> Inbox & Omnichannel Broadcasts and select Broadcast Campaign, Broadcast Automation Rule, or Broadcast Delivery Log.
- Author & Schedule Campaigns: In Broadcast Campaign (
/admin/content-manager/collection-types/plugin::broadcasts.campaign), create an entry withtitle,slug,topic,targetLocale,channels(['email', 'telegram', 'whatsapp']), and channel-specific templates. - Configure EventHub Automation Rules: In Broadcast Automation Rule (
/admin/content-manager/collection-types/plugin::broadcasts.automation-rule), bindeventName(entry.publish) andtargetContentType(e.g.,plugin::events.eventorplugin::islam.hilal-announcement). - Workspace vs. Content Manager: Use Content Manager to draft campaign copy, attach review notes, and query
Broadcast Delivery Loghistory; use the Broadcasts Workspace (/admin/plugins/broadcasts) to execute dry-run previews and trigger live omnichannel sends.
Content Manager & Plugin Workspace Synchronization
Section titled “Content Manager & Plugin Workspace Synchronization”Content Manager Use Cases & Editorial Workflows
Section titled “Content Manager Use Cases & Editorial Workflows”Content Manager Use Case 1 — Two-Stage Editorial Approval Before Omnichannel Dispatch
Section titled “Content Manager Use Case 1 — Two-Stage Editorial Approval Before Omnichannel Dispatch”- Why & What it is for: Allow editors to prepare multilingual campaign copy and WhatsApp template variables in Content Manager while a reviewer leaves approval notes before sending.
- How to use in Content Manager: Create a
Broadcast Campaignwithstatus: 'draft'in/admin/content-manager/collection-types/plugin::broadcasts.campaign, review it via the Content Manager Notes panel, and dispatch it from/admin/plugins/broadcasts.
Content Manager Use Case 2 — Filtering Failed or Skipped Delivery Logs by Channel & Campaign
Section titled “Content Manager Use Case 2 — Filtering Failed or Skipped Delivery Logs by Channel & Campaign”- Why & What it is for: Investigate delivery failures or idempotent duplicate skips across Email, Telegram, and WhatsApp without exposing raw subscriber PII.
- How to use in Content Manager: Open
/admin/content-manager/collection-types/plugin::broadcasts.delivery-logand filter bystatus = failedorchannel = whatsappto inspecterrorMessageandrecipientMasked.
End-to-End Use Cases & Workflows
Section titled “End-to-End Use Cases & Workflows”Use Case 1 — Omnichannel Manual & Scheduled Community Campaigns
Section titled “Use Case 1 — Omnichannel Manual & Scheduled Community Campaigns”- What it is for: Dispatch announcements simultaneously across Email (SMTP/Resend), Telegram Bot channels/threads, and WhatsApp Cloud API.
- How it works: Create a
plugin::broadcasts.campaignentity withchannels: ['email', 'telegram', 'whatsapp'], preview viaPOST /broadcasts/campaigns/{id}/dry-run, and dispatch viaPOST /broadcasts/campaigns/{id}/send.

Use Case 2 — EventHub Zero-Touch Publish Automation
Section titled “Use Case 2 — EventHub Zero-Touch Publish Automation”- What it is for: Automatically broadcast a Telegram/WhatsApp notification whenever an editor publishes a new Event, Hilal Announcement, or Urgent Campaign.
- How it works: Create a
plugin::broadcasts.automation-ruleentity matchingeventName: 'entry.publish'andtargetContentType: 'plugin::events.event'with Mustache-stylesubjectTemplateandbodyTextTemplate.

Use Case 3 — Idempotent PII-Masked Delivery Auditing
Section titled “Use Case 3 — Idempotent PII-Masked Delivery Auditing”- What it is for: Guarantee no subscriber receives duplicate messages on retry while keeping phone numbers and emails masked in database logs.
- How it works: Every dispatch computes a deterministic
idempotencyKeyrecorded inplugin::broadcasts.delivery-logwithrecipientMasked(j***@example.org,+57***4821).

Admin Workspace, Content Manager & Settings Panel Preview
Section titled “Admin Workspace, Content Manager & Settings Panel Preview”
Strapi v5 Content Manager Entities (/admin/content-manager)
Section titled “Strapi v5 Content Manager Entities (/admin/content-manager)”
Settings Panel (Settings -> Configuration)
Section titled “Settings Panel (Settings -> Configuration)”
Explore Content Types & Use Cases, the Developer Guide & Admin UI Tour, and the Interactive OpenAPI Reference for complete schema, workflow diagram, and endpoint documentation.