The action Pushover

Modified on Fri, 15 Aug at 5:24 PM

Purpose

Sends a push notification from the scenario to Pushover, which delivers it to phones (IOs and Android), tablets and desktop clients registered to a Pushover user/group key. Use this action to alert operators about processed files, errors or provide a quick link to results.


Where to add

Put this action after any step that should trigger an alert (Important file, Convert to PDF, Save File, Summarize with AI, Print Document, Send File to FTP, etc.).


Settings to connect to PushOver



Main fields and how to configure

  • Pushover User key
    The recipient user or group key (not an email). Paste the key you or the target user obtained from Pushover.
  • Message title
    Short headline for the notification (appears as the alert title on devices). Use fields to insert dynamic values.
  • Message
    The main notification body text. Use Fields for filename, date, ...
  • Add a link in notification (More options)
    An URL that will be shown in the notification and opened on tap. Useful to point recipients to a network share, FTP path, or any other location.
  • Notification type / Priority
    Choose how urgent the notification is (Normal, Low, High, Emergency) . Priority controls sound on the device.
  • Send to specific device name (More options)
    Optionally restrict the notification to a named device registered on the Pushover account rather than all devices.
  • Your own Pushover token to get unlimited messages (Application token)
    Optionally provide your application token (API token) from Pushover if you want to use your own app credentials (helps avoid per-account limits and lets you manage messages centrally). If left blank the action may use our free credit.
  • Send a test message
    Use this to verify the User key, token and message formatting before running the full scenario.


Quick setup steps

  1. Install the Pushover application on your device(s) from https://pushover.net
  2. Launch the app and it will walk you through creating a Pushover account and registering your device.
  3. Obtain the recipient’s User Key. Your User Key is a randomly generated identifier which allows Rofiles to send Pushover notifications to your devices.
  4. Add the Pushover action to your scenario and paste the Pushover User key into the field.
  5. Compose Message title and Message. Use Fields to add dynamic content if needed.
  6. Click Send a test message to verify delivery, then save the action.


The cost is very simple

  • Free from Rofiles
  • To use the app on your phone you have to buy the Pushover application, it's just a $5 USD one-time purchase on each platform (iPhone/iPad, Android, and Desktop) where you want to receive Pushover notifications. 
  • There are no subscription fees to use Pushover.
  • Try the app for free during 30 days here >


Behavior notes and limitations

  • Text and link only by default: the action posts a push notification (title, message and optional URL). It does not upload arbitrary files or attach documents to the notification. If you need to deliver files to users, use services that support file uploads (Slack, Telegram) as part of your workflow.
  • Device targeting: you can restrict messages to a particular device name registered with the Pushover user to avoid alerting all devices.  
  • Rate limits / quotas: Pushover enforces usage limits and has a business model (free trial + paid plans). Check Pushover docs for current limits and billing. Using your own application token may help centralize and manage usage.


Security, privacy and compliance

  • Notifications go through Pushover servers. Do not push sensitive data unless allowed by your policies; prefer sending a link to a secured file location if necessary.
  • We don't read your message, we don't have access to them, Rofiles is local to your computer.


Troubleshooting

  • No notification received: verify the User key and (if used) the Application token, ensure the recipient has the Pushover client installed and notifications enabled, and use Send a test message to debug.  
  • “Invalid token” or “Invalid user”: confirm you pasted the exact keys from Pushover (no extra spaces).  
  • Messages not appearing on a device: check device name spelling if targeting a specific device, and ensure the device is online and allowed to receive push notifications.  


Examples

  • Simple success alert: Title = "File processed", Message = "Document %FILENAME_FULL% processed at %DATE%. 
  • Operator alert to a single tablet: Device name = "WarehouseTablet", Priority = High, Message = "New VIP file received %FILENAME_FULL%."


Done! Add the action, paste the Pushover User key (and optionally your App token), compose a title/message and optional link, choose priority and device if needed, test with Send a test message, and the action will push notifications to the recipient’s Pushover-enabled devices. Remember: this action sends notifications (text + link) and does not attach or upload documents, use Slack or Telegram actions to post files.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article