Resources · n8n integration

Gotify n8n integrationAutomate Gotify with n8n.

Can a workflow push an alert straight to a notification server you own? The Gotify n8n integration exposes one resource, Message, with 3 operations: create, delete and get many. No trigger node comes with it, so a Schedule Trigger or a Webhook starts the run. Built for self-hosted setups.

Try the Gotify integration on n8nSee the 3 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

Why set up the Gotify n8n integration?

Gotify is a push notification server you install on your own machine, and its clients display whatever lands on its API. The n8n node n8n-nodes-base.gotify talks to that API from inside a workflow. It carries a single Message resource with 3 operations, so one run can send a notification, read the message history back, and delete an entry that no longer matters.

Start with the morning recap. A Schedule Trigger wakes the workflow, a Google Sheets node reads yesterday's rows, and message.create posts a short summary with a Title and a Priority. One of the two published templates works exactly that way: it fetches a weather update and sends it as a message every day.

Then there is alert routing that never leaves your servers. A workflow already watching Gmail for failed deliveries, or a Slack channel for incidents, can end on Gotify instead of a hosted chat. Teams that already notify through Pushover or Telegram often keep both for a few weeks and compare what actually gets read.

The third pattern is housekeeping. message.getAll brings back what the server still holds, a filter isolates the entries older than the retention you picked, and message.delete removes them one at a time. The other published template syncs liked songs from Spotify and reports the result through Gotify, same shape: a scheduled run that ends on a notification.

What the node does not do, HTTP Request does. Those 3 operations stop at the Message resource, so any other Gotify endpoint goes through the HTTP Request node, which reuses the same credential, that is the connection details you store once in n8n.

Two limits are worth knowing before you build. There is no Gotify trigger node, so nothing starts on its own when a message reaches the server. And on Get Many, with Return All off, n8n stops at the number set in Limit. If n8n itself is new to you, the n8n training covers the trigger and credential basics this page assumes.

Connect

How do you connect Gotify to n8n?

  1. 01

    Install Gotify and copy its URL

    Gotify runs on your own server, so the first move happens outside n8n: install it, then keep the address of the host at hand. The credential asks for the URL of the Gotify host, and every operation in the workflow is sent to that address. n8n has to be able to reach it, which is the part people forget when the server sits behind a private network.

  2. 02

    Generate the two API tokens

    Gotify issues two kinds of token and the node uses them for different jobs. An App API Token comes from an application you create in the Apps menu, and it is the one that lets a workflow create messages. A Client API Token comes from a client you create in the Clients menu, and it covers every other action, deleting and retrieving messages included.

  3. 03

    Store the credential in n8n

    In n8n, open the Credentials menu and create a Gotify credential with the host URL and the token. Save it, and the Gotify node offers it in its dropdown. A credential is set up once and reused by every workflow after that, so the second notification flow you build needs no new configuration at all.

Actions

What can the Gotify node do?

The Gotify node exposes 3 operations across 1 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceCreateGet ManyDelete
Message✓✓✓

Message

3 operations
01

Create a message

message.create

What you see in n8n

Notes & use cases

Posts a notification to the Gotify server, where the connected clients display it.

Key parameters

  • Message: the body of the notification, often {{ $json.text }} coming from the previous node. Writing it in markdown means setting the Content Type option as well.
  • Title: the line shown above the body, in Additional Fields.
  • Priority: the priority of the message, also in Additional Fields, 1 by default.
  • Content Type: text/plain renders the message as plain text, text/markdown renders it as markdown.
Use cases
a nightly import ends with a one line recap, and the Options collection adds a Click URL so tapping the notification opens the page that matters.
02

Delete a message

message.delete

What you see in n8n

Notes & use cases

Removes a single message from the server, identified by its id.

Key parameters

  • Message ID: the id of the message to remove, usually {{ $json.id }} picked up from a Get Many step placed earlier in the same run.
Use cases
an incident flow clears the alert it raised once the service answers again, so nobody keeps staring at a warning that no longer applies. Chained after Get Many and a filter, it also trims a history that grew past what you wanted to keep.
03

Get many messages

message.getAll

What you see in n8n

Notes & use cases

Reads the messages stored on the server and hands them to the workflow, one item per message.

Key parameters

  • Return All: switched on, n8n walks the pages of the API until the whole history is back.
  • Limit: with Return All off, it caps how many messages the node returns.
Use cases
a weekly cleanup lists everything, filters on age, then feeds Delete. Return All off with a small Limit is also the quick way to check what the last runs really sent.
Need help

Need help automating Gotify with n8n?

A person reads every message.

FAQ

Gotify and n8n, common questions

01Is the Gotify n8n integration free?
Yes on the n8n side. The Gotify node ships with n8n, so there is nothing to install and nothing extra to pay, whether the workflow runs on n8n Cloud, the hosted offer from n8n, or on an instance you host yourself under the Community Edition and its Sustainable Use licence. Gotify itself is software you install on your own server, so what it costs you is hosting, not a subscription. A workflow behaves identically in both setups, which means a flow built on Cloud moves to your own instance without being rewritten.
02Which credentials does the Gotify node need?
An API token, and which one depends on the operation. Creating messages needs an App API Token, generated by creating an application in the Apps menu of Gotify. Deleting or retrieving messages needs a Client API Token, generated by creating a client in the Clients menu. Both go into a Gotify credential in n8n alongside the URL of the host. Store that credential once and every workflow picks it from the node dropdown, so a token never has to be pasted into a node again.
03What are the limits of the Gotify node in n8n?
It covers one resource and 3 operations: create, delete and get many messages. Anything else on the Gotify API has no dedicated field in the node, so it goes through the HTTP Request node, which reaches any endpoint of the API while reusing the same credential through predefined authentication. On Get Many, leaving Return All off means the node stops at the number set in Limit, which matters when you scan a long history before a cleanup. The absence of a trigger is the other limit, covered next.
04Can n8n react to a new Gotify message automatically?
Not on its own. Gotify has no trigger node in n8n, so no workflow starts because a message reached the server. Two ways around it. A Schedule Trigger runs Get Many on a fixed interval and compares what comes back with what was already handled, which is polling, that is asking the server regularly rather than being told. Or the service that produced the event calls an n8n Webhook, a URL that n8n exposes for an outside system to call, and that workflow ends with a Gotify message.
05n8n or Make for Gotify?
Both send the notification. The difference sits elsewhere. n8n runs on your own infrastructure or on n8n Cloud, which fits naturally next to a Gotify server you already host, since the data stays on machines you control. Make is hosted only, with no self-hosting option, and bills per operation, so a workflow that loops over a long message history costs more as the history grows. Make's visual editor is easier to hand over to a colleague who never builds automations. Decide on hosting and cost model first.
Same platform

Other docs you might need on this stack.

Browse all integrations