Axiom Contact Form for NTFY

Description

Axiom Contact Form for NTFY is an independent plugin by Axiom Event Systems that sends contact form submissions to ntfy as a notification. It is a client for the ntfy service and is not affiliated with, sponsored by, or endorsed by the ntfy project.

It adds a lightweight contact form that is dropped onto any page with the [ntfy_contact_form] shortcode. Each submission is published to an ntfy topic, so staff get a push notification on their phone, desktop or in the ntfy web app instead of relying on email.

Try it without installing: run the plugin in WordPress Playground — a throwaway WordPress boots in your browser with the plugin installed, the settings screen open and a demo page using the shortcode.

Highlights

  • Pre-filled for the public ntfy.sh server, with a topic field.
  • Works with self-hosted ntfy servers over HTTPS.
  • Authentication via an access token (Authorization: Bearer …) or username/password (HTTP Basic).
  • Per-form notification title, priority, tags and click action.
  • Theme-aware styling: inherit the site’s colours and fonts, or set your own accent, text, field and border colours.
  • Optional phone, preferred-contact and subject fields, plus a required consent checkbox.
  • Spam trap and per-IP rate limiting.
  • Works with or without JavaScript: submissions fall back to admin-post.php.
  • Sends a test notification from the settings screen.
  • Keeps a log of every submission in the database, viewable under Axiom Contact Form Messages, so nothing is lost when the ntfy server is unreachable. Each entry shows whether delivery succeeded, the failure reason if not, and can be paged 10/20/30/50 at a time.

Security notes

  • All requests to the ntfy server are made server-side, so credentials are never sent to the browser.
  • Credentials are stored in the WordPress options table (ntcf_settings). Limit dashboard access to trusted administrators.
  • Submitted messages may contain personal data. Choose a topic and server appropriate for your privacy requirements.

Screenshots

Installation

  1. Upload the axiom-contact-form-for-ntfy folder to /wp-content/plugins/, or install the ZIP through Plugins Add New Upload Plugin.
  2. Activate the plugin.
  3. Open Axiom Contact Form Settings and set the server, topic and authentication method.
  4. Use Send test notification to confirm delivery.
  5. Add [ntfy_contact_form] to a page, post, widget or block.

FAQ

Can I use a self-hosted ntfy server?

Yes. Enter the base URL, for example https://notify.example.com. Do not include a topic or a trailing slash.

Which topic name should I use?

Topics may contain letters, numbers, underscores and hyphens, 1–64 characters. Subscribe to the same topic in the ntfy app or web UI to receive the messages.

Why did the test fail with HTTP 403?

The topic is protected by your ntfy server’s access control. Switch authentication to an access token or username/password, and make sure that account may publish to the topic.

Can I change the colours?

Yes. Either leave Use the site colours enabled (text, borders and font inherit from the theme, and the accent is taken from the theme palette when available), or turn it off and set explicit colours. Shortcodes accept accent and use_site_colors overrides.

Does it store submissions in WordPress?

Yes. Each accepted submission is written to a dedicated database table (wp_ntcf_messages) before the ntfy request is made, then marked Sent or Failed with the error detail. Read them under Axiom Contact Form Messages. Deleting the plugin removes the table and its contents.

Where do I see why a notification failed?

Open Axiom Contact Form Messages; the Status column shows Failed with the reason (for example ntfy returned HTTP 403). The message itself is still stored, so you can act on it even though no push arrived.

Can I try it before installing it on my site?

Yes. WordPress Playground runs WordPress in the browser; the plugin is installed and activated, and the settings screen opens first. If the environment has outbound network access disabled, notifications cannot be delivered and every submission is stored with status Failed — the same view you get when a real server is unreachable. Nothing is sent anywhere until you enter a topic and submit or press Send test notification.

Reviews

There are no reviews for this plugin.

Contributors & Developers

“Axiom Contact Form for NTFY” is open source software. The following people have contributed to this plugin.

Contributors

Changelog

1.2.15

  • Changed: the Messages screen no longer prints a

1.2.14

  • Renamed to Axiom Contact Form for NTFY (slug axiom-contact-form-for-ntfy), so the plugin name identifies the author first and refers to ntfy as the integration it provides. The admin menu is now Axiom Contact Form.
  • The readme now states plainly that the plugin is an independent ntfy client with no affiliation to the ntfy project.
  • No functional changes: settings, the message log, the [ntfy_contact_form] shortcode and stored messages are untouched.

1.2.13

  • Improved: the “Send a test notification” button is shown only on the Connection tab, so it no longer looks like part of the Notification, Form or Appearance settings.

1.2.12

  • New: the title used when the subject field is filled in is editable on the Notification tab (default “Contact form: {subject}”). {subject} is replaced with the visitor’s subject.
  • Improved: the notification preview shows the tags before the title, matching how the ntfy app renders them.

1.2.11

  • New: the “Text back” reply is editable on the Notification tab. {name} and {site} are replaced with the visitor’s name and the site name when the notification is sent.

1.2.10

  • Branding: the plugin is published by Axiom Event Systems, with the plugin and author links pointing to axiomeventsystems.com.
  • Fix: the floating position and button text rows started hidden even when their option was already enabled.
  • Fix: the page URL is kept in a notification only when it points at this site, so a forged value cannot put someone else’s link in front of staff.
  • Fix: the preferred-contact value is accepted only when it matches one of the form’s options, and the rate limit and corner radius are clamped to the range the settings screen offers.
  • Fix: a form submitted with JavaScript had no status element to write into, so confirmations and errors never appeared on the page.
  • Fix: the rate limit counted every attempt, including invalid ones, so a few corrections could silently block the form for ten minutes. Only accepted messages count now.
  • Fix: a visitor without an account is no longer told their session expired when the browser does not keep the session between the page and the request.
  • Improved: uninstalling on multisite removes each site’s settings, log table and transients.

1.2.9

  • Fix: the button-only launcher always used the default blue instead of the selected accent and border radius. The inline custom properties now sit on the wrapper that holds both the launcher and the form, so the button, the form and the overlay share one palette.

1.2.8

  • New: “Notched” form style — labels sit on the top edge of each field, with centred heading and button.
  • New: button-only display. With it on, the shortcode renders just a configurable button (default “Contact Us”); pressing it dims and blurs the page and opens the form centred in an overlay. Closing the overlay, pressing Escape or clicking the backdrop returns the page to normal, and the overlay closes itself a few seconds after a successful send.
  • New: the live preview shows the notched style, the launcher and the overlay in place.
  • Fix: custom colours were dropped from the inline custom properties in 1.2.7.

1.2.7

  • New: ten form styles on the Appearance tab — classic, card, outlined, minimal, soft, pill, bold, inset, compact and editorial. Each one changes the frame, spacing and controls; the accent and custom colours still apply.
  • New: optional floating form, pinned to one of nine positions (three corners and three edges, each in three rows). Left off, the form stays wherever the shortcode was placed.
  • New: the live preview shows the selected style and, when floating is on, pins a scaled copy inside the preview panel at the chosen position.

1.2.6

  • Fix: North American numbers are stored without a plus sign, as 415-555-0132, so the “Text back” action dials the way the number is written domestically.
  • New: numbers typed with a leading plus keep only the plus and the digits after it, the global form of an RFC 3966 telephone URI.
  • New: the phone field formats as (415) 555-0132 while typing, and numbers that do not fit a known length are rejected on submit.

1.2.5

  • New: include or leave out the page URL and the site name in the message footer, from the Notification tab.
  • New: emoji generator on the Notification tab with the ntfy short codes; the preview shows tags the way ntfy renders them, emoji included.
  • New: when a visitor asks for a text message reply (or states no preference) and leaves a phone number, the notification carries a “Text back” action that opens the messaging app on the phone.

1.2.4

  • Improved: the live form preview is only shown on the Form and Appearance tabs, and those tabs that do not need it now use the full width.
  • New: the Notification tab shows a dark preview of the notification with its title, tags and an example submission, updating as you edit the title and tags.

1.2.3

  • Improved: the Connection tab shows only the fields the selected authentication mode uses — nothing for a public topic, the access token for token auth, and the username and password for basic auth — instead of all four rows at once.
  • The hidden rows are decided by PHP on load, so the correct fields appear even before the script runs, and existing values are kept when you switch modes.

1.2.2

  • Fix: each settings tab now renders its own fields. The tab map holds the short section name while the Settings API stores sections as ntcf_section_<name>, so the lookup missed every section and all four tabs showed the same empty page.

1.2.1

  • Fix: the settings tabs are now rendered and switched by PHP, so they load correctly with or without JavaScript.
  • Fix: status messages in the redirect URL are decoded once, because PHP already decodes query arguments.
  • Fix: the message log’s direct database call is annotated on the call itself, clearing the remaining plugin-check warnings.

1.2.0

  • New: the plugin has its own Axiom Contact Form for NTFY admin menu with Settings and Messages screens instead of being buried under Settings.
  • New: tabbed settings (Connection, Notification, Form, Appearance) with a live preview of the form that updates as you edit the copy, fields and colours.
  • New: the preview follows the appearance mode, switching between the theme palette accent and the custom colours without a page reload.

1.1.0

  • New: submission log in the database, viewable under Axiom Contact Form Messages with 10/20/30/50 per page.
  • New: delivery status (Sent / Failed) and the failure reason are stored with each message.
  • Submissions are logged before the ntfy request, so a timeout or rejected publish still leaves a record.
  • “Empty log” button to remove stored messages.

1.0.0

  • Initial release: shortcode contact form, ntfy publishing, token and basic authentication, theme colour support, spam trap, rate limiting, test notification.