Actionist·Gotify
Gotify

Gotify

· #128 most-used

Your self-hosted push notifications, fully automated

CommunicationDeveloperAutomationSecurityProductivity

Gotify is a free, open-source, self-hosted server that routes push notifications to any device or service you control — with zero dependency on third-party cloud infrastructure. Connect it to Actionist and your agents can send priority-tiered alerts the moment a deployment completes, an error threshold is breached, a budget is exceeded, or any other event demands immediate attention. Every notification stays on your infrastructure; no data ever touches an external push service.

Try Gotify with ActionistVisit Gotify
Average time saved
10 hours
per person · per month
≈ 1 workdays back

Eliminates manual work. Eliminates manual monitoring, copy-pasting alert text, and switching between dashboards to page the right people when something goes wrong.

Schedule

What your Gotify agent runs on autopilot

A week of scheduled jobs your Actionist agent will execute on your behalf.

28Scheduled jobs
7Agents at work
24/7Always on
Agents
Tue–Thu
Tue
Wed
Thu
7a
8a
9a
10a
11a
12p
1p
2p
3p
4p
5p
6p
Multi-app workflows

Gotify × every other app you use

End-to-end automations that span multiple apps — each one a real business outcome.

6Workflows
9Apps spanned
~13 hrsSaved / week
6Personas served
For customer success
Featured4 apps

Critical alert to Slack and calendar in 30s

When a support ticket email hits your inbox flagged as a production outage, your agent scans the Gotify server for any in-flight high-priority messages about the same system — then fires a new Gotify priority-9 push to every on-call device, simultaneously posts the incident summary to #incidents in Slack, and creates a war-room calendar event for the next 30 minutes. The on-call engineer is paged, the channel is informed, and the call is booked before the support email is even opened.

~2 hrs / week

Time saved for your team — every week, on autopilot

The flow
Trigger·When a priority-8 or above email arrives in Gmail about a production incident
trigger
Step 1
Gmail
Detect incoming incident email
read
Step 2
Gotify
Get all messages — scan active alerts
write
Step 3
Gotify
Create message — push priority-9 alert to on-call
write
Step 4
Slack
Post incident summary to #incidents
write
Step 5
Google Calendar
Create war-room event for next 30 min
Result
Create message — push priority-9 alert to on-callPost incident summary to #incidentsCreate war-room event for next 30 min
The win
Saved per run
15 min
Runs / week
~8×
On-call paged in under 30 seconds
Driven byCustomer Support Agent
ROI

Savings

What your team gets back — two angles: what you stop doing manually, and what that's worth.

Without Actionist

What you do manually today

With Actionist

What your agent runs for you

  • Sales
    18 min / week
    Manual deal-win broadcast

    Sales rep sends individual Slack messages or emails to announce closed deals — takes 5–10 minutes per win.

    Sales Agent
    0 min
    Agent pushes instant deal-won alert

    Gotify message fires to every sales device the moment the CRM updates — team celebrates in under 10 seconds.

  • Marketing
    13 min / week
    Campaign launch check-in

    Marketing manager manually notifies the team via Slack or email that a campaign is live — often delayed by timezone gaps.

    Marketing Agent
    0 min
    Agent pushes campaign-live notification

    Gotify fires a named campaign alert with segment count to all marketing devices the instant HubSpot activates the send.

  • Customer Support
    18 min / week
    Incident triage notification

    Support lead manually alerts on-call engineers via Slack or phone when a customer-impacting incident is detected.

    Customer Support Agent
    0 min
    Agent pushes priority-9 incident alert

    Gotify message reaches every on-call device within 10 seconds of incident detection — before the support lead finishes reading the ticket.

  • Human Resources
    7 min / week
    Onboarding access confirmation

    HR manually checks systems and emails the new hire to confirm their accounts and notification access are live.

    Human Resources Agent
    0 min
    Agent verifies and confirms automatically

    After creating the Gotify client for a new hire, the agent sends a welcome push and confirms the token is active — HR closes the checklist item without touching a dashboard.

  • Finance
    13 min / week
    Budget overage manual alert

    Finance analyst spots a budget breach in the spreadsheet and manually emails the team and deal owner — often same day, sometimes the next morning.

    Finance Agent
    0 min
    Agent fires priority-8 budget alert instantly

    The moment an overage flag appears in the finance tracker, Gotify pushes a named alert to every finance device — the team acts before the business day ends.

  • Operations
    25 min / week
    Threshold breach manual page

    Ops engineer monitors dashboards, detects a metric breach, and manually pages the team via Slack or phone.

    Operations Agent
    0 min
    Agent detects and pushes threshold alert

    Gotify fires a specific metric breach alert to all ops devices within 30 seconds of the spreadsheet value crossing the threshold — no dashboard watching needed.

  • Legal
    6 min / week
    Compliance deadline reminder

    Legal coordinator manually sends reminder emails when a compliance filing deadline is approaching — easy to miss with a full calendar.

    Legal Agent
    0 min
    Agent sends scheduled compliance push

    Gotify delivers a named filing deadline reminder to legal team devices 48 hours and 2 hours before each deadline — zero reminders missed.

+ 100s of other Gotify automations
Average monthly
10 hrs / person / month
Average monthly
10 hrs / person / month
Calculator

Calculate what your team saves

Team size
10 people
Hourly rate
$20 / hr
Hours saved / week
25
Hours saved / year
1,250
Annual ROI
$25,000

Based on Gotify's typical team usage — the visible tasks plus a few other automations the agent runs: ~2.5 hrs / person / week of admin work automated.

Connect

How to plug Gotify into Actionist

Pick the connection method that suits your environment.

The fastest path — install Gotify's MCP server from the Apps library and the agent connects to your self-hosted Gotify instance through a single authorised handshake. No tokens to manage manually; the MCP layer handles credential refresh automatically.

1
Open the Apps tab

Find Gotify in the Apps library and click Connect. MCP is selected by default.

2
Enter your Gotify server URL

Provide the base URL of your self-hosted Gotify instance (e.g. https://push.yourdomain.com). Actionist connects to the MCP server you have running against that instance.

3
Test the connection

Actionist runs a read-only call to verify the handshake. You're ready.

Actions

15 actions your agent can call

Read and write operations available to your Actionist agent.

Triggers

7 events your agent can react to

Events your agent watches for, and the actions it kicks off in response.

Skills

Skills that pair with Gotify

Reusable agent skills that work well alongside this app.

No paired skills curated yet. Add this app to your agent to discover what fits.
MCP servers

MCP servers that work with Gotify

Connect Actionist to MCP servers built for or around this app.

gotify-mcp
Official

MCP server that exposes Gotify's full API — send messages, manage applications, and handle clients from any Actionist workflow.

Gotify MCP
Official

Self-hosted Gotify MCP server for push notification management — send messages, list applications, and manage clients on your own infrastructure.

FAQs

Questions about Gotify + Actionist

How do I connect Actionist to my self-hosted Gotify server?
In the Actionist Apps tab, find Gotify and click Connect. Choose MCP (recommended) and enter your Gotify server's base URL — for example, https://push.yourdomain.com. Actionist will verify the connection with a test read before activating. If you prefer a token-based connection, switch to API Token mode, create an application in your Gotify dashboard under Apps, copy the generated token, and paste it into Actionist.
What credentials does Actionist need to send messages via Gotify?
For the API Token method, Actionist needs an App API Token — not a Client token. App tokens are generated per application in your Gotify dashboard (Apps → your app → Token) and authorise sending messages to that specific channel. Client tokens are for receiving notifications and are not used by Actionist. Keep each integration's token separate so you can revoke one without affecting others.
Can I combine Gotify with other apps in Actionist workflows?
Yes — Gotify works as both a notification delivery layer and an event trigger inside Actionist workflows. You can have a GitHub Actions completion fire a Gotify message, or use a Gotify high-priority message as the event that kicks off a PagerDuty incident and a Slack post. Gotify pairs naturally with any app in your infrastructure stack because it sits on your own servers and has no rate limits imposed by a third party.
What are the most common Gotify automation use cases?
The most-used patterns are: (1) infrastructure alerting — push a message when a deployment completes, a service goes down, or a metric threshold is breached; (2) on-call paging — route high-priority messages to the on-call engineer's device before any human notices; (3) budget and compliance alerts — send a named push when a finance threshold or deadline is hit; (4) workflow notifications — confirm to the team that a long-running automated job finished successfully without anyone having to check a dashboard.
How do I avoid flooding devices with duplicate Gotify alerts?
Before sending a message, use the Get all messages action to check whether an alert for the same event already exists in the channel — compare titles or include a unique event ID in the message body. For recurring monitors, store the last-sent message ID in a variable and skip sending if the previous message is still in the channel. You can also use message priority to separate informational noise (priority 1–4) from actionable alerts (priority 7–10) so operators can mute low-priority channels during off-hours.
How does message priority work in Gotify?
Gotify uses a numeric priority scale from 1 to 10. Priority 1–4 are low — messages arrive silently or as minimal notifications on most clients. Priority 5–7 are medium — standard push behaviour. Priority 8–10 are high — clients configured to respect priority will trigger heads-up notifications, sound alerts, or bypass Do Not Disturb. When the agent sends a message using Set message priority or Create message with a priority field, it sets this value explicitly. Use priority 8 or above for incidents that require immediate human attention.
Can I use Gotify triggers in Actionist if my server has no internet exposure?
Gotify triggers in Actionist work via the MCP server running on your local network alongside the Gotify instance — the MCP connection polls or subscribes to your server directly, so your Gotify installation does not need to be publicly accessible. If you are running Actionist on a machine inside the same network as your Gotify server, triggers will work without opening any inbound firewall ports. For remote access, a reverse proxy with authentication (e.g. nginx with SSL) is the recommended pattern.
How do I manage Gotify applications and clients at scale?
Use the List applications and List clients actions on a schedule to audit what is registered on your server. Cross-reference the results against your service registry or employee directory to identify orphaned applications (services no longer active) and stale clients (devices belonging to former employees). The Delete application and Delete client actions let the agent clean up automatically — revocation is instant, and the token stops working the moment the record is deleted.