AlgoBridge Documentation

AlgoBridge is a production-grade, bidirectional Salesforce ↔ PostgreSQL sync engine. It implements the same trigger names, column conventions, and state machine used by the de facto standard for Salesforce sync — running entirely on your own infrastructure.

What it does

Sync Salesforce → PostgreSQL: Pull Salesforce object changes into your database automatically every 10 seconds
Sync PostgreSQL → Salesforce: Write changes from your database back to Salesforce via SOAP or Bulk API
Trigger-based CDC: PostgreSQL triggers capture every INSERT, UPDATE, and DELETE into _trigger_log as hstore diffs
State machine: Every record transitions through NEW → PENDING → SUCCESS | FAILED — no silent drops
31-day archive: Processed log rows move to _trigger_log_archive and are purged after 31 days

Key technical facts

Property	Value
Sync interval	Fixed 10 seconds
PG → SF (small batch)	SOAP API (≤ 200 records)
PG → SF (large batch)	Bulk API v2 (> 200 records)
Change tracking format	hstore (not JSONB)
SF ID column type	`VARCHAR(18)`
Archive retention	31 days

Guides

Getting Started — Connect your Salesforce org and PostgreSQL database and run your first sync
Architecture — How the sync engine works internally: CDC, state machine, API thresholds
API Reference — REST API endpoints for programmatic access

System tables installed per client database

When you connect a PostgreSQL database, AlgoBridge automatically installs:

_trigger_log          -- live CDC queue
_trigger_log_archive  -- 31-day audit trail
_abmeta               -- schema metadata

These tables, plus the trigger functions and trigger names, match the de facto Salesforce sync specification exactly. Existing tooling that introspects your schema (dbt, Metabase, BI tools) will work without modification.