Getting Started

Get AlgoBridge running with your Salesforce org and PostgreSQL database in under 15 minutes.

Prerequisites

Before you begin, make sure you have:

• A Salesforce org (Developer Edition, Sandbox, or Production) with API access enabled
• A PostgreSQL database (version 13+) that is network-accessible from the AlgoBridge server
• The hstore extension available on your PostgreSQL instance
• An AWS account with SSM Parameter Store access (for secure credential storage in production)

Local development: You can use a local PostgreSQL instance or a free Neon database. AWS SSM is only required in production.

Step 1: Create your account

1. Go to AlgoBridge and request access
2. Check your email for the verification link
3. Set your password and complete account setup

Step 2: Create a workspace

A workspace represents one sync connection — one Salesforce org paired with one PostgreSQL database.

1. After signing in, click Create Workspace
2. Give your workspace a name (e.g. production, staging)
3. Click Continue

Step 3: Connect your PostgreSQL database

AlgoBridge needs a connection string to your PostgreSQL database. It will install system tables and triggers automatically.

1. On the Connect Database step, enter your PostgreSQL connection URL:

postgresql://user:password@host:5432/dbname?sslmode=require

2. Click Test Connection to verify connectivity
3. If the test passes, click Save & Continue

What gets installed: AlgoBridge runs CREATE EXTENSION IF NOT EXISTS hstore and creates _trigger_log, _trigger_log_archive, and _abmeta tables on first connection.

Step 4: Connect your Salesforce org

1. On the Connect Salesforce step, click Authorize with Salesforce
2. You will be redirected to Salesforce’s OAuth login page
3. Sign in with a Salesforce user that has API Enabled permission and read/write access to the objects you want to sync
4. After authorization, you will be redirected back to AlgoBridge

Required Salesforce permissions: The connected user needs API Enabled in their profile, plus read access to any object you map, and write access for bidirectional sync.

Step 5: Create your first mapping

A mapping defines which Salesforce object maps to which PostgreSQL table, and the sync direction.

1. Go to Mappings → New Mapping
2. Select a Salesforce Object (e.g. Contact)
3. Choose a PostgreSQL table name (e.g. contact) — AlgoBridge will create it if it doesn’t exist
4. Set Sync Direction:
   • Salesforce → PostgreSQL — pull-only
   • PostgreSQL → Salesforce — push-only
   • Bidirectional — full two-way sync
5. Select the fields you want to sync
6. Click Save Mapping

AlgoBridge will immediately install the required triggers on your PostgreSQL table.

Columns added to your table

Every mapped table gets these system columns automatically:

Step 6: Monitor your sync

1. Go to Dashboard to see live sync stats
2. Go to Monitoring → Activity for a per-record sync history
3. Go to Health to check the status of your PostgreSQL connection, Salesforce connection, and sync engine

Understanding _ab_lastop values

Troubleshooting

Connection test fails: Check that your PostgreSQL host is reachable from the AlgoBridge server and that the user has CREATE privileges (needed to install system tables).

Salesforce auth fails: Ensure the Salesforce user has API Enabled in their profile. Check that your org’s Connected App allows the OAuth flow.

Records not syncing: Check the _ab_err column on failed rows. Common causes: field-level security preventing the SF user from writing a field, or a required field missing in the mapping.

Triggers not installed: Go to Health → Triggers to see trigger status per table. Click Reinstall to force re-installation.