Skip to content
ERP ⇄ Analytics

Dynamics 365 Business Central to Pendo integration — real-time, two-way sync

Keep Dynamics 365 Business Central and Pendo 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 Dynamics 365 Business Central and Pendo

Put Dynamics 365 Business Central's records into Pendo as live data for reporting and dashboards, without nightly exports, and send the segments and metrics Pendo computes back where Dynamics 365 Business Central can use them.

ERP data is some of the most requested data for analysis and some of the hardest to pull: the record types are many, the APIs are strict, and export jobs break on every upgrade. Whether Dynamics 365 Business Central carries financials, operations, workforce data, or all three, those numbers belong in Pendo, next to the product, behavioral, and web data the team already measures.

Stacksync syncs Purchase Orders, General Ledger Entries, Journals, Dimensions from Dynamics 365 Business Central into Pendo continuously, handling API limits and schema drift as it goes, so each record type arrives as Guide Events, Poll / NPS Responses, Features / Pages / Guides (metadata), Visitors ready to report on. The connection is bi-directional, so segments, scores, and metrics computed in Pendo can be written back to fields in Dynamics 365 Business Central where that is useful.

Common use cases

  • 01 Export feature, page, and guide Events out of Pendo over event-time windows into Postgres or a warehouse so product usage joins with CRM, billing, and support data in SQL.
  • 02 Pull NPS scores and poll responses into a database so voice-of-customer sits next to revenue, renewal, and churn signals for analysis.
  • 03 Sync vendor and purchase order data with procurement or AP automation tools.
  • 04 Create sales orders in Business Central automatically from e-commerce or CRM order records, and sync fulfillment status back.

Common sync patterns

Where Dynamics 365 Business Central runs operations: inventory and fulfillment metrics

Operational records from Dynamics 365 Business Central become measurable in Pendo, joinable with the rest of what the company tracks for supply and fulfillment reporting.

Where Dynamics 365 Business Central is the HR system of record: workforce and cost analysis

Worker and organization data from Dynamics 365 Business Central syncs into Pendo for headcount, cost, and utilization reporting alongside other company data.

Write-back where Dynamics 365 Business Central exposes writable fields: segments and scores return

Segments, scores, or metrics computed in Pendo sync onto the matching records in Dynamics 365 Business Central, so operations act on what the analysis found.

What you can sync between Dynamics 365 Business Central and Pendo

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.

Dynamics 365 Business Central objects Pendo objects How this pairing syncs
Sales Orders Order headers and lines created from external channels and read back for fulfillment status. Features / Pages / Guides (metadata) Definitions of tagged UI elements listed through the entity endpoints; read-only reference used to label and join the event streams. Sales Orders is specific to Dynamics 365 Business Central and Features / Pages / Guides (metadata) to Pendo — each maps to any object or custom field on the other side.
Sales Invoices Billing documents synced to CRMs and payment platforms. Visitors End-user records with agent-collected and custom fields; queried through the Aggregation API and enriched with custom fields written back via the Metadata API. Sales Invoices is specific to Dynamics 365 Business Central and Visitors to Pendo — each maps to any object or custom field on the other side.
Purchase Orders Procurement documents exchanged with supplier-facing systems. Accounts Company/workspace records that roll visitors up to an account dimension; readable via Aggregation and a write target for custom fields (plan, ARR, health) via the Metadata API. Purchase Orders is specific to Dynamics 365 Business Central and Accounts to Pendo — each maps to any object or custom field on the other side.
General Ledger Entries Posted financial transactions read for reporting; posted entries are immutable. Feature Events Click/interaction events on tagged features, read-only through the Aggregation API over an event-time window and joined to the Feature definitions. General Ledger Entries is specific to Dynamics 365 Business Central and Feature Events to Pendo — each maps to any object or custom field on the other side.
Journals Staging records for financial postings created by integrations before posting. Page Events Page-view events for tagged pages; read-only via the Aggregation API, used for adoption and path analysis in a warehouse. Journals is specific to Dynamics 365 Business Central and Page Events to Pendo — each maps to any object or custom field on the other side.
Dimensions Analytical tags (department, project) that syncs preserve for reporting integrity. Guide Events Guide seen/advanced/dismissed and step events for in-app walkthroughs; read-only through the Aggregation API to measure onboarding flow adoption. Dimensions is specific to Dynamics 365 Business Central and Guide Events to Pendo — each maps to any object or custom field on the other side.

How changes propagate between Dynamics 365 Business Central and Pendo

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.

Dynamics 365 Business Central Pendo Sub-second propagation

DetectionDynamics 365 Business Central notifies Stacksync of record changes through webhook events. API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime.

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

Pendo Dynamics 365 Business Central Interval-based propagation

DetectionStacksync polls Pendo for changes on an incremental schedule, reading only records changed since the previous pass. Polling - reads query the Aggregation API over event-time windows.

DeliveryEach detected change is written to Dynamics 365 Business Central through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Pendo: Pendo does not publish fixed numeric limits; it throttles heavy Aggregation queries with 429s and caps/paginates large responses, so wide exports are paced and time-windowed.
What ships with Dynamics 365 Business Central ⇄ Pendo

Connect Dynamics 365 Business Central and Pendo for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dynamics 365 Business Central–Pendo connection.

Real-time

Two-way sync

Changes in Dynamics 365 Business Central or Pendo instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Dynamics 365 Business Central or Pendo 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 Dynamics 365 Business Central or Pendo record.

Observability

Monitoring

Track your Dynamics 365 Business Central ⇄ Pendo sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Dynamics 365 Business Central and Pendo.

How the Dynamics 365 Business Central and Pendo connectors work

Dynamics 365 Business Central

Integration surface
REST API built on OData v4 (standard API v2.0), extensible with custom API pages in AL
Authentication
OAuth 2.0 via Microsoft Entra ID
Change detection
API webhooks (change notifications on subscribed entities) plus polling on lastModifiedDateTime
Capabilities
read · write · webhooks

Pendo

Integration surface
Pendo Engage API (REST) on app.pendo.io (US) / app.eu.pendo.io (EU), base path /api/v1/ - Aggregation API for reads and the Metadata API for writes
Authentication
Integration key sent in the x-pendo-integration-key header, generated in Subscription Settings; keys are scoped read-only or read/write, so writes require a read/write key
Change detection
Polling - reads query the Aggregation API over event-time windows; no change-data-capture feed and no data-change webhooks. Writes go through the Metadata API on demand.
Capabilities
read · write
Rate limits
Pendo does not publish fixed numeric limits; it throttles heavy Aggregation queries with 429s and caps/paginates large responses, so wide exports are paced and time-windowed.
How it works

How to connect Dynamics 365 Business Central to Pendo — 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 Dynamics 365 Business Central and Pendo 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
    Dynamics 365 Business Central connected
    Pendo connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Dynamics 365 Business Central and Pendo 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 · Dynamics 365 Business Central ⇄ Pendo
    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
    Dynamics 365 Business Central Pendo
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Dynamics 365 Business Central and Pendo 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 481 integrations available for Dynamics 365 Business Central and Pendo.

Popular · 7 of 481
All Dynamics 365 Business Central integrations All Pendo 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