Pushover Node Lists twice Timestamp which is a bug, and misses TTL parameter

[aalmenar]

Bug Description

We you configure the Pushover Node, you can see that timestamp is included twice and TTL is missing which i bealive it was an error when it was implemented.

TTL fields is an integer with the number of seconds to delete the message from the user inbox.

To Reproduce

Add a pushover node, go to Additional Fields, Click on Add Field. There you will have listed twice timestamp which show two timstamp fields.

Expected behavior

To show a single field, and to show on the list of additional fields TTL

Debug Info

Debug info

core

• n8nVersion: 2.11.2
• platform: docker (self-hosted)
• nodeJsVersion: 24.13.1
• nodeEnv: production
• database: sqlite
• executionMode: regular
• concurrency: -1
• license: enterprise (production)
• consumerId: 5a1614bd-8f1b-462d-baaf-061b41e5a691

storage

• success: all
• error: all
• progress: false
• manual: true
• binaryMode: filesystem

pruning

• enabled: true
• maxAge: 336 hours
• maxCount: 10000 executions

client

• userAgent: mozilla/5.0 (iphone; cpu iphone os 18_7 like mac os x) applewebkit/605.1.15 (khtml, like gecko) version/26.3 mobile/15e148 safari/604.1

Generated at: 2026-03-13T07:36:19.120Z

Operating System

Debian 12/13

n8n Version

2.11.2

Node.js Version

24.13.1

Database

SQLite (default)

Execution mode

main (default)

Hosting

self hosted

[n8n-assistant]

Hey @aalmenar,

Thank you for reaching out! We’ve received your issue and are looking into it. To help us track this internally, we’ve created a Linear ticket with the reference: "GHC-7257".

We’ll keep you updated as we make progress, but if you have any additional details or context to share, feel free to add them here - it’s always helpful!

Thanks for your patience and for bringing this to our attention.

---

For INTERNAL use only: GHC-7257

[VishishtaDilsara]

#triage:in-progress

[VishishtaDilsara]

Hi! @aalmenar
Thank you for raising this issue, the first step of triage is completed, and it has been routed internally for further investigation.

We have successfully reproduced the bug you mentions. It appeared duplicate fields for Time Stamp. Now our team will look into this.

#triage:complete

[aalmenar]

There was a pull request for the previous bug i reported also: #11287 that fixes this issue

[mango766]

Hi! I noticed this issue and put together a fix in #27027. It removes the duplicate Timestamp entry from the Additional Fields dropdown and adds the missing TTL (Time to Live) parameter, which lets users set how many seconds before a message is automatically deleted from their devices (as documented in the Pushover API: https://pushover.net/api). Happy to adjust anything if needed.