Forge Stream#

Forge Stream is real-time, bidirectional sync. It captures changes out of your connected systems, routes them through pipelines you define, and writes them into other systems — exactly once.

How it works#

1. Capture. A source connector emits a change event for every insert, update, or delete (Salesforce Change Data Capture, HubSpot/Zendesk/JIRA polling on a cursor, Stripe's event feed).
2. Match. The trigger engine evaluates each event against your pipelines' conditions — including delta logic like "changed to Closed Won".
3. Route. A matching pipeline hydrates the record and dispatches its mapped fields to the destination.

It's exactly-once: events are deduplicated on their coordinates, so a redelivery or a restart never double-applies.

Watching it live#

• Activity is the live event feed — a KPI strip, a sparkline, and a streaming list of changes as they arrive over a WebSocket.
• Objects is a per-entity grid with a record drawer.
• Runs is every pipeline firing, newest first, with a detailed run view.

When writes fail#

A destination write that fails is dead-lettered, not lost. The DLQ screen shows each failure classified by kind — a config problem (bad mapping), a data problem, or a transient one — and lets you retry it the right way: a config failure redispatches the stored snapshot without a wasteful refetch; a data or transient failure re-hydrates fresh.

Note: Conditions Stream used to swallow — a suppressed re-trigger, a stale approval — now surface in Alerts.