OnePass · Scenarios

15 things you can push, with the steps to set each one up

You do not need to be a developer to use OnePass. Pick a scenario you recognize, follow the steps, and finish in a few minutes. Each card says whether it is no-code, a one-time setup, or something an AI assistant can write for you.

Personal and family Work and team Monitoring and automation Feeds and interaction
Difficulty: No code One-time setup AI can write it

Most scenarios come down to one address: a channel code plus a title and body. Paste it into a scheduled task, a CI step, a monitoring alert or a downloader's "run after completion".

https://www.phprm.com/services/push/trigger/your-32-char-channel-code?head=Backup%20finished&body=Database%20is%20on%20the%20NAS

A browser can open this address directly. URL-encode Chinese or spaces in the parameters. You can also send the same fields by POST. See the API documentation.

1Personal and family reminders

Fixed-time reminders that land in the app you already check.

01No code

Medicine and daily routine

For anyone who needs to remind themselves or a family member at a fixed time.

Remind at 8:00 to take medicine and at 20:00 to check blood pressure. The message goes to WeCom, DingTalk, Feishu, Bark or email — whichever the person actually looks at.

How to set it up
  1. Create a channel in Channel management and pick a receiving app.
  2. On your phone, create a scheduled group for the reminder and choose the daily time.
  3. Press Test push and confirm the phone rings before you rely on it.

For reminders that cannot be missed, use a combo channel with email as a second copy.

Pages: Channel management · Schedule builder

02No code

Classes, exams and renewals

Parents, students, and anyone paying for several subscriptions.

Get a reminder three days and one day before a tuition deadline, an exam or a domain renewal. Set it once and forget the calendar.

How to set it up
  1. Use a combo channel if both you and your partner should be reminded.
  2. Create scheduled reminders on the phone, one per date, or use a Quartz rule for repeating cycles.
  3. Put the date in the title, such as "Tuition due in 3 days".

Quarterly tasks — domain, certificate, membership — can be one repeating rule rather than four separate reminders.

Pages: Schedule builder · Channel management

03No code

Tickets and appointment openings

Hospital bookings, concert tickets, course registration.

The hard part is not sending a message — it is being at your phone at the exact minute. Let OnePass remind you five minutes before the window opens.

How to set it up
  1. Create and test the channel the night before, not in the queue.
  2. Add a scheduled reminder five minutes before the opening time.
  3. Save the booking page with the browser extension so it is one click away.

Send a test push at the same time of day once, so you know notification permissions are still on.

Pages: Extension and client · Channel management

04AI can write it

Morning briefing

People who want weather, their to-do list and industry news without opening five apps.

An AI assistant gathers the summary every morning and pushes it as one message, with Markdown formatting.

How to set it up
  1. Configure the MCP Server in Cursor, Claude or Trae, or install the SKILL.
  2. Ask the assistant to produce a morning briefing and push it to your channel code.
  3. Schedule the task for 8:00 using the assistant's own scheduling or a cron job.

Save the prompt once; changing the topics next week is then a one-line edit.

Pages: MCP setup · push-sdk.js guide

2Work and team notices

Small teams get the most value: one message reaches the group, the owner and the archive.

05One-time setup

New orders and after-sales

Small shops, independent sellers, customer service teams.

When an order is paid or a refund is requested, the whole service group sees it immediately instead of refreshing a backend.

How to set it up
  1. Create a combo channel with the service group's WeCom, DingTalk or Feishu bot.
  2. In your order system or form tool, find the Webhook notification setting and paste the trigger address with your channel code.
  3. If the system has no Webhook, ask a developer or an AI assistant to add a five-line request.

Put the order number and amount in the title — the group can search for them later.

Pages: API documentation · Channel management

06No code

Team announcements and shift handover

Small teams, communities and online shops with rotating shifts.

Publish an announcement once and let members subscribe with their own channel, or push a 9:00 and 21:00 handover reminder to the group.

How to set it up
  1. Create a combo channel and attach the group bot plus an email address for the record.
  2. Make the channel public so members can subscribe from the market.
  3. Add scheduled reminders for the handover times.

Announcements belong in the group chat as well; push is for people who are not looking at it.

Pages: Market · Groups I joined

07One-time setup

Backup, sync and conversion finished

NAS owners, site admins and anyone running long copy jobs.

Stop checking the progress bar. The backup script pushes one line when it finishes, or when it fails.

How to set it up
  1. In Baota, open Scheduled tasks → Shell script and add the trigger address after the backup command.
  2. On Synology, use Control Panel → Task Scheduler → User-defined script.
  3. In Qinglong, add the trigger line to the end of the task command.

To alert only on failure, wrap the call in an exit-code check; an AI assistant can write those two lines.

Pages: API documentation · Help center

08One-time setup

Approvals, tickets and form submissions

Administration, HR and customer support.

A new leave request, a support ticket or a website enquiry arrives in the group as a short message with a link to the record.

How to set it up
  1. Look for the Webhook or "notify an external service" setting in the form or ticket tool.
  2. Paste the trigger address with your channel code.
  3. Map the title to the event type, for example "New ticket #1234".

Keep personal data out of the message body; send a link and let people open the record instead.

Pages: API documentation · Channel management

3Monitoring and automation

Machines should tell you when something happens, not make you watch a dashboard.

09One-time setup

Website down and recovered

Site owners and on-call engineers.

Get one alert when the site goes down and another when it is back, so the group knows the incident is over.

How to set it up
  1. In Uptime Kuma, Baota monitoring or your cloud monitor, choose Webhook as the notification method.
  2. Paste the trigger address with the channel code; use the title field for the domain and status.
  3. Send both the alert and the recovery notification to a combo channel.

Do not host the monitor on the same server it watches, or a dead server also kills the alert.

Pages: API documentation · Domain verification

10AI can write it

Restock and price drops

Shoppers chasing limited items or a better price.

Subscribe to a market channel and filter by keyword, or run a small monitor that checks a page and pushes only when the price actually changes.

How to set it up
  1. Start with the market: join a deal channel and set keyword forwarding to "restock" or "price drop".
  2. For a specific product page, ask an AI assistant to write a scheduled checker that calls the trigger address.
  3. Keep the check interval reasonable so the shop does not block you.

The cheapest option is subscribing before building anything; only automate the page nobody else monitors.

Pages: Market · Groups I joined

11AI can write it

Build results from GitHub or GitLab

Developers, and anyone whose AI assistant maintains a repository.

A failed build should reach your phone with the branch name, not wait until you open the laptop.

How to set it up
  1. Add a final step to the pipeline that sends the trigger address with the result and branch.
  2. Use different titles for success and failure so the phone notification is readable at a glance.
  3. Ask an AI assistant to edit the workflow file if you are unsure about the syntax.

Send failures to the team group and successes to your own channel — most people only need the bad news.

Pages: MCP setup · push-sdk.js guide

12One-time setup

Download and transcode finished

NAS users, download boxes, video editors.

qBittorrent, Synology Download Station and many transcoders can run a command when a job completes.

How to set it up
  1. Find the "run after completion" or "notification script" option in the downloader.
  2. Add the trigger address with the channel code.
  3. Put the file name in the title and the save path in the body.

One message per finished batch is enough; per-file pushes become noise for a season pack.

Pages: API documentation · Help center

4Feeds, danmu and interaction

For people who publish, stream, or just want fewer notifications, not more.

13No code

Only the deals you care about

Shoppers who want a handful of alerts instead of a flooded group.

Join a public deal channel, then forward only messages containing your keywords — a graphics card, a flight, a restock.

How to set it up
  1. Open the market and join a channel.
  2. In the join dialog, choose keyword forwarding and enter your words.
  3. Mute or leave at any time from Groups I joined; leaving only affects your account.

Public channels are run by their publishers; report messages that break the rules.

Pages: Market · Help center

14AI can write it

Live danmu and page interaction

Streamers, site owners and event organizers.

Add a danmu layer with one script tag. Viewers' messages can also reach your phone through the channel while the page is open.

How to set it up
  1. Try the no-login demo on the danmu demo page and copy the snippet.
  2. Paste the snippet before the closing body tag of your page.
  3. For long-term use on your own domain, verify it first — the channel code can then be omitted and the rate limit lifted.

For a big screen or OBS, open the danmu page as a browser source — no plugin needed.

Pages: Danmu demo · Domain verification

15AI can write it

Tell me when the AI finishes

Anyone running long AI coding or research tasks.

Start a long task, walk away, and get one message when it is done — with a short summary and a link to the result.

How to set it up
  1. Configure the MCP Server or install the SKILL in your AI tool.
  2. Put the instruction in the prompt: "when finished, push a summary to my channel code".
  3. For your own website users, the push-sdk.js guide shows the same flow end to end.

Ask for the summary in Markdown; it reads better in WeCom, DingTalk and Feishu.

Pages: MCP setup · push-sdk.js guide

Not sure where to start?

Begin with one fixed-time reminder in scenario 01. Once you have received it, the rest are the same three steps: create a channel, copy the channel code, and hand it to the task that knows when something happened.

Questions about a channel or a missing message are answered in the help center. The exact parameters are in the API documentation.

OnePass · Scenarios · Examples use common tools; your own system only needs to be able to send one HTTP request.

15 push notification scenarios for personal, team and website use

OnePass can be used without writing code. This page collects 15 concrete scenarios — medicine reminders, renewal dates, ticket openings, order notifications, backup completion, site downtime, price drops, build results, deal subscriptions, danmu and AI task completion — and gives the actual steps for each, marking whether it is no-code, a one-time configuration, or something an AI assistant can write.

Most scenarios share one address

A trigger address contains the 32-character channel code plus the title and body parameters. It can be pasted into a scheduled task, a CI step, a monitoring Webhook or a downloader's completion hook. Browsers can open the same address directly; Chinese and spaces in parameters must be URL-encoded, and POST is also supported.

Groups on this page

  • Personal and family: fixed-time reminders, class and renewal dates, ticket openings, AI-generated morning briefings.
  • Work and team: new orders and after-sales, announcements and shift handover, backup and conversion completion, approvals and form submissions.
  • Monitoring and automation: website down and recovered, restock and price drops, build results, download completion.
  • Feeds and interaction: keyword-filtered deal subscriptions, live danmu, and "tell me when the AI finishes".

What you can do on this page

  • Pick a scenario that matches your day and follow its three or four steps.
  • Check the difficulty tag first: no-code scenarios use only the site UI, one-time setups need a Webhook field, and AI-assisted ones can be delegated to an assistant.
  • Open the linked pages for channel management, the schedule builder, the market, MCP or the API documentation when a step needs more detail.

For channel problems or missing messages, use the help center. The exact parameters and response fields are in the API documentation.