tiny-send/send@v1 emails your audience from any workflow. GitHub notifications reach people who watch your repo; this reaches your subscribers — with deliverability, archives, and unsubscribe handled.

on:
  release:
    types: [published]

jobs:
  notify:
    runs-on: ubuntu-latest
    steps:
      - uses: tiny-send/send@v1
        with:
          api-key: ${{ secrets.TINYSEND_API_KEY }}
          list: ${{ vars.TINYSEND_LIST }}
          subject: ${{ github.event.release.name }}
          body: ${{ github.event.release.body }}

Inputs

api-key (required): your API key, stored as a repo secret
list (required): newsletter id to send to
subject (required): email subject
body: message content, markdown by default
body-file: read content from a file instead (CHANGELOG.md, release notes)
format: markdown (default), html, or text
draft: true creates the post without sending, so you can review first
channel: email today; sms and whatsapp are coming — same action, no rewrite

Outputs: post-id, status, recipients.

What people build with it

release notes emailed to subscribers when you publish a release
issues as a newsletter: label an issue announcement and it’s sent — the issue tracker becomes your editor
incident updates: open an issue labeled incident → “investigating” email; close it → resolution email
deploy notes on successful production deploys
weekly digests on a cron schedule
a universal email webhook via repository_dispatch — any system can trigger a send, no server needed

Full recipes with copy-paste workflows: github.com/tiny-send/send.

Pair it with a subscriber badge in your README — https://{your-list}.tinysend.com/subscribers.svg — the badge recruits subscribers, the action keeps them posted.

Questions?

Contact us at hi@tinysend.com.

GitHub action — tinysend developers

Inputs

What people build with it

Questions?