Wake-on-LAN
Wake a device through one validated broadcast address and MAC address. The route returns a status code instead of raw firewall output.
Reachability Checks
Ask pfSense to ping one validated IP address with bounded attempts. Scripts get a predictable result without direct shell access.
System Information
Read the operating system, release, and architecture through a fixed response schema designed for safe automation.
Scoped Personal Tokens
Give each client only the capability it needs. SQLite stores hashes rather than recoverable token values, independently from browser administration.
Operations Console
Sign in with a local administrator account to manage client tokens, redacted activity, write-only pfSense settings, and alerts when pfSense stops answering.
Container Operations
Run a slim Debian controller with health checks, encrypted state, and s6 process supervision.
API at a Glance
4
Action routes
3
Token scopes
1
Target firewall
0
Arbitrary commands
A small API on purpose.
pfSense Actions exposes the few operations that are useful in unattended workflows. Broader administration stays in pfSense, where it belongs.
From the Blog
Release notes, upgrade guides, and notes on automating pfSense safely.
Introducing pfSense Actions 2.0.0: A Token for Every Script
pfSense Actions 2.0.0 gives every script its own scoped token to wake devices, ping addresses, or read pfSense details, plus a console to manage them.