Main Header

Zapier for SignalPress

Updated on July 30, 2026

Use Settings to configure delivery, Routing to select events, Logs to inspect delivery history, and Help for this guide. Routing requires Tier 1; Tier 2 adds request rules. Log visibility, payload previews, and deletion can be delegated separately with Tier 2 role permissions.

Send signals to Zapier to trigger automations from WordPress activity.

Zapier is a premium SignalPress service. The active SignalPress license must include service_zapier or *. Zapier currently restricts Webhooks by Zapier triggers to its paid Professional, Team, and Enterprise plans.

Hub service ID: zapier. Index: Integrations Overview. Target from PHP: Service Targeting.

Get the Catch Hook URL

  1. Sign in to Zapier and create a new Zap.
  2. Select Webhooks by Zapier as the trigger app. Dismiss the API by Zapier suggestion if Zapier displays it; API by Zapier is not the trigger used here.
  3. Choose Catch Hook as the trigger event and continue.
  4. Leave Pick Off A Child Key blank so Zapier receives the complete SignalPress envelope.
  5. Copy the generated URL beginning with https://hooks.zapier.com/hooks/catch/.
  6. Activate Zapier under SignalPress → Integrations.
  7. Paste the complete URL into Catch Hook URL, enable Zapier, and save.

Treat the Catch Hook URL as a password. Anyone who has it can trigger the Zap. Do not publish it, commit it to source control, or place it in browser JavaScript.

  • [Zapier's Catch Hook instructions](https://help.zapier.com/hc/en-us/articles/8496288690317-Trigger-Zap-workflows-from-webhooks)

Test and map the sample

  1. Keep the Zap editor open on its trigger-test step.
  2. In SignalPress, click Send test signal.
  3. Return to Zapier and click Test trigger or Find new records.
  4. Select the signalpress_test sample.
  5. Map its fields into any Zapier action and publish the Zap.

The sample includes predictable fields such as event, project, environment, source, level, timestamp, data, context, and WordPress site metadata. Zapier may flatten nested JSON fields in its mapping UI.

Send a signal to Zapier

PHP

sp_capture(
	'customer_upgraded',
	[
		'customer_id' => 42,
		'plan'        => 'pro',
		'level'       => 'info',
	],
	[
		'source'   => 'billing',
		'services' => [ 'zapier' ],
	]
);

The signalpress/zapier/payload filter can modify the final JSON envelope with Tier 1 or higher.

Troubleshooting

  • A successful SignalPress test means Zapier accepted the sample. It does not mean the Zap has been published or that later actions succeeded.
  • If no sample appears, send another test while the Zap editor is listening, then run Test trigger again.
  • A 404 usually means the Zap was deleted, disabled, or its Catch Hook is no longer active.
  • A 410 means Zapier no longer accepts events at that hook URL. Create or copy the current URL again.
  • A 429 indicates Zapier throttling. Reduce bursts or use the Tier 2 SignalPress delivery queue to smooth background delivery.