SignalPress connects WordPress to logging, analytics, notification, and automation services through integrations. Each integration is a destination where you can send a signal — for example, send a signal to Slack, send a signal to Email, or send a signal to PostHog.
This guide explains how integrations appear in the admin, how activation differs from delivery, and how free and Pro services fit together. Start with Setup & Activating SignalPress if you have not installed the plugin yet.
Where to find integrations
Open SignalPress → Integrations to browse every available service. The page groups integrations by category:
- Built-in — Local, Email, RequestBin (free)
- Analytics & Product — GA4, PostHog, Mixpanel (Pro)
- Notifications — Slack, Teams, Discord, Pushover (Pro)
- Logs & Observability — Better Stack, Sentry, Datadog, and others (Pro)
- Automation — Webhooks, Zapier, Google Sheets, Excel Online (Pro)
You can also filter by Free or Premium, search by name, and narrow by category using the toolbar on the Integrations page.
Premium integrations (21 total)
Free (3): Local, Email, RequestBin
Pro (18): PostHog, GA4, Mixpanel, Better Stack, Pushover, Webhooks, Slack, Discord, Teams, Zapier, Google Sheets, Excel Online, Sentry, Datadog, Honeycomb, Axiom, New Relic, Loki
PostHog and Mixpanel appear under both Analytics & Product and Logs & Observability because they support analytics and event logging use cases.
Webhooks requires Plus or Pro: free sites cannot use webhooks; Plus allows one HTTPS endpoint; Pro allows unlimited endpoints. See Free vs SignalPress Pro.
When you call sp_capture() with a services array, use the exact IDs from Service Targeting.
Integration setup guides
Each bundled service has a hub setup guide. The in-plugin Help tab uses the same content.
| Category | Guides |
|---|---|
| Built-in (free) | Local, Email, RequestBin |
| Analytics & product | PostHog, GA4, Mixpanel |
| Notifications | Slack, Discord, Microsoft Teams, Pushover |
| Logs & observability | Better Stack, Sentry, Datadog, Honeycomb, Axiom, New Relic, Grafana Loki |
| Automation | Webhooks, Zapier, Google Sheets, Excel Online |
Active vs inactive integrations
An active integration has its own admin submenu item under SignalPress. An inactive integration stays on the Integrations page with its settings preserved, but it does not appear in the submenu and cannot receive signals.
- Click Activate on a card to turn an integration on.
- Click Deactivate to hide it without deleting saved credentials.
Local is active by default when you install SignalPress.
Integration activation vs service enabled
These two controls are easy to confuse:
| Control | What it does |
|---|---|
| Activate integration | Shows the service in the admin menu and makes it eligible for delivery |
| Enable service (Settings tab) | Allows the service to send or store events right now |
You can keep an integration active but disabled when you want to pause delivery without losing API keys, webhook URLs, or routing rules.
Free, Plus, and Pro services
The free plugin includes three working integrations:
- Local — store events in WordPress
- Email — send alert messages
- RequestBin — inspect payloads during development
Premium integrations require SignalPress Pro and a valid license. Before Pro is installed and licensed, premium cards appear on the Integrations page with upgrade links. After licensing, those cards become fully configurable.
License tiers unlock additional features across integrations (not just more destinations):
- Tier 1 (Plus) — extended delivery logs, advanced routing, system logs, event transformation hooks
- Tier 2 (Pro) — request rules, durable delivery queue, role permissions, Pro debugging, email message templates, and more
See Free vs SignalPress Pro for a fuller tier breakdown.
Each integration page has four tabs
When an integration is active, open it from the SignalPress submenu:
| Tab | Purpose |
|---|---|
| Settings | Credentials, enable/disable, connection test |
| Routing | Signal filters for this service only — Advanced Event Routing |
| Logs | Delivery history — Connection Tests and Delivery Log |
| Help | Service-specific setup guide bundled with the plugin |
Use the Help tab for credential walkthroughs and copyable examples. The ? icons on Settings fields link directly to the relevant Help section.
Choosing your first integrations
A practical order for new sites:
- Local — confirm events are being captured (no external account needed)
- Email or a notification service — get alerts when something fails
- One analytics or log destination — PostHog, Better Stack, or similar for production visibility
You do not need to activate every integration. Enable only the destinations your project actually uses.
After Local works, send a real signal with Capturing Events with sp_capture().
What to read next
- Your First Connection Test — send a test signal and read the delivery log
- Free vs SignalPress Pro — licensing and tier features
- Setup & Activating SignalPress — install and license walkthrough
- Service Targeting — exact service IDs for
sp_capture() - Permissions and Access — who can configure integrations on Tier 2 sites
- Extending SignalPress — bundled services, custom plugins, and hooks