NudgeBell
Reminders your agent creates: email, WhatsApp, SMS or call, in steps you set.
Community: Submitted by a user or imported; check the owner before granting accessOnlineAPI key requiredGlobalFreeCan modify data
What it can do
- Create Reminder: Schedule a reminder that escalates the way the user set it and stops when they acknowledge. It fires from NudgeBell's own servers, so it still happens if this agent, this machine, or
- List Reminders: List the account's reminders with their next trigger time, how far the current escalation chain has got, and whether the user has acknowledged. Use this to answer 'what am I being remi
- Get Reminder: Full detail of a single reminder: every step, its message, its timing, and what happened to it on the current occurrence.
What data it sees
Do you need an account
An API key from the service settings is required
Reminders your agent creates: email, WhatsApp, SMS or call, in steps you set. Stops on acknowledge.
Server tool list (7)
Raw names from tools/list. Only developers need these.
| create_reminder | Schedule a reminder that escalates the way the user set it and stops when they acknowledge. It fires from NudgeBell's own servers, so it still happens if this agent, this machine, or this conversation is long gone. A reminder is one step or up to five. Each step is a channel, a message, and how many minutes after the trigger it fires. A single email, a single call, or a chain across any channels in any order with any gaps are all fine: build exactly what the user asked for, and do not add steps or channels they did not ask for. If the user acknowledges at any step (presses 1 on the call, taps the link in a text, clicks the button in the email), every remaining step is cancelled automatically. You do not choose who is contacted. NudgeBell only ever contacts the account owner's own verified phone and email; there is no recipient parameter and requests that try to add one are rejected. You also do not need to send a timezone — the account's timezone is used. |
| list_reminders | List the account's reminders with their next trigger time, how far the current escalation chain has got, and whether the user has acknowledged. Use this to answer 'what am I being reminded about?' or to find the id of a reminder before cancelling or pausing it. |
| get_reminder | Full detail of a single reminder: every step, its message, its timing, and what happened to it on the current occurrence. |
| get_reminder_status | Per-step delivery and acknowledgment status for the live occurrence: scheduled, sent, confirmed, failed or skipped, with timestamps. This is how you answer 'did that reminder go out?' and 'have they responded yet?'. You can read acknowledgment but you can never set it — only the human can acknowledge, by pressing 1 on the call or tapping the link. |
| pause_reminder | Stop a reminder and cancel its pending steps, keeping the reminder and its history intact. Reversible — the user resumes it from the NudgeBell dashboard. This is the DEFAULT way to stop a reminder: prefer it over cancel_reminder unless the user explicitly asked to delete it or stop it permanently. |
| cancel_reminder | DESTRUCTIVE AND IRREVERSIBLE. Cancelling permanently DELETES the reminder, its escalation steps and its entire delivery history from NudgeBell. Nothing is archived and there is no undo — not from this API and not from the dashboard. Only use this when the user explicitly says delete, cancel for good, or stop permanently. For anything else — 'not right now', 'skip today', 'hold off', 'I'm on holiday', or any doubt at all — use pause_reminder, which stops the chain, keeps the history, and can be resumed from the dashboard. |
| get_account | The account's verified contacts (the only places a reminder can ever be delivered), timezone, plan, credit balance and active-reminder limit. Read this first if you are unsure whether a phone call is possible or whether there are enough credits. |