Resources · n8n integration

Spontit n8n integrationAutomate Spontit with n8n.

Some alerts have to reach a phone, not another app. The Spontit n8n integration exposes one resource, Push, with a single operation and 12 optional fields behind Additional Fields. It fits builders who already run workflows in n8n and want the result on their own screen.

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Spontit n8n integration actually do?

The Spontit node lets a workflow step send a push notification to the devices that follow your Spontit account, or one of your channels. It ships with n8n, so there is nothing to install on n8n Cloud or on a self-hosted instance. The catalogue holds one resource, Push, and one operation, Create a push notification, with 12 optional fields grouped under Additional Fields.

Three shapes come back often. The first is the scheduled digest: a Schedule Trigger fires each morning, a weather or metrics node collects the numbers, and the push drops the summary on your phone before you open a laptop.

The second is the threshold alert. A workflow reads a Google Sheets range, an IF node keeps the rows that cross a limit, and the push carries the row text in Content with the sheet address in Link. One tap on the notification and the source is open.

The third is escalation. Routine notices already land in Slack or Telegram, where they wait for someone to scroll. The branch that cannot wait gets a Spontit push instead, on a channel named in Channel Name so only the people following that channel get woken up. Teams that also keep Pushover in the workflow usually split the two by audience, not by severity.

The node holds that one operation. For anything else in the Spontit API, the HTTP Request node calls any endpoint and reuses the same credential through its predefined authentication.

Two smaller fields decide what happens once someone taps the notification. Open Link In App chooses between the iOS app and Safari for the URL you attached, while the Android PWA opens every link in the default browser anyway. Open In Home Feed arbitrates between the home feed and a standalone page for the notification, the standalone page being the default.

Two numbers shape the message before you write it: Content stops at 2500 characters and Title at 100. A push expires 10 days after it is sent unless Expiration Stamp says otherwise. If n8n itself is new ground, the n8n training covers the workflow basics this page takes for granted.

Connect

How do you connect Spontit to n8n?

  1. 01

    Create the credential once

    Open the Credentials menu in n8n and add a Spontit credential. A credential is the stored set of connection details for one account: you fill it once, n8n keeps it, and every workflow that talks to Spontit picks it from a dropdown afterwards. The Spontit node has no authentication selector, so there is a single way in and no method to compare.

  2. 02

    Fill it with your own Spontit values

    The values come from your Spontit account, and n8n stores them under the name you give the credential. Name it for the account it belongs to rather than for the workflow, because the same credential will show up in every Spontit node you add later. If several people share the instance, that name is the only clue about which account a push goes out from.

  3. 03

    Run one push before building anything

    Drop a Spontit node in an empty workflow, pick the credential in its dropdown, type two words in Content, and execute the node on its own. The notification either shows up on your device or it does not, and you know where you stand in under a minute. Only then wire the node to whatever produces the real text.

Actions

What the Spontit node does in a workflow

The Spontit node exposes 1 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
ResourceCreate
Push

Push

1 operation
01

Create a push notification

push.create

What you see in n8n

Notes & use cases

Sends a push notification from the workflow to the devices following your Spontit account or one of your channels.

Key parameters

  • Content: the text of the push, capped at 2500 characters, usually an expression such as {{ $json.field }} pulled from the previous node.
  • Title: appears in bold at the top, up to 100 characters.
  • Channel Name: the name of a channel you created; empty, the push goes to your main account.
  • Link: a valid URL attached to the push.
  • Schedule: a Unix timestamp to send the push later.
Use cases
start with Content alone and run the node once, then add Title and Link when you know the text lands.
Need help

Need help automating Spontit with n8n?

A person reads every message.

FAQ

Spontit and n8n, the questions that come next

01Is the Spontit integration free in n8n?
Yes on the n8n side. The node ships with n8n, so there is nothing to install and no extra n8n cost, whether you run n8n Cloud or a self-hosted instance under the Community Edition and its Sustainable Use licence. A workflow behaves the same way in both, which matters if you prototype on Cloud and move the finished version onto your own server later. What a Spontit account itself costs sits outside the n8n catalogue, so this page does not answer that part. Budget the n8n side at zero and check the Spontit side on your own account.
02What credentials does the Spontit n8n integration need?
One Spontit credential, created once from the Credentials menu in n8n. A credential is the stored set of connection details for an account: fill it in a single time and every node that needs it offers it in a dropdown, so adding a second or a tenth workflow costs no setup. The node carries no authentication selector, which means there is a single way in and no method to pick between. Give the credential a name that says which Spontit account it belongs to, because that name is what you will read in the node dropdown months later.
03What are the limits of the Spontit node in n8n?
The catalogue gives one resource, Push, and one operation. For anything else in the Spontit API, the HTTP Request node calls any endpoint and reuses the same credential through its predefined authentication, so you are never stuck at the edge of the node. On the message itself, Content stops at 2500 characters, Title at 100, and Subtitle at 20, that last one showing only on iOS devices. A push expires 10 days after it is sent by default. Once the expiry time passes, it becomes unreachable within 15 to 30 minutes, though it stays on device screens until dismissed or clicked.
04Can an n8n workflow react to Spontit in real time?
No, and the reason is structural: this tool has no trigger node in n8n. A workflow about Spontit therefore starts somewhere else, with a Schedule Trigger running at a fixed interval, with an n8n Webhook, meaning a URL that another service calls, or with the trigger of another tool you already use. Create a push notification then runs as an ordinary step further down the workflow. Pick the Schedule Trigger when the push is a digest you want at a set hour, and the Webhook when something outside n8n decides the moment.
05n8n or Make for Spontit?
It depends on four things, and price is only one of them. Hosting: n8n runs on your own server through Docker or npm, or on n8n Cloud, while Make is hosted only. Data control follows from that choice, since a self-hosted instance keeps the push content on machines you own. Cost model: Make bills per operation, which is worth modelling if a workflow fans out one push per row. Visual logic: both draw the workflow on a canvas, and the one that reads better to you is a real criterion, not a detail. Both send the push.
Hack'celeration Lab

Get our weekly integration tips.

No spam. Unsubscribe anytime.