· PushNow
How PushNow connects your automations to your iPhone
PushNow is an iOS inbox for results from AI agents, scripts, monitoring tools, and other automations. A sender submits a message to your account so you can review the result on your phone. Use it for a finished build, a monitoring event, or a report that deserves your attention, with a link back to the original context.
How do I connect an automation?
Sign in to PushNow on your iPhone and set up the device. Enable notifications if you want alerts outside the app; iOS settings determine how those alerts appear.
Start sender authorization with the PushNow CLI. Approve its code in the app and compare the sender fingerprint. Then verify the account fingerprint in the CLI before trusting the connection.
Send a small test message with a recognizable title and a useful link. Check that it appears in the correct inbox, then confirm notification behavior on the phone before relying on the workflow.
Keep sender credentials private and use separate senders for separate integrations. If a sender is no longer needed, revoke its access. Consult the API docs when adding scheduling, files, or retry handling.
Questions about PushNow
What can I send to PushNow?
Send results that your automation produces: build summaries, monitoring events, research notes, or scheduled reports. Messages can carry a title, body, and links to the source. The content guide documents file and media handling and the limits that apply; PushNow does not create or verify the underlying report for you.
Does an accepted API request prove that my iPhone received an alert?
No. API acceptance, inbox storage, push delivery, and a visible notification are different steps. Check the inbox and the actual device. Network conditions, notification permissions, Focus settings, and preview processing can change when and how an alert appears. Do not use PushNow as the only channel for emergency or safety-critical alerts.
Can I save a result without interrupting myself?
The product separates inbox content from notification behavior. Choose an in-app-only workflow when a result can wait, and use an alert for results that need attention. Consult the current API documentation for the delivery fields supported by your integration; setting a priority does not override iOS notification settings.
Who can read encrypted message content?
The documented v2 flow encrypts message content for the account archive before upload. Trusted devices receive archive access through approval. Routing identifiers, source names, timing, ciphertext sizes, and delivery attempts remain service metadata. Avoid placing secrets in source names, and verify fingerprints when approving a sender or another device.
How do plans and purchases work?
Review the membership screen for the products, currency, billing period, and limits currently available to your App Store account. Confirm the purchase sheet before subscribing and use Restore Purchases if access is missing after reinstalling. Website examples are not a substitute for the current store price or entitlement state.
Where should I start when an integration fails?
First verify the account and authorized sender, then check the response and relevant logs without sharing credentials. Test a minimal message before adding links, attachments, or scheduling. If the item exists but no alert appears, inspect the phone notification settings separately. Send support the timestamp, error, and reproduction steps, with secrets removed.