Skip to content
Business productivity ⇄ CRM

Agiloft to Salesforce integration — real-time, two-way sync

Keep Agiloft and Salesforce in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Agiloft and Salesforce

Sync what happens in Agiloft with the customer records in Salesforce, in real time and in both directions.

The CRM is supposed to be the record of every customer relationship, but customer-relevant information also accumulates in the other tools a team runs. Whatever Agiloft holds or produces that touches a customer, whether conversations, payments, replies, enriched data, or notes, the CRM only benefits if it arrives without someone copying it over.

Stacksync connects Custom tables, Contracts, Companies, People in Agiloft to Tasks and Events, Products and Price Books, Custom Objects, Accounts in Salesforce with bi-directional, real-time sync. Activity and record changes in Agiloft update the matching contact or account in Salesforce, and CRM data flows the other way wherever Agiloft can store and use it.

Common use cases

  • 01 Write contract or company records into Agiloft when a deal closes in the CRM to kick off downstream legal and procurement workflows.
  • 02 Two-way sync Contracts between Agiloft and an ERP or warehouse so value, renewal dates, and status stay current without manual re-keying.
  • 03 Consolidate multiple Salesforce orgs into a single database for cross-org reporting after an acquisition.
  • 04 Sync Accounts, Contacts, and Opportunities bi-directionally with Postgres so engineering teams read and write CRM data with plain SQL.

Common sync patterns

Where Agiloft processes payments

Charges, refunds, and subscription changes appear on the account in Salesforce, so revenue context lives with the relationship.

Where Agiloft can store CRM context: fields kept current

Owner, lifecycle stage, or account details from Salesforce sync into Agiloft, so people working there have the context without switching tools.

Where Agiloft supplies contact or company data

Enriched fields land directly on records in Salesforce, and refreshes keep them from going stale.

What you can sync between Agiloft and Salesforce

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Agiloft objects Salesforce objects How this pairing syncs
People Parent table for individuals, split into Employees (internal users) and Contacts (external company contacts); synced to map signers, approvers, and account owners to CRM or HR records. Tasks and Events Activity records; usually read-only in syncs to feed activity reporting. People is specific to Agiloft and Tasks and Events to Salesforce — each maps to any object or custom field on the other side.
Attachments File records holding the executed contract PDFs and supporting documents linked to a contract; read to pull signed files out, or written to push generated documents in. Products and Price Books Catalog and pricing data; commonly mastered in an ERP and written into Salesforce. Attachments is specific to Agiloft and Products and Price Books to Salesforce — each maps to any object or custom field on the other side.
Approvals Per-record approval instances generated from Approval Templates and Workflows; read to report approval status and cycle time, or written to trigger and record decisions. Custom Objects Org-specific tables with the __c suffix; discoverable via describe metadata so field mappings can be generated. Approvals is specific to Agiloft and Custom Objects to Salesforce — each maps to any object or custom field on the other side.
Tasks Assigned action items with owners, due dates, and states tied to contracts or projects; synced two-way to surface Agiloft work inside a PM or operations system. Accounts Company records that anchor most syncs; typically mapped to customer tables in a database or ERP. Tasks is specific to Agiloft and Accounts to Salesforce — each maps to any object or custom field on the other side.
Clause Library Reusable, approved contract clauses with metadata and categories; read to feed clause content into other systems or reporting, or maintained from an external source of truth. Contacts People linked to Accounts; synced two-way with marketing, support, and warehouse person records. Clause Library is specific to Agiloft and Contacts to Salesforce — each maps to any object or custom field on the other side.
Custom tables Agiloft is a no-code platform, so any customer-built table (NDAs, SOWs, vendor risk, renewals) exposes the same REST and SOAP CRUD and syncs like the standard CLM tables. Leads Unqualified prospects; often written into Salesforce from enrichment or product-signup pipelines. Custom tables is specific to Agiloft and Leads to Salesforce — each maps to any object or custom field on the other side.

How changes propagate between Agiloft and Salesforce

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Agiloft Salesforce Sub-second propagation

DetectionAgiloft notifies Stacksync of record changes through webhook events. Native webhook subscriptions (POST /ewws/webhooks) fire on record create, edit, or delete after a GET handshake verifies the callback URL.

DeliveryEach detected change is written to Salesforce through its API, with automatic retries and rate-limit backoff.

Salesforce Agiloft Sub-second propagation

DetectionChanges in Salesforce are captured at the source via change data capture — no polling loop against its API. Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting).

DeliveryEach detected change is written to Agiloft through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Agiloft: Agiloft publishes no fixed per-minute REST quota; throughput is instance-specific and bounded by license seats (Assigned/Floating Power User) and concurrent API sessions. Each SOAP/EWS call runs in its own transaction, and REST logins issue a session token meant to be reused rather than re-authenticated per call.
  • Salesforce: Daily API request allocations vary by edition and license count.
What ships with Agiloft ⇄ Salesforce

Connect Agiloft and Salesforce for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Agiloft–Salesforce connection.

Real-time

Two-way sync

Changes in Agiloft or Salesforce instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Agiloft or Salesforce data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Agiloft or Salesforce record.

Observability

Monitoring

Track your Agiloft ⇄ Salesforce sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Agiloft and Salesforce.

How the Agiloft and Salesforce connectors work

Agiloft

Integration surface
REST API (/ewws/rest/{kb}) and SOAP/EWS v2 web services (EWWSv2Service WSDL), plus a native Webhooks subscription API
Authentication
OAuth 2.0 via OAuth2 Client Setup - Authorization Code with PKCE for user-delegated apps and Client Credentials for machine-to-machine; also JWT tokens or Basic Auth with a session token from POST /ewws/rest/{kb}/login
Change detection
Native webhook subscriptions (POST /ewws/webhooks) fire on record create, edit, or delete after a GET handshake verifies the callback URL; otherwise poll each table by its Date Updated / modified-time fields. Agiloft has no database change-data-capture log.
Capabilities
read · write · webhooks
Rate limits
Agiloft publishes no fixed per-minute REST quota; throughput is instance-specific and bounded by license seats (Assigned/Floating Power User) and concurrent API sessions. Each SOAP/EWS call runs in its own transaction, and REST logins issue a session token meant to be reused rather than re-authenticated per call.

Salesforce

Integration surface
REST, SOAP, and Bulk APIs
Authentication
OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode
Change detection
Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting)
Capabilities
read · write · CDC
Rate limits
Daily API request allocations vary by edition and license count.
Salesforce setup guide
How it works

How to connect Agiloft to Salesforce — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Agiloft and Salesforce with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Agiloft connected
    Salesforce connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Agiloft and Salesforce objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Agiloft ⇄ Salesforce
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Agiloft Salesforce
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Agiloft and Salesforce integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 438 integrations available for Agiloft and Salesforce.

Popular · 5 of 438
All Agiloft integrations All Salesforce integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own