CommunicationReal-timeUpdated June 2026

Gotify integration

Gotify self-hosted push notification server

Gotify is the lightweight self-hosted push-notification server — a single Go binary that runs anywhere, exposes a REST API for sending messages, and has Android/web clients that subscribe and notify on incoming messages. Used by homelab operators, DIY monitoring setups, and small teams who want a self-hosted Pushover alternative. Tiny Command exposes four actions, no triggers (Gotify's WebSocket stream is the real-time delivery path to clients; HTTP webhooks for sending events out of Gotify are minimal): Create Message (post a notification with title, body, priority, optional extra-key extras for client-specific behaviour), Delete Message (remove a previously sent message — useful for "the alert is no longer active, clear it" patterns), List Messages (recent messages, paginated), List Applications (each Gotify application is a sender identity with its own token; useful for routing notifications to different client groupings). The connection takes the Gotify server URL plus the application token (one per Gotify application — generate in the admin UI under Apps).

Connect Gotify

No credit card required · Set up in under 2 minutes

0triggers

4actions

≈ 2 minto set up

Freetier · no card

Actions

Do anything Gotify 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	Open action
Send Gotify Notification	Pushes a notification to a Gotify application with title, body, priority. The standard "send me a push" hook for self-hosted homelab alerting workflows.	1 input	View
Delete Gotify Message	Removes a previously-sent message from the server. For "alert resolved → clear from server" workflows. Clients that already received the message keep it locally until manually dismissed.	1 input	View
List Gotify Applications	Returns every Gotify application (sender identity) on the server. Useful for resolving app tokens and for inventorying notification senders.	1 input	View
List Gotify Messages	Returns recent messages on the server. Useful for "audit what notifications were sent today" workflows or for searching message history.	2 inputs	View

Recipes

Pre-built Gotify workflows.

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

Gotify → Slack alerts

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

Gotify → Google Sheets log

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

Gotify → Notion database

Turn Gotify 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 Gotify 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 Gotify 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 Gotify integration.

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

How do I connect Gotify to Tiny Command?

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

What Gotify triggers does Tiny Command support?

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

What Gotify actions can I run from a workflow?

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

Is the Gotify integration real-time?

Gotify actions execute synchronously inside your workflow. Tiny Command waits for Gotify'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 Gotify with Tiny Command?

No. Every Gotify 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 Gotify API endpoint directly.

How much does the Gotify 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 Gotify integration itself has no per-app surcharge.