eMabler Pulse
Overview
Pulse is the automation product inside eMabler Connect. It lets a CPO operator turn the events flowing through the platform — charger status updates, time-based conditions, usage thresholds — into rules that the platform acts on automatically. When a charge point reports an error, when a socket has been stuck in a state too long, or when a connector is being plugged in more often than expected, Pulse can notify the team, disable a faulty connector, or remotely reboot a charge point — without anyone watching the dashboard.
Pulse lives in Connect under the Sense area, alongside the rest of the platform's intelligence and visibility tooling.
The problem Pulse solves
A growing charging network produces a steady stream of OCPP status notifications. Most fault patterns are not new — the same handful of recurring conditions drive the majority of operator effort. Without automation, every one of them waits for a human to triage and act, which means failed sessions, lost revenue, and avoidable support load.
Pulse closes the loop. Define the rule once, and the platform handles the recurring case every time it appears.
How Pulse works
Every automation in Pulse is built from three parts:
Trigger — the event that starts the automation
Action — what Pulse does when the trigger fires
Rule — one trigger combined with one or more actions, scoped to specific sites or charge points
A typical rule reads: When a charge point at site X reports status Error, then send a Slack message to the maintenance channel and reboot the charge point.
Each automation has its own settings (fire policy, active period, home site for access) and its own Activity timeline so operators can see exactly what the platform did, when, and why.
Available triggers
Trigger | What it means | Typical use case |
|---|---|---|
Charger sends status update | Fires when a charge point or connector reports an OCPP status change. Can be filtered by status value (Available, Error, Offline, Info, Charging, Suspended car, Suspended charger, Preparing) and an optional message match. | Notify operations the moment a charge point goes into |
Socket has status after time | Fires when a connector remains in a specified status past a defined start time. | Catch connectors stuck in |
Plug in count threshold exceeded | Fires when a connector's plug-in count crosses a defined threshold. | Schedule preventive inspection for high-utilisation connectors before they degrade. |
All triggers can be scoped to specific sites and chargers
Available actions
Action | What it does | Notes |
|---|---|---|
Send Slack message | Posts a message to a configured Slack channel with the event context. | Available for all triggers. |
Send email | Sends an email notification with the event context. | Available for all triggers. |
Set sockets as inactive | Changes the targeted connectors to | Currently not available for the Charger sends status update trigger. |
Reboot chargers | Issues a remote reset to the targeted charge points (OCPP | Currently not available for the Charger sends status update trigger. |
A single rule can chain multiple actions — for example, send a Slack alert and disable the affected sockets in the same automation.
Automation settings
Each automation is configured with:
Fire policy — controls how often the automation runs against the same target. Options: Always, Once, Once per charger, Once per socket.
Active until — an optional end date after which the automation stops firing. Leave empty for an open-ended automation.
Home site — controls who in the customer's organisation can see and manage the automation. Automations without a home site are visible to all operators with access.
Automations are created in an inactive state, reviewed, and explicitly activated by the operator — there is no risk of a half-configured rule firing in production.
Visibility and activity
Pulse provides two layers of visibility into what the platform has done on the operator's behalf:
Automations activity — a network-wide timeline of every action Pulse has executed, accessible from the Pulse area in Connect. Useful for audit, troubleshooting, and demonstrating the value of automation to internal stakeholders.
Per-automation Activity tab — each automation has its own execution history showing the triggering events and the actions taken, so an operator can see exactly how a specific rule has behaved over time.
Operators do not need to keep a dashboard open — Pulse handles execution and surfaces results through the configured notification channels.
Use cases
Large enterprise CPO
A multi-site network cannot scale operations linearly with charge point count. Pulse absorbs the long tail of repetitive faults — the same recurring Error codes that drive most of the recoverable downtime — by combining the Charger sends status update trigger with Slack notifications, scoped per region. Stuck-session detection (sockets remaining in Charging or Preparing past a reasonable duration) is handled by the Socket has status after time trigger paired with Set sockets as inactive, keeping faulty connectors out of the driver's path.
Energy utility
For an energy company running EV charging alongside grid-aware services, the underlying chargers must stay healthy for the smart-charging value proposition to land. Pulse watches for Error and Offline status updates on chargers participating in DLM and spot-price optimisation, alerting the team and disabling unrecoverable connectors before they distort load assumptions.
Parking operator
When charging is part of a driver-facing parking app, the connector experience is the product. Pulse uses the Plug in count threshold exceeded trigger to flag high-cycle connectors for preventive inspection, and the Socket has status after time trigger to catch sockets stuck in Preparing so they are taken out of rotation before a driver arrives at a non-working bay.
Integrations
Pulse is built on the eMabler Connect platform and uses the same surfaces:
OCPP 1.6 and OCPP 2.0.1 — Pulse acts on charge points using the standard protocol commands available in Connect.
Slack — supported notification channel; operators configure the destination channel per action.
Email — supported notification channel for individual or distribution-list recipients.
eMabler API V2 — automations and activity are part of the Connect data model and are accessible to customers integrating Connect into their own operations tooling.
Push API and webhooks — Pulse-driven events can be delivered into customer-hosted message queues or HTTP endpoints alongside other Connect platform events.
Because Pulse runs on top of Connect rather than as a parallel stack, customers using any of the existing Connect integrations get Pulse activity surfaced in the systems they already operate from.
What's next
Pulse is on a path toward what eMabler describes as CPOLess operations — a charging network that runs itself for the predictable cases and only involves humans for genuinely novel issues. Areas of active development include:
Additional triggers and actions covering more of the recurring operational patterns customers run into.
Broader coverage of which actions are available for which triggers, so rules can be expressed as freely as operators need them.
AI-assisted diagnostics that cross-reference charger errors with vendor documentation to recommend the most likely fix when an action cannot resolve the issue automatically.
Tighter integration with Data Insights, so anomalies in usage and energy patterns can become Pulse triggers.
Getting started
Pulse is enabled per customer account. Existing Connect customers can request activation through their account contact or the support portal. Once enabled, Pulse appears in the Connect navigation under Sense, and operators can begin defining automations immediately.
For a guided walkthrough of Pulse against your own network, request a demo at emabler.com/book-your-demo.