OtherReal-timeUpdated May 2026

Courier

Courier notification orchestration

Courier is the notification orchestration platform — single API to send notifications across email, SMS, push, in-app, Slack, Microsoft Teams, plus a designer UI for building notification templates per channel. Similar shape to Novu (Courier is the longer-running commercial alternative). Tiny Command exposes one action, no triggers (Courier emits delivery events via webhooks configured per-channel; point at a Tiny Command webhook trigger URL): Send Notification (fire a notification for a recipient with optional data payload — Courier handles channel selection per recipient preferences and template per-channel rendering). The connection uses a Courier API key. For workflows that want to abstract notification delivery across multiple channels (without integrating SendGrid + Twilio + FCM separately), Courier is the right pick. Per-channel pricing is on top of Courier's per-recipient subscription.

Connect Courier

0triggers

1action

≈ 2 minto set up

Freetier · no card

Actions

Do anything Courier can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

Action	What it does	Inputs
Send Notification	Fires a Courier notification for a recipient with optional data payload. Courier handles channel selection (email, SMS, push, in-app) per the template config and the recipient's preferences. The single-call abstraction over the multi-channel notification stack.	3 fields	View →

Recipes

Pre-built Courier workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Courier → Slack alerts

AI-triage every Courier event, ping the right channel only when it matters.

Courier → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

Courier → Notion database

Turn Courier into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Courier once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Courier field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Courier integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Courier to Tiny Command?

Open the Tiny Command workflow builder, drop in a Courier node, and click Connect. Authorize Courier once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What Courier triggers does Tiny Command support?

Tiny Command focuses on outbound actions for Courier today. Use Tiny Command's universal Webhook or Schedule trigger to start Courier workflows, then run any Courier action you need.

What Courier actions can I run from a workflow?

1 Courier action are available out of the box, covering other operations like "Send Notification". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Courier integration real-time?

Courier actions execute synchronously inside your workflow. Tiny Command waits for Courier's API to confirm before continuing to the next step, so downstream nodes can rely on the result.

Do I need to write code to use Courier with Tiny Command?

No. Every Courier trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Courier API endpoint directly.

How much does the Courier integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Courier integration itself has no per-app surcharge.