← Back to all sparks
E

Encharge

MARKETING
Velocity0.0

Encharge grinds through reliability and security fixes, with an MCP teased next

email-automationreliabilitysecurityintegrationshubspotmcp
Current state
Encharge is in a steady maintenance-and-hardening phase. The two most recent monthly updates are dominated by fixes — multi-select fields across forms and segments, HubSpot date sync, sending reliability — plus security work: signups now require email confirmation, form notifications only send from verified senders, and stronger bot and spam protection. It's an email-automation product tightening its foundations rather than expanding surface area.
Where it's heading
The arc is deliberate stability: quarter after quarter of email-editor, forms, flows, and integration fixes, with incremental additions like a marketing-consent field and smoother sending autoscaling. The one forward signal is an Encharge MCP now in testing — the first hint of an agent-facing layer on top of the existing automation engine — alongside a Shopify connector app in progress.
Prediction
The Encharge MCP is the most likely next headline; expect it to ship out of testing, with the in-progress Shopify connector close behind. Otherwise the cadence points to continued reliability and integration work.

Recent moves

  1. 1mo ago

    May–June: multi-select fixes, signup security hardening, HubSpot sync

    The May–June update centers on making multi-select work across forms and segments, hardening signups (mandatory email confirmation, verified-sender notifications, bot protection), and cleaning up HubSpot date sync. It also teases that an Encharge MCP is now in testing.

  2. 2mo ago

    April: reliability fixes, better bot detection, form consent field

    April's update is reliability-focused — segment, form, email-content, and Salesforce-sync fixes — with improved bot detection, caching, and monitoring, plus a new marketing-consent field for forms.

  3. 2mo ago

    April update (duplicate feed entry)

    A duplicate of the April update, re-emitted by the feed with a date stamp appended to the title; no new content beyond the canonical April post.

  4. 2mo ago

    April update (duplicate feed entry)

    Another duplicate of the April update, with whitespace stripped and a date stamp appended; same content as the canonical April post.

  5. 3mo ago

    Year-start stability push across editor, forms, integrations

    A large year-start stability release: dozens of fixes across the email editor, forms, and integrations, plus scale and performance work (more DB capacity, a new IP pool) and a Shopify connector in progress.

  6. 3mo ago

    What we've been up to since the beginning of the year 2026

    Third copy of the same year-to-date recap — pure feed-side duplication.