Pushover node gains message expiration field
The Pushover node in n8n now supports message expiration. A duplicate timestamp field has been replaced with the missing TTL field, allowing workflows to automatically delete notifications from devices after a set time.
The Pushover node in n8n had a problem: it included a timestamp field that served no practical purpose while omitting the TTL (Time to Live) field that the Pushover API actually supports. The timestamp field displayed a message's date and time, but the node was already sending timestamps automatically.
That changed with this fix. The redundant timestamp field is gone, replaced with TTL support. Now when sending Pushover notifications through n8n, workflows can specify how long a message should live on receiving devices before being automatically deleted. Set TTL to 3600 seconds, for example, and the notification disappears from phones after an hour.
This matters for workflow builders who need ephemeral notifications—on-call alerts that should vanish after acknowledgment, or time-sensitive reminders that become irrelevant quickly. The fix aligns the n8n integration with what Pushover's API actually offers.
The change touches the file in n8n's nodes-base package.
View Original GitHub Description
Summary
Fixing the duplicate timestamp field, by swapping it for the missing ttl field described in the api documentation: https://pushover.net/api#ttl
Related Linear tickets, Github issues, and Community forum posts
https://github.com/n8n-io/n8n/issues/10984 Fixes https://github.com/n8n-io/n8n/issues/26973