Przejdź do treści
Biblioteka skilli
Sprzedaż i obsługa klienta · Automatyzacja

broadcasts

/broadcasts

Przygotowuje wysyłkę komunikatów do członków lub segmentu, podgląda odbiorców i pokazuje, kto został pominięty; wysyła po zgodzie.

Licencja
MIT
Ostatnia zmiana repozytorium
09.11.2026

Ocena i bezpieczeństwo

90/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść25 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
5
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
1
Przestarzałość

Brak sygnałów. Repozytorium zmienione 09.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Przygotowuje wysyłkę komunikatów do członków lub segmentu, podgląda odbiorców i pokazuje, kto został pominięty; wysyła po zgodzie.

Oryginalny opis (EN)

This skill should be used when the user asks to send a message, announcement or reminder to members, a segment, a plan's members, pass holders or people whose access is expiring, to preview who a broadcast reaches, to read a broadcast's history or who it missed, or to retry or resend one.

Jak działa

  1. Audiences
  2. Sending
  3. History and retries
  4. Do not
  5. References
Sekcje z nagłówków SKILL.md, w oryginale · 47 linii, 728 słów
Podgląd SKILL.md
---
name: broadcasts
description: "This skill should be used when the user asks to send a message, announcement or reminder to members, a segment, a plan's members, pass holders or people whose access is expiring, to preview who a broadcast reaches, to read a broadcast's history or who it missed, or to retry or resend one."
license: MIT
metadata:
  category: creators
  catalogue: 2026-05-01
---

# Broadcasts

A broadcast is one message sent from the project's bot to a segment of its members, queued and delivered in the background, paced inside the platform's limits. It reaches a member only if they have a chat with the project's currently connected bot; a member who bought on the portal and never opened the bot is neither counted nor attempted. The recipient count is the result of the exact query the send runs, so the people counted and the people messaged are the same set.

Every broadcast reaches real people. The order is always: read the audiences, preview the count, confirm the exact wording and the count with the user, send once.

## Audiences

`list_broadcast_audiences` answers every segment the project accepts with its value, label, meaning, whether it needs a pass window, whether it can be narrowed to a plan, whether it reads the expiring horizon, and a recipient estimate. The segments:

- **Member segments**, on the person's status: all users, customers only, trialing users, leads, churned users.
- **Subscription segments**, on the purchase: expiring soon (within a horizon of 7, 14 or 30 days; an auto-renewing member is never expiring, only one who turned renewal off or holds a plan that does not renew), cancelled but still inside their period, paused subscriptions, trialing without a card, waiting on a connection.
- **Pass segments** (need the Passes capability): all active pass holders, all active pass holders not in queue, active pass holders of one window, active pass holders of one window not in queue. "Active" means the pass can still deliver access; "not in queue" means the holder has not tapped their invite link yet. Every-window and single-window are different sends: a "doors open in an hour" message goes to one window, never to next week's holders.
- **Narrow to a plan** (`plan_id`) composes with a segment: customers of Gold, churned from Gold (a retired plan stays selectable on purpose). Not offered for leads or the pass segments.

## Sending

1. `preview_broadcast_audience` with `audience` and, where the segment needs it, `pass_window_id`, `plan_id` or `expiring_within_days` sizes the send without sending; omit `audience` to list every segment with its count. A zero count means there is nothing to send.
2. Show the user the message text and the count, and wait for a yes. A segment that silently resolves to every member is the one mistake a broadcast cannot take back.
3. `broadcast_message` with the same arguments and `message` (up to 4,096 characters). It answers the broadcast row with its id; delivery continues in the background.

On Telegram the message arrives in each member's chat with the bot. On Discord it is posted once in the announcement channel mentioning the plans' roles, or sent as direct messages, as the installation's settings say. For nudging pass holders about their invite link specifically, `remind_pass_window_queue` and `remind_pass_holder` in `plans-and-passes` carry the link; a broadcast is for anything else.

## History and retries

- `list_broadcasts` pages the project's broadcasts newest first (`filter` `sending`, `completed` or `failed`; `status` for one exact status), each with who sent it and from where, the audience, the tallies and `progress.line`, the sentence the creator reads.
- `get_broadcast` reads one with its failures by kind and the first fifty members it could not reach, each with the connector's reason.
- `retry_broadcast` sends a finished broadcast again to the members it could not reach and nobody else, as a new broadcast under the old one; refused while the parent is still sending, when it missed nobody, or when none of the missed can be reached now. Confirm it like a send.

`broadcast.queued` fires when the send begins (with `recipient_estimate`) and `broadcast.completed` with the tallies; the message body is never in a payload. The creator is told once when it finishes.

## Do not

- Do not send without the preview count in front of the user, and never guess a segment value: read `list_broadcast_audiences`.
- Do not pick the every-window segment for a message about one date.
- Do not repeat a send to the same audience to "make sure"; read the history and retry the missed instead.
- Do not put a member's personal data in a broadcast.

## References

- [references/tools.md](references/tools.md): the six tools with their arguments.
- [references/events.md](references/events.md): `broadcast.queued` and `broadcast.completed`.
- [references/endpoints.md](references/endpoints.md): the REST twins under `/v1/projects/{project}/broadcasts`.
- [references/abilities.md](references/abilities.md): `broadcast:send` and `broadcast:read`.
- Documentation: [Broadcasts](https://docs.subscriby.net/creators/broadcasts).
Pliki w paczce (5)
  • SKILL.md 5 KB
  • references/abilities.md 1 KB
  • references/endpoints.md 17 KB
  • references/events.md 5 KB
  • references/tools.md 8 KB

Wersje

W bazie nie ma innych skilli o nazwie broadcasts.

Migawka bazy z 13.11.2026 · wersja paczki 2ee2e58210a0 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 86resend
    Integruje Resend API z zarządzanym uwierzytelnianiem: wysyła e-maile transakcyjne, zarządza domenami, kontaktami, szablonami i broadcastami.
  • 100resend
    Pomaga w pracy z platformą Resend: wysyłką i odbiorem maili, listami odbiorców i kampaniami.
  • 100report-problem
    Zgłasza błędny wynik narzędzia crm-lifecycle-ops, np. fałszywy alarm lub pominięty problem, by został naprawiony i dodany do testów.
  • 90members
    Zarządza członkami i subskrybentami projektu: sprawdza, kto odszedł, łączy konta, blokuje osoby i przekazuje dostępy.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.