EP Connect
EP Connect sends webhook notifications from your PageMotor site to external services when things happen. Someone fills out a contact form, a booking is confirmed, a newsletter subscription lands — EP Connect fires a JSON POST to whatever URL you configured.
Published by ElmsPark Studio.
Overview
Section titled “Overview”Use EP Connect to plug PageMotor into the wider automation ecosystem:
- Zapier or Make to trigger multi-step automations.
- Slack or Discord to post alerts to a channel.
- Your own API for custom workflows.
- Google Sheets via Zapier or Apps Script to log every event.
Eleven built-in events, with hooks for other plugins to register their own. A delivery that fails is sent again on a back-off schedule, so an outage at the receiving end does not lose your data.
Built-in events
Section titled “Built-in events”| Event | Source plugin | Fired when |
|---|---|---|
| Email Form Submitted | EP Email | Someone submits a contact form. |
| Booking Made | EP Booking | A new booking is created. |
| Booking Confirmed | EP Booking | A booking moves to Confirmed status. |
| Booking Rescheduled | EP Booking | A booking moves to a new time. |
| Newsletter Subscription | EP Newsletter | Someone opts in to a newsletter list. |
| Comment Posted | EP Comments | A comment is submitted (before moderation). |
| Order Completed | EP Ecommerce | An order settles payment. |
| Review Submitted | EP Reviews | A product review is submitted. |
| Testimonial Submitted | EP Testimonials | A testimonial is submitted. |
| Content Published | PageMotor core | A page’s status changes to Published. |
| User Registered | PageMotor core | A new user account is created. |
Nine events (from EP Email, EP Booking, EP Newsletter, EP Comments, EP Ecommerce, EP Reviews and EP Testimonials) fire in real time via the emit() API. The remaining two (Content Published and User Registered) use database observation with a 30-second throttle, because PageMotor core doesn’t have an emit hook for them. Events still arrive, just with up to 30 seconds of latency.
Requirements
Section titled “Requirements”- PageMotor 0.11.5 or later
- EP Suite base class (bundled)
Installation
Section titled “Installation”ep-connect.zipcomes with an EP Suite licence — ElmsPark supplies it directly (see EP Suite plugins); after install it updates through your site’s Updates screen.- Upload via Plugins → Manage Plugins. Activate.
Setting up a webhook
Section titled “Setting up a webhook”- Open Plugin Settings → EP Connect.
- Click Add Webhook.
- Fill in:
- Name (optional): a label such as “New leads to the CRM”. It shows in the webhooks list, the delivery log and the Retries panel.
- Event: pick from the dropdown (the eleven built-in events plus any custom ones).
- URL: the endpoint to POST to.
- Secret: a string used to sign the payload via HMAC-SHA256. Your receiving endpoint uses this to verify the payload came from you and wasn’t tampered with. Generate a random 32-character string and paste it here and on the receiver.
- Only send these fields (optional): see Choosing the fields a webhook sends. Leave it blank to send everything.
- Click Save. A new webhook starts switched on; the switch on its row in the list pauses and resumes it.
- Click Send Test on the saved webhook row. A sample payload fires to your URL. Check the receiver got it.
Payload format
Section titled “Payload format”Every webhook POST body is JSON with this shape:
{ "event": "booking.confirmed", "timestamp": "2026-04-20T14:32:11+00:00", "site_url": "https://yoursite.com", "delivery_id": "9f2c4e1a7b3d48e6a0c5f1d2e3b4a596", "data": { "booking_id": 123, "service": "60-minute consultation", "customer_name": "Alice Smith", "...": "..." }}Headers:
Content-Type: application/jsonX-EP-Event: <event name>: for exampleuser.registered.X-EP-Timestamp: <unix seconds>: when the webhook was signed.X-EP-Delivery: <id>: the delivery ID, the same on every try of one delivery.X-EP-Attempt: <n>: which try this is, starting at 1.X-EP-Signature-V2: <hex>: HMAC-SHA256 of the timestamp, a full stop, then the body (timestamp + "." + body), using your webhook secret. Use this one.X-EP-Signature: <hex>: HMAC-SHA256 of the body alone, kept for older receivers. It does not protect against a captured request being sent again.
Both signatures are plain lowercase hex, with no sha256= prefix.
Choosing the fields a webhook sends
Section titled “Choosing the fields a webhook sends”By default a webhook sends every field of the event. To send only some, list them in Only send these fields, one per line or separated by commas:
emailname as full_namefields.companyemailsends that field as it is.name as full_namesendsnameunder a new name.fields.companyreaches a field inside another field (up to five levels deep).
A listed field the event does not carry is left out. A field EP Connect always strips (see below) cannot be added back this way. Up to 50 entries per webhook.
The list changes only what that webhook sends. Other plugins listening to EP Connect, such as EP Flows, still receive the whole event.
Retries
Section titled “Retries”If the receiver does not answer within 5 seconds, or answers HTTP 408, 425, 429 or any 5xx, EP Connect sends the delivery again. It waits 1 minute, then 5 minutes, 30 minutes, 2 hours, 6 hours and 24 hours: seven tries in all. Any other 3xx or 4xx answer is final, because sending the same request again would get the same refusal.
Every try carries exactly the same body and the same delivery_id. Only X-EP-Attempt and the signature change. If your receiver handled a delivery but answered too late, it sees the retry carrying an ID it already has, and should ignore it. Once a receiver accepts a delivery with a 2xx, EP Connect never sends it again.
Retries run when your site has traffic, in the same 30-second pass as the observed events, so a quiet site may send one a little later than scheduled.
The Retries panel in Settings lists the deliveries waiting to be sent again and the ones EP Connect gave up on, with Send again now and Discard on each row. Given-up deliveries are removed after 7 days.
Failure emails. After 5 failed tries in a row on one webhook, the site’s administrators get one email naming the webhook, the event, the receiving host and the last answer. It never includes the webhook’s full address (Slack and Zapier keep the key in it) or any of the data. At most one email per webhook per day; a delivery that gets through resets the count. Switch it off with the checkbox in the Retries panel.
Signature verification
Section titled “Signature verification”On your receiver, verify the signature before trusting the payload, and refuse old timestamps so a captured request cannot be replayed. Example in Node.js:
import crypto from 'node:crypto';
const body = rawRequestBody; // the raw bytes, not re-serialised JSONconst timestamp = request.headers['x-ep-timestamp'];const signature = request.headers['x-ep-signature-v2'];const expected = crypto .createHmac('sha256', process.env.EP_CONNECT_SECRET) .update(timestamp + '.' + body) .digest('hex');
const fresh = Math.abs(Date.now() / 1000 - Number(timestamp)) <= 300;if (!fresh || !signature || signature.length !== expected.length || !crypto.timingSafeEqual(Buffer.from(signature), Buffer.from(expected))) { return response.status(401).send('Invalid signature');}Without verification, anyone who guesses your webhook URL can fake payloads. Always verify. If the receiver is another PageMotor site, EP Flows does all of this for you, including refusing a repeated request.
Because a retry is signed afresh, a receiver that remembers signatures will not spot it as a repeat. Remember the X-EP-Delivery ID instead.
What sensitive fields are stripped
Section titled “What sensitive fields are stripped”Every payload has these left out, whichever plugin the event came from. A field is dropped when its name looks like:
- a password, password hash or salt;
- a token, key, secret, session or nonce (API keys, private keys, reset and activation codes);
- an IP address or browser details (user agent).
Very long text values are shortened to 2,000 characters.
Delivery log
Section titled “Delivery log”EP Connect keeps the last 200 delivery attempts across all webhooks, and the settings page shows the newest 50:
- Event, webhook name, destination URL (shortened), HTTP status code, time, and which try it was.
- Green for 2xx, grey
ERRwhen the receiver did not answer, red for any other code.
Older attempts are removed automatically.
From your AI assistant
Section titled “From your AI assistant”Since 1.3.0, an AI assistant connected to your site (Claude, ChatGPT or any MCP client) can set up and look after EP Connect for you. Ask in plain words, for example “send new enquiries to this Zapier hook and test it”.
It needs an administrator connection. Everything the settings page does is available:
| Action | What it does |
|---|---|
list-events | The events a webhook can be set for |
list-webhooks, get-webhook | Your webhooks, and one webhook in detail |
add-webhook | Add one: event, URL, and optionally a name, a signing secret and a field list |
update-webhook | Change only what you name; everything else stays |
set-webhook-active | Switch a webhook on or off |
delete-webhook | Remove a webhook |
test-webhook | Send a test now and report the receiver’s answer |
list-deliveries | The delivery log |
list-retries | Deliveries waiting to be sent again, and ones given up on |
retry-delivery, discard-delivery | Send one again now, or drop it |
get-overview | Today’s deliveries, retries and settings at a glance |
set-failure-emails | Turn the failure email on or off |
A signing secret can be set or replaced this way, but it is never shown back. The data inside a waiting delivery is never shown either.
Your assistant finds these itself. If it asks, they belong to EP_Connect and are reached through call-action.
Performance
Section titled “Performance”- Webhooks are sent at the very end of the request, after your page has been built. Several webhooks go out in parallel, and each waits at most 5 seconds for an answer, so a slow receiver costs one wait, not one per webhook.
- 30-second observation throttle for DB-observed events so this plugin never becomes the performance bottleneck on a busy site.
Registering custom events from another plugin
Section titled “Registering custom events from another plugin”Any plugin can add an event to the dropdown by calling:
EP_Connect::register_event('my_plugin.something_happened', [ 'label' => 'My custom event', 'plugin' => 'My Plugin',]);Then emit it when the thing happens:
EP_Connect::emit('my_plugin.something_happened', [ 'field' => 'value', 'another' => 42,]);Your event appears in the webhook dropdown and fires through the same signing and delivery pipeline as built-in events.
Troubleshooting
Section titled “Troubleshooting”“Send Test succeeds but real events don’t fire”
Section titled ““Send Test succeeds but real events don’t fire””Check the webhook is switched on (the switch on its row in the webhooks list). Check the event you are expecting actually happened — look at the source plugin’s own logs.
“Receiver gets the payload but signature verification fails”
Section titled ““Receiver gets the payload but signature verification fails””The secret on your receiver must match the secret saved on the webhook, byte for byte, including any trailing whitespace. EP Connect stores secrets encrypted and never shows them again, so if you are not sure, type a new secret into the webhook and paste the same value into your receiver. Also check the receiver signs the raw request body exactly as it arrived, and compares plain hex with no sha256= prefix.
“Delivery log shows HTTP 403 from my receiver”
Section titled ““Delivery log shows HTTP 403 from my receiver””Your receiver is rejecting the request. Common cause: the receiver expects a specific authentication header. EP Connect sends the headers listed under Headers above and nothing else. If the receiver needs anything else, it needs to be a proxy or adapter, not a direct EP Connect target.
“Delivery log shows 301, 302 or 307”
Section titled ““Delivery log shows 301, 302 or 307””The receiver answered with a redirect. EP Connect does not follow redirects, so nothing reached the final address. Put the final URL (the one the redirect points to) into the webhook instead.
“Delivery log shows ERR for every event”
Section titled ““Delivery log shows ERR for every event””The receiver is slow or unreachable. EP Connect waits up to 5 seconds, then retries on the schedule under Retries. If your receiver is legitimately slow, use a faster endpoint (a Zapier webhook that queues, rather than a slow direct integration).
“Events I expect to fire aren’t in the delivery log”
Section titled ““Events I expect to fire aren’t in the delivery log””Some events come from plugins that must be active and configured. For example, “Booking Confirmed” only fires if EP Booking is installed and a booking was actually confirmed. Check the source plugin is doing its bit.
Feedback and corrections
Section titled “Feedback and corrections”For a quick question about this plugin, EP Support inside your admin is the fastest option. The chat widget sits on every EP plugin settings page and knows which one you’re on, with starter questions and links preloaded for that exact screen.
For anything bigger — a bug report, a feature request, or a “how do I…” that needs a real reply — open a ticket at help.elmspark.com. A real person, helped by AI, writes the reply. Usually within a few hours. Tickets don’t disappear into the void.
Changelog
Section titled “Changelog”- Set up EP Connect from your AI assistant. Claude, ChatGPT or any assistant connected to your site can now do everything the EP Connect settings page does: list the events, add a webhook, change or rename one, switch it on or off, send a test, read the delivery log, see what is waiting to be sent again, send a delivery again or discard it, and turn the failure email on or off. Until now an assistant could install EP Connect but could not set up a single webhook.
- Secrets stay secret. A webhook’s signing secret can be set or replaced by an assistant, but it is never shown back, not even to an administrator. The data inside a waiting delivery is never shown either.
- Administrators only. Every one of these actions needs an administrator connection to your site.
- “Send again now” no longer delays other deliveries that happened to be going out at the same moment.
- Tidier on PHP 8.5: no more deprecation notice in the log for each delivery.
- Failed webhooks are sent again. If the receiving service is down, slow or busy (no answer within 5 seconds, or HTTP 408, 425, 429 or any 5xx), EP Connect tries again after 1 minute, 5 minutes, 30 minutes, 2 hours, 6 hours and 24 hours before giving up. Until now each webhook was sent once, so an order or a lead sent while your CRM was down was lost.
- A retry is easy to tell from a new order. Each retry is clearly marked, so your receiver can recognise it and ignore a duplicate. See the EP Connect documentation for details. Once a receiver accepts a delivery, EP Connect never sends it again.
- New Retries panel. Settings now lists the deliveries waiting to be sent again, and the ones EP Connect gave up on, with Send again now and Discard buttons. Given-up deliveries stay for 7 days.
- An email when a webhook keeps failing. After 5 failed tries in a row on one webhook, the site’s administrators get one email naming the webhook, the receiving service and the last answer, at most once a day per webhook. It never includes the webhook’s full address or any of the data. Switch it off in Settings.
- Four more events. You can now set webhooks for Booking Made and Booking Rescheduled (EP Booking), Review Submitted (EP Reviews) and Testimonial Submitted (EP Testimonials).
- Webhook names. Give each webhook a name, such as “New leads to the CRM”. It shows in the webhooks list, the delivery log and the Retries panel.
- Choose the fields a webhook sends. List the fields to send, rename them (“name as full_name”) and reach fields inside fields (“fields.email”). Leave it blank to send everything, as before. A field EP Connect always leaves out (passwords, tokens, IP addresses) cannot be added back this way.
- Faster when several webhooks fire together. Deliveries now go out in parallel instead of one after another.
- Needs PageMotor 0.11.5. Nothing else to do after updating; see Retries for how it works.
- EP Connect no longer stops working when a plugin it watches is missing. On a site where EP Connect watches for something whose plugin is not installed, or was removed (EP Comments, for example), EP Connect could fail to load on some page views, about once every 30 seconds. Events on those page views were lost, and an error was written to your log each time. It now skips what it cannot read and carries on.
- This release also includes 1.1.5 and 1.1.6 (below), not previously released.
- New webhooks start from now. When you add the first webhook for an event, EP Connect no longer sends a burst of old records (existing users, past bookings, old orders); it starts with the next new one.
- Webhook settings are admin-only on every PageMotor version, and the security check on them is stricter.
- Nothing to do after updating.
- Security fix: webhook secret keys are stored encrypted and never shown again. When you edit a webhook, leave the secret blank to keep it, type a new one to replace it, or tick “Remove the saved secret”. Existing secrets are encrypted the first time the site loads after updating.
- Security: webhooks now carry less personal data.
- Signed webhooks now include a timestamp, so receivers (including EP Flows) can refuse a replayed request. The original signature header is still sent.
- No more duplicate deliveries when two visitors load pages at the same moment.
- Webhooks to an address that answers with a redirect are now logged with that code, and nothing more is sent.
- Settings language menu. The language menu in this plugin’s settings now lists only the languages it is actually translated into, plus English, so you can no longer pick a language that changes nothing.
- Danish. Adds a Danish translation.
- “Order Completed” now fires only for orders that are really paid. Before, every new EP Ecommerce order was announced as completed the moment it was created, while it was still waiting for payment. Webhooks and EP Flows automations for “Order Completed” could run for an order that was never paid, or that failed or expired.
- An order is now announced once it completes, even when EP Connect was not running on the request that completed it. It is announced once. An order that was completed and then refunded is still announced once, because it did complete.
- An order left waiting for more than 14 days stops holding back the check.
- Trims order detail that does not need to be sent from what EP Connect delivers.
- “Booking Confirmed” now fires only for confirmed bookings. Before, every new EP Booking booking was announced as confirmed the moment it was made, including bookings still waiting for payment or for your approval. Webhooks and EP Flows automations for “Booking Confirmed” could then run for a booking that was never paid.
- A booking is now announced when it becomes confirmed, even when that happens later (the payment arrives, or you approve it). It is announced once.
- A booking left waiting for more than 14 days stops holding back the check, so an abandoned booking cannot delay the others.
- A missing table for one of the watched plugins now skips just that check instead of risking an error on the page.
- Fixes “Your session has expired. Please reload to ensure your security.” on PageMotor 0.11. The message appeared on this plugin’s admin screens even though you were signed in perfectly normally, and whatever you were doing failed to save.
- Nothing was wrong with your session. PageMotor 0.11 started handling part of the security check that this plugin was already handling itself, and the two together made every save look invalid. The plugin now checks whether PageMotor has already done it.
- Visitors who were not signed in were never affected, on any version.
- There is nothing to reconfigure, and nothing else changed.