Çok Kanallı Yayınlar — Geliştirici Kılavuzu ve Yönetim Arayüzü
1. Kurulum ve Bağımlılıklar
Section titled “1. Kurulum ve Bağımlılıklar”pnpm add @vicacha-devs/strapi-plugin-broadcasts2. Sunucu Yapılandırması (config/plugins.ts)
Section titled “2. Sunucu Yapılandırması (config/plugins.ts)”Strapi v5 projenizin config/plugins.ts dosyasına eklenti yapılandırmasını ekleyin:
export default ({ env }: { env: (key: string, defaultValue?: string) => string }) => ({ "broadcasts": { enabled: true, config: { defaultSenderName: env("BROADCASTS_SENDER_NAME", "Community Hub"), dryRun: false, }, },});
3. Strapi v5 Yönetim Arayüzü (Admin UI) Turu
Section titled “3. Strapi v5 Yönetim Arayüzü (Admin UI) Turu”Etkinleştirildiğinde eklenti, Strapi Design System v2 bileşenlerini kullanarak çalışma alanını ve ayarlarını yönetim paneline kaydeder:

Yerelleştirilmiş Arayüz Etiketleri (Türkçe)
Section titled “Yerelleştirilmiş Arayüz Etiketleri (Türkçe)”| Çeviri Anahtarı | Arayüz Metni |
|---|---|
checkbox.enable_dry_run_sandbox_mode |
Deneme (Dry-Run) Simülasyon Modunu Etkinleştir |
checkbox.enable_email_designer_5_html_template_bridge |
Email Designer 5 HTML Şablon Köprüsünü Etkinleştir |
checkbox.enable_eventhub_auto_broadcast_triggers |
EventHub Otomatik Yayın Tetikleyicilerini Etkinleştir |
checkbox.enable_telegram_transport |
Telegram İletimini Etkinleştir |
checkbox.enable_whatsapp_transport |
WhatsApp İletimini Etkinleştir |
checkbox.segment_confirmed_subscribers_via_inbox_bridge |
Onaylı aboneleri Inbox Köprüsü üzerinden bölümlendir |
common.activate |
Etkinleştir |
common.active |
aktif |
4. İçerik Türü Varlıkları, Konumları ve Şemaları (strapi.documents)
Section titled “4. İçerik Türü Varlıkları, Konumları ve Şemaları (strapi.documents)”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.
Strapi v5 İçinde İçerik Türü Varlıkları Nerede Bulunur?
Section titled “Strapi v5 İçinde İçerik Türü Varlıkları Nerede Bulunur?”- 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
plugin::broadcasts.automation-rule — Broadcast Automation Rule
Section titled “plugin::broadcasts.automation-rule — Broadcast Automation Rule”EventHub-driven automated multi-channel broadcast rule
Kind:
collectionType· DB Table:broadcast_automation_rules· Admin Location:/admin/content-manager/collection-types/plugin::broadcasts.automation-rule· Draft & Publish:No· i18n:No
| Alan (Attribute) | Strapi Türü | Zorunlu | Kısıtlamalar / İlişki |
|---|---|---|---|
name |
string |
Yes | — |
slug |
uid |
Yes | — |
eventName |
string |
Yes | — |
targetContentType |
string |
No | — |
topic |
string |
Yes | default: "announcements" |
channels |
json |
Yes | default: ["telegram"] |
active |
boolean |
No | default: true |
priority |
enumeration |
No | enum: low, normal, high, urgent; default: "normal" |
subjectTemplate |
string |
Yes | — |
bodyTextTemplate |
text |
Yes | — |
bodyHtmlTemplate |
richtext |
No | — |
ctaLabelTemplate |
string |
No | — |
ctaUrlTemplate |
string |
No | — |
translations |
json |
No | default: {} |
lastTriggeredAt |
datetime |
No | — |
triggerCount |
integer |
No | default: 0 |
plugin::broadcasts.campaign — Broadcast Campaign
Section titled “plugin::broadcasts.campaign — Broadcast Campaign”Omnichannel Email, Telegram & WhatsApp broadcast campaign
Kind:
collectionType· DB Table:broadcast_campaigns· Admin Location:/admin/content-manager/collection-types/plugin::broadcasts.campaign· Draft & Publish:No· i18n:No
| Alan (Attribute) | Strapi Türü | Zorunlu | Kısıtlamalar / İlişki |
|---|---|---|---|
title |
string |
Yes | — |
slug |
uid |
Yes | — |
topic |
string |
Yes | default: "announcements" |
channels |
json |
Yes | default: ["email","telegram"] |
priority |
enumeration |
Yes | enum: low, normal, high, urgent; default: "normal" |
status |
enumeration |
Yes | enum: draft, scheduled, sending, sent, failed, cancelled; default: "draft" |
scheduledAt |
datetime |
No | — |
sentAt |
datetime |
No | — |
subject |
string |
Yes | — |
bodyText |
text |
Yes | — |
bodyHtml |
richtext |
No | — |
ctaLabel |
string |
No | — |
ctaUrl |
string |
No | — |
mediaUrl |
string |
No | — |
emailTemplateRef |
string |
No | — |
whatsappTemplateName |
string |
No | — |
whatsappGroupIds |
json |
No | default: [] |
telegramChatId |
string |
No | — |
telegramThreadId |
integer |
No | — |
translations |
json |
No | default: {} |
secondaryDate |
json |
No | default: {} |
secondaryDateLabel |
string |
No | — |
stats |
json |
No | default: {} |
metadata |
json |
No | default: {} |
plugin::broadcasts.delivery-log — Broadcast Delivery Log
Section titled “plugin::broadcasts.delivery-log — Broadcast Delivery Log”Idempotent, PII-masked multi-channel delivery audit log
Kind:
collectionType· DB Table:broadcast_delivery_logs· Admin Location:/admin/content-manager/collection-types/plugin::broadcasts.delivery-log· Draft & Publish:No· i18n:No
| Alan (Attribute) | Strapi Türü | Zorunlu | Kısıtlamalar / İlişki |
|---|---|---|---|
idempotencyKey |
string |
Yes | — |
campaignSlug |
string |
Yes | — |
channel |
enumeration |
Yes | enum: email, telegram, whatsapp |
driver |
string |
Yes | — |
recipientMasked |
string |
Yes | — |
locale |
string |
Yes | default: "es" |
status |
enumeration |
Yes | enum: sent, simulated, skipped_duplicate, failed |
externalMessageId |
string |
No | — |
errorMessage |
text |
No | — |
sentAt |
datetime |
Yes | — |
secondaryDateLabel |
string |
No | — |
Strapi v5 İçerik Yöneticisi (Content Manager) Entegrasyonu (/admin/content-manager)
Section titled “Strapi v5 İçerik Yöneticisi (Content Manager) Entegrasyonu (/admin/content-manager)”İçerik Yöneticisi Kenar Çubuğu Grubu:
Inbox & Omnichannel Broadcasts
İçerik Yöneticisi Varlıkları ve Bileşenleri
Section titled “İçerik Yöneticisi Varlıkları ve Bileşenleri”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)

Bu Eklenti Neden Content Manager Varlıkları Oluşturur?
Section titled “Bu Eklenti Neden Content Manager Varlıkları Oluşturur?”@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.
Strapi Content Manager İçinde Nasıl Kullanılır? (Adım Adım)
Section titled “Strapi Content Manager İçinde Nasıl Kullanılır? (Adım Adım)”- 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 ve Eklenti Çalışma Alanı Senkronizasyonu
Section titled “Content Manager ve Eklenti Çalışma Alanı Senkronizasyonu”Content Manager Kullanım Senaryoları ve Editöryal İş Akışları
Section titled “Content Manager Kullanım Senaryoları ve Editöryal İş Akışları”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”- Amacı ve Neden Kullanıldığı: Allow editors to prepare multilingual campaign copy and WhatsApp template variables in Content Manager while a reviewer leaves approval notes before sending.
- Content Manager İçinde Uygulama Adımları: 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”- Amacı ve Neden Kullanıldığı: Investigate delivery failures or idempotent duplicate skips across Email, Telegram, and WhatsApp without exposing raw subscriber PII.
- Content Manager İçinde Uygulama Adımları: Open
/admin/content-manager/collection-types/plugin::broadcasts.delivery-logand filter bystatus = failedorchannel = whatsappto inspecterrorMessageandrecipientMasked.
5. Uçtan Uca Kullanım Senaryoları ve İş Akışları
Section titled “5. Uçtan Uca Kullanım Senaryoları ve İş Akışları”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).

6. REST API Uç Noktaları (content-api ve admin)
Section titled “6. REST API Uç Noktaları (content-api ve admin)”| Metot | Uç Nokta Yolu | Kapsam | Denetleyici (Handler) | Kimlik Doğrulama |
|---|---|---|---|---|
GET |
/api/broadcasts/public/channels |
content-api |
broadcastController.listPublicChannels |
Public |
GET |
/api/broadcasts/public/archive |
content-api |
broadcastController.listPublicArchive |
Public |
GET |
/broadcasts/settings |
admin |
broadcastController.getSettings |
Bearer JWT |
PUT |
/broadcasts/settings |
admin |
broadcastController.updateSettings |
Bearer JWT |
GET |
/broadcasts/templates |
admin |
broadcastController.listStarterTemplates |
Bearer JWT |
GET |
/broadcasts/email-templates |
admin |
broadcastController.listEmailTemplates |
Bearer JWT |
GET |
/broadcasts/campaigns |
admin |
broadcastController.listCampaigns |
Bearer JWT |
POST |
/broadcasts/campaigns |
admin |
broadcastController.createCampaign |
Bearer JWT |
PUT |
/broadcasts/campaigns/{documentId} |
admin |
broadcastController.updateCampaign |
Bearer JWT |
POST |
/broadcasts/campaigns/from-template |
admin |
broadcastController.createFromTemplate |
Bearer JWT |
POST |
/broadcasts/campaigns/{documentId}/send |
admin |
broadcastController.sendCampaign |
Bearer JWT |
GET |
/broadcasts/automation-rules |
admin |
broadcastController.listAutomationRules |
Bearer JWT |
POST |
/broadcasts/automation-rules |
admin |
broadcastController.createAutomationRule |
Bearer JWT |
PUT |
/broadcasts/automation-rules/{documentId} |
admin |
broadcastController.updateAutomationRule |
Bearer JWT |
GET |
/broadcasts/delivery-logs |
admin |
broadcastController.listDeliveryLogs |
Bearer JWT |
7. Sunucu Tarafı Programatik Kullanım (strapi.plugin ve strapi.documents)
Section titled “7. Sunucu Tarafı Programatik Kullanım (strapi.plugin ve strapi.documents)”// Registered services on plugin "broadcasts": "settings", "transportService", "campaignService", "automationService"const pluginService = strapi.plugin("broadcasts")?.service("transportService");
// Querying records via the Strapi v5 Document Service APIconst records = await strapi.documents("plugin::broadcasts.automation-rule").findMany({ limit: 25, sort: "createdAt:desc",});8. Sorun Giderme ve Doğrulama
Section titled “8. Sorun Giderme ve Doğrulama”- Yönetim paneli değişiklikleri görünmüyor:
config/plugins.tsdosyasını güncelledikten sonrapnpm strapi buildkomutunu çalıştırın. - Strapi bağımlılık izolasyonu: React bağlam çakışmalarını önlemek için
pnpm-workspace.yamliçindehoistPattern: ["*", "!@strapi/*"]ayarını koruyun. - Sıkı TypeScript kontrolü: Hem
adminhem deserverpaketlerini doğrulamak içinpnpm checkkomutunu çalıştırın.