Hooks
Every action and filter BooleanSMTP fires — 123 hooks (41 actions, 82 filters), generated from the plugin's own docblocks.
Every hook carries the plugin's prefix, in the WordPress style: boolean_smtp_<subject>_<event> for actions (something happened or is about to happen), boolean_smtp_<value> for filters (named for the value they carry — should_… when they decide whether something happens), boolean_smtp_<provider>_… for provider-specific seams, boolean_smtp_pro_… for the Pro add-on. A filter always returns the type it received. Dynamic names (like boolean_smtp_pro_webhook_{$provider}) list their possible names on the hook's own page.
Tiers
| Tier | Meaning | Hooks |
|---|---|---|
| A | Stable public API. Documented and tested; a rename or a change of arguments goes through a deprecation cycle kept for at least two minor releases. | 51 |
| B | Advanced seam. Documented; may change with a deprecation notice in the release notes. | 50 |
| C | Internal. Documented for support engineers — no stability promise; may change or disappear in any release. | 22 |
Areas
| Area | Hooks |
|---|---|
| Mail pipeline | 24 |
| Delivery lifecycle | 15 |
| Connections and OAuth | 21 |
| Provider transports | 17 |
| Notifications | 7 |
| Migration from other plugins | 6 |
| Admin UI and REST API | 7 |
| Log files | 3 |
| Framework | 1 |
| Internal (unstable) | 22 |
Next steps
- Hook Explorer — filter by kind, tier and area, and see the mail pipeline's hooks light up in the order they actually fire.
- Mail pipeline — the hooks every message passes through, in firing order.
- Delivery lifecycle — the three hooks most integrations start with:
boolean_smtp_email_sent,boolean_smtp_email_delivery_failed_final.