Skip to content
Marketing ⇄ ERP

Iterable to Sage 300 integration — real-time, two-way sync

Keep Iterable and Sage 300 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 Iterable and Sage 300

Feed the real customer, order, and revenue records from Sage 300 into Iterable so campaigns run on who actually bought what, and let contact and consent changes flow back in real time.

Marketing runs on lists of people, but the list rarely knows which of those people are paying customers, what they ordered, or what they are worth. Sage 300 holds exactly that: GL Accounts, Journal Batches, Order Entry Orders, Purchase Orders that record who the customer is, what they bought, and what they owe. When the two are joined only by a periodic export, campaigns go out against stale audiences, existing customers get prospecting emails, high-value accounts look the same as cold leads, and a canceled order still counts toward a segment.

Stacksync syncs GL Accounts, Journal Batches, Order Entry Orders, Purchase Orders in Sage 300 with Export data, Users, Events, Campaigns in Iterable in real time, and where both sides accept writes, in both directions. Customer, order, and invoice data maps field by field onto the contacts, audiences, or accounts Iterable works with, so segmentation and personalization run on current purchase history instead of a month-old snapshot. Contact details and consent changes that originate in Iterable flow back onto the record in Sage 300.

The strongest bridge between the two is identity and purchase history, who the customer is and what they have bought, so that is where most of the value sits. Because the sync is field-level, each system keeps the attributes the other has no use for; only the shared records are held in agreement.

Common use cases

  • 01 Write web and EDI orders into Order Entry and return order status to the source channel.
  • 02 Replicate GL, AR, and AP detail to a warehouse for consolidated multi-company reporting.
  • 03 Two-way sync User profiles and their custom data fields between Iterable and a Postgres database or CRM so attributes and subscription state stay aligned in both systems.
  • 04 Push warehouse or CRM audience segments into Iterable as Users via bulkUpdate (up to 1000 per call) and subscribe them to static Lists to drive campaigns.

Common sync patterns

Suppress or target existing customers

Because Sage 300 knows who is already a paying customer, Iterable can exclude them from acquisition campaigns or single them out for renewal and cross-sell.

One customer identity across both systems

A person or company's contact details corrected in either system update the other, so marketing and the back office stop maintaining separate versions of the same record.

Lifecycle triggers from back-office events

A first order, a renewal, or a lapsed account recorded in Sage 300 appears in Iterable within seconds, ready to start or stop a lifecycle campaign.

What you can sync between Iterable and Sage 300

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.

Iterable objects Sage 300 objects How this pairing syncs
Templates Reusable email/SMS/push/in-app message templates with handlebars fields; read via /api/templates and per-channel get endpoints, written via /api/templates/email/upsert and the other channel upserts. Purchase Orders Procurement documents read for spend visibility and receiving. Templates is specific to Iterable and Purchase Orders to Sage 300 — each maps to any object or custom field on the other side.
Lists Static subscriber lists; read via GET /api/lists and /api/lists/getUsers, with users added or removed via /api/lists/subscribe and /api/lists/unsubscribe to control who receives a send. Inventory Items Item master with costing and quantities, synced to storefronts and WMS. Lists is specific to Iterable and Inventory Items to Sage 300 — each maps to any object or custom field on the other side.
Catalogs Named catalogs of items (products, content) used for personalization and recommendations; items upserted and read via /api/catalogs/{catalogName}/items. AR Invoices and Receipts Billing and payment records replicated for cash and revenue reporting. Catalogs is specific to Iterable and AR Invoices and Receipts to Sage 300 — each maps to any object or custom field on the other side.
Commerce / Purchases Purchase and cart activity tracked via /api/commerce/trackPurchase and /api/commerce/updateCart, feeding revenue attribution and abandoned-cart journeys. AR Customers Receivables customer master synced to CRMs and billing tools. Commerce / Purchases is specific to Iterable and AR Customers to Sage 300 — each maps to any object or custom field on the other side.
Export data Historical user and event records pulled through the Export API (/api/export/data.json, data.csv, and userEvents) across data types like emailSend, emailOpen, emailClick, emailBounce, purchase, and customEvent. AP Vendors Payables vendor master synced with procurement and payment systems. Export data is specific to Iterable and AP Vendors to Sage 300 — each maps to any object or custom field on the other side.
Users User profiles keyed by email or userId with custom data fields; upserted via POST /api/users/update, read via GET /api/users/{email} or getByUserId, bulk-written via /api/users/bulkUpdate (up to 1000 users per call), and deleted or GDPR-forgotten. GL Accounts Chart of accounts read for transaction mapping across integrations. Users is specific to Iterable and GL Accounts to Sage 300 — each maps to any object or custom field on the other side.

How changes propagate between Iterable and Sage 300

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.

Iterable Sage 300 Sub-second propagation

DetectionIterable notifies Stacksync of record changes through webhook events. System Webhooks push email/SMS/push/in-app and custom events (send, open, click, bounce, complaint, unsubscribe) as JSON POSTs in near real time.

DeliveryEach detected change is applied to Sage 300 as a row-level write, with types converted between the two schemas.

Sage 300 Iterable Interval-based propagation

DetectionStacksync polls Sage 300 for changes on an incremental schedule, reading only records changed since the previous pass. Scheduled polling.

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

Rate-limit considerations

  • Iterable: Limits are per endpoint and per project/key; exceeding one returns HTTP 429, so exponential backoff is advised. Event tracking allows far higher volume than metadata endpoints like campaigns/templates, and the Export API is throttled more tightly. Since Nov 10, 2025, passing the key in the query string or body is rate-limited more strictly than the Api-Key header.
What ships with Iterable ⇄ Sage 300

Connect Iterable and Sage 300 for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Iterable–Sage 300 connection.

Real-time

Two-way sync

Changes in Iterable or Sage 300 instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Iterable or Sage 300 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 Iterable or Sage 300 record.

Observability

Monitoring

Track your Iterable ⇄ Sage 300 sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Iterable and Sage 300.

How the Iterable and Sage 300 connectors work

Iterable

Integration surface
Iterable REST API (JSON over HTTPS): Users, Events, Campaigns, Templates, Lists, Catalogs, and Commerce endpoints, plus a bulk Export API for historical data
Authentication
API key sent in the Api-Key HTTP header (also accepted as Api_Key; the name is case-insensitive). Keys are scoped by type - Server-side, JavaScript (Web SDK), or Mobile - with optional JWT-enabled keys. US projects use api.iterable.com; EU projects use api.eu.iterable.com.
Change detection
System Webhooks push email/SMS/push/in-app and custom events (send, open, click, bounce, complaint, unsubscribe) as JSON POSTs in near real time; historical backfill and incremental catch-up run through the Export API over a date range.
Capabilities
read · write · webhooks
Rate limits
Limits are per endpoint and per project/key; exceeding one returns HTTP 429, so exponential backoff is advised. Event tracking allows far higher volume than metadata endpoints like campaigns/templates, and the Export API is throttled more tightly. Since Nov 10, 2025, passing the key in the query string or body is rate-limited more strictly than the Api-Key header.

Sage 300

Integration surface
Sage 300 Web API (REST) on newer releases; .NET/COM SDK and direct SQL Server access on-prem
Authentication
Sage 300 user credentials (Basic auth on the Web API); database credentials for direct SQL reads
Change detection
Scheduled polling; batch-oriented modules with no webhook surface
Capabilities
read · write
How it works

How to connect Iterable to Sage 300 — 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 Iterable and Sage 300 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
    Iterable connected
    Sage 300 connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Iterable and Sage 300 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 · Iterable ⇄ Sage 300
    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
    Iterable Sage 300
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Iterable and Sage 300 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
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 469 integrations available for Iterable and Sage 300.

Popular · 8 of 469
All Iterable integrations All Sage 300 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