Title: NotifyCrew – Team reminders for Slack Author: Aditya Shah Published: July 24, 2026 Last modified: July 25, 2026 --- Search plugins ![](https://ps.w.org/notifycrew/assets/banner-772x250.png?rev=3622164) ![](https://ps.w.org/notifycrew/assets/icon-256x256.png?rev=3621729) # NotifyCrew – Team reminders for Slack By [Aditya Shah](https://profiles.wordpress.org/ethicaladitya/) [Download](https://downloads.wordpress.org/plugin/notifycrew.1.1.0.zip) * [Details](https://co.wordpress.org/plugins/notifycrew/#description) * [Reviews](https://co.wordpress.org/plugins/notifycrew/#reviews) * [Installation](https://co.wordpress.org/plugins/notifycrew/#installation) * [Development](https://co.wordpress.org/plugins/notifycrew/#developers) [Support](https://wordpress.org/support/plugin/notifycrew/) ## Description Your team already lives in Slack. Your deadlines live somewhere else: a spreadsheet, a calendar nobody opens, or someone’s memory. NotifyCrew closes that gap. Schedule a reminder in WordPress, pick the team it belongs to, and NotifyCrew posts it to that team’s Slack channel at the right moment. No Zapier account, no monthly per-seat fee, no third-party service holding your data. Your WordPress site talks to Slack directly. #### Why teams choose NotifyCrew * **No per-seat pricing.** It is a WordPress plugin. Add as many teams and members as you want. * **No middleman service.** Reminders go straight from your site to Slack. Nothing is routed through anyone else’s server. * **Your Slack credentials stay encrypted.** Webhook URLs and bot tokens are encrypted at rest with libsodium, not stored as plain text in the options table. * **Delivery you can trust.** If Slack is down or your token expires, NotifyCrew retries automatically and tells you when something is wrong instead of failing silently. * **Your team does not need WordPress accounts.** Members can be added by email address alone and still manage their own reminders through the optional portal. #### What you can do * **Send reminders to Slack on a schedule.** Pick a date and time, or use a one- click preset like “In 4 hours” or “In 48 hours”. * **Give every team its own channel.** The design team posts to `#design`, engineering posts to `#eng-standup`. A global fallback channel covers teams without one. * **Ping the right people.** Add `@channel` or `@here` per team so urgent reminders actually get seen. * **Recover from failures automatically.** Failed deliveries retry with exponential backoff, and you get an email plus an admin notice when a reminder keeps failing. * **Send rich, readable messages.** Reminders arrive as Slack Block Kit messages with a header, the scheduled time, a task or ticket link, who submitted it, and any notes. * **Let your team file their own reminders.** Drop a shortcode on any page for a Google-authenticated portal, restricted to the email domains you allow. * **Set it and forget it.** Make any reminder repeat daily, weekly, or monthly. NotifyCrew auto-creates the next occurrence so standups, deadlines, and check- ins keep running. * **Keep a full audit trail.** Every reminder event is logged with a timestamp, so you can always answer “was this actually sent?” * **Uninstall cleanly, or not at all.** Your data is never deleted unless you explicitly opt in under Settings. #### Common uses * Daily stand-up and scrum reminders for engineering teams * Deploy windows, release freezes, and on-call handoffs * Invoice, payroll, and compliance deadlines * Content and social publishing schedules * Client check-ins and recurring agency deliverables * Nudges for anything your team keeps forgetting #### Let your team schedule their own reminders Most reminder plugins stop at the WordPress admin, which means everything routes through whoever has an admin login. NotifyCrew ships an optional frontend portal instead. Add `[ncrw_frontend_reminder_form]` to any page and your team signs in with Google, sees only the teams they belong to, and creates or edits their own reminders. No WordPress account required. Restrict access to your company’s email domains so nothing else gets through. Prefer read-only? `[ncrw_upcoming_reminders]` shows what is coming up, with filters and sorting, and nothing editable. Building your own frontend? NotifyCrew exposes REST endpoints under `ncrw/v1` so you can run the portal on any stack and keep WordPress as the backend. See the FAQ. #### Requirements * WordPress 5.8 or higher * PHP 7.4 or higher, with the sodium extension (bundled with PHP 7.2 and later) * A Slack workspace, plus either an Incoming Webhook URL or a Bot Token with the` chat:write` scope ### External services This plugin connects to the following third-party services: **Slack API (chat.postMessage)** This service delivers team reminders to Slack channels. It is activated every time a scheduled reminder is due or manually retried. Data sent: team name, reminder title, task/ticket link, submitter email address, reminder notes, and timestamp. This service is provided by Slack Technologies: [terms of service](https://slack.com/terms-of-service), [privacy policy](https://slack.com/trust/privacy/privacy-policy). **Google OAuth / Sign-In** This service authenticates users on the optional frontend reminder portal and view- only portal. It is activated when a user loads a portal page or submits a reminder form. Data sent: Google ID token (for identity verification only). This service is provided by Google LLC: [terms of service](https://policies.google.com/terms), [privacy policy](https://policies.google.com/privacy). ## Screenshots [⌊Before NotifyCrew: reminders scattered across DMs, channels, and forgotten spreadsheets. After: every reminder lives in one place, sorted by team and status, with delivery history at a glance.⌉⌊Before NotifyCrew: reminders scattered across DMs, channels, and forgotten spreadsheets. After: every reminder lives in one place, sorted by team and status, with delivery history at a glance.⌉[ Before NotifyCrew: reminders scattered across DMs, channels, and forgotten spreadsheets. After: every reminder lives in one place, sorted by team and status, with delivery history at a glance. [⌊Creating a reminder takes seconds. Pick a team, write what needs to happen, and choose a preset like "In 4 hours" — no date picker required.⌉⌊Creating a reminder takes seconds. Pick a team, write what needs to happen, and choose a preset like" In 4 hours" — no date picker required.⌉[ Creating a reminder takes seconds. Pick a team, write what needs to happen, and choose a preset like “In 4 hours” — no date picker required. [⌊Every team gets its own Slack channel and mention rules. Engineering posts to # eng-standup with @channel. Design posts to #design. No crossover, no noise.⌉⌊Every team gets its own Slack channel and mention rules. Engineering posts to #eng-standup with @channel. Design posts to #design. No crossover, no noise.⌉[ Every team gets its own Slack channel and mention rules. Engineering posts to #eng- standup with @channel. Design posts to #design. No crossover, no noise. [⌊Slack credentials encrypted with libsodium. Google OAuth for the optional team portal. Every setting in one screen.⌉⌊Slack credentials encrypted with libsodium. Google OAuth for the optional team portal. Every setting in one screen.⌉[ Slack credentials encrypted with libsodium. Google OAuth for the optional team portal. Every setting in one screen. ## Installation 1. Install and activate the plugin. A **Reminders** menu appears in your admin sidebar. 2. Go to **Reminders > Settings**, choose Incoming Webhook or Bot Token, and paste your Slack credentials. They are encrypted before they are saved. 3. Go to **Reminders > Teams** and create a team. Add members by picking WordPress users or by typing email addresses. 4. Optionally give the team its own Slack channel, a mention tag, and quick-schedule presets. 5. Go to **Reminders > Add Reminder** and schedule your first one. #### Setting up the team portal (optional) 1. In **Reminders > Settings**, enable **Frontend Reminder Intake**. 2. Add your **Google OAuth Client ID**, created at [Google Cloud Console](https://console.cloud.google.com/apis/credentials). 3. Set **Allowed Email Domains**, for example `yourcompany.com`. 4. Add `[ncrw_frontend_reminder_form]` to a page. For a read-only view, use `[ncrw_upcoming_reminders]` instead. ## FAQ ### Is NotifyCrew free? Yes. It is fully functional, GPL licensed, with no paid tier, no locked features, and no upsells. ### Do I need a paid Slack plan? No. Incoming Webhooks and Bot Tokens both work on Slack’s free plan. ### Do my team members need WordPress accounts? No. Members can be added by email address alone. If you enable the frontend portal, they sign in with Google and manage their own reminders without ever touching wp- admin. ### Can reminders repeat automatically? Yes. Set any reminder to repeat daily, weekly, monthly, or on a custom interval. Choose how long to repeat — forever, after a set number of times, or until a specific date. When a recurring reminder fires, NotifyCrew auto-creates the next occurrence so you never have to set it up again. ### How does the retry logic work? If a Slack delivery fails, NotifyCrew reschedules it with exponential backoff: 2 minutes after the first failure, then 4, then 8, then 16. After the fifth attempt it stops retrying and marks the reminder Completed so it cannot loop forever. You can also trigger a manual retry from the Reminders list at any time. ### What happens when deliveries keep failing? From the second failure onward, the site admin gets an email with the reminder title, the error Slack returned, and links back to the Reminders and Settings pages. A warning notice also appears in the admin area while failures are recent, and the latest error is shown inline next to the reminder’s attempt count. ### My reminders are not sending on time. What should I check? NotifyCrew runs on WP-Cron, which only fires when someone visits your site. On low- traffic sites, reminders can be late. Disable WP-Cron and use a real server cron job hitting `wp-cron.php` every five minutes for reliable delivery. Also confirm your Slack credentials are still valid under **Reminders > Settings**. ### Which Slack authentication mode should I use? Use an **Incoming Webhook** for the fastest setup when all reminders go to one channel. Use a **Bot Token** with the `chat:write` scope if you want per-team channels. You can switch modes at any time. ### Is my data deleted when I deactivate the plugin? No. Deactivation only clears the cron schedule. Your reminders, teams, logs, and settings are preserved. Data is removed only when you delete the plugin, and only if you enabled **Data Cleanup** in Settings first. ### What does the plugin store in my database? Four tables prefixed `ncrw_`: teams, team memberships, reminders, and an audit log of reminder events. ### Can I build my own frontend? Yes. The `ncrw/v1/portal/bootstrap` and `ncrw/v1/portal/reminder` endpoints accept an API key in the `X-NCRW-API-Key` header along with a Google ID token, so you can run a decoupled frontend on any stack. Additional endpoints under `ncrw/v1` cover listing reminders, triggering processing, and queuing retries for logged-in users. ### Is NotifyCrew translation ready? Yes. Every user-facing string uses WordPress i18n functions with the `notifycrew` text domain, and a `.pot` file is included. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “NotifyCrew – Team reminders for Slack” is open source software. The following people have contributed to this plugin. Contributors * [ Aditya Shah ](https://profiles.wordpress.org/ethicaladitya/) [Translate “NotifyCrew – Team reminders for Slack” into your language.](https://translate.wordpress.org/projects/wp-plugins/notifycrew) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/notifycrew/), check out the [SVN repository](https://plugins.svn.wordpress.org/notifycrew/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/notifycrew/) by [RSS](https://plugins.trac.wordpress.org/log/notifycrew/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 1.1.0 * New: Recurring reminders — daily, weekly, monthly, and custom intervals * New: End conditions — stop after N occurrences or on a specific date * Improved: Auto-reschedule creates the next occurrence when a recurring reminder fires #### 1.0.0 * Initial release of NotifyCrew. ## Meta * Version **1.1.0** * Last updated **13 hours ago** * Active installations **Fewer than 10** * WordPress version ** 5.8 or higher ** * Tested up to **7.0.2** * PHP version ** 7.4 or higher ** * Language * [English (US)](https://wordpress.org/plugins/notifycrew/) * Tags * [Notifications](https://co.wordpress.org/plugins/tags/notifications/)[reminders](https://co.wordpress.org/plugins/tags/reminders/) [scheduler](https://co.wordpress.org/plugins/tags/scheduler/)[slack](https://co.wordpress.org/plugins/tags/slack/) [slack integration](https://co.wordpress.org/plugins/tags/slack-integration/) * [Advanced View](https://co.wordpress.org/plugins/notifycrew/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/notifycrew/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/notifycrew/reviews/) ## Contributors * [ Aditya Shah ](https://profiles.wordpress.org/ethicaladitya/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/notifycrew/)