Marketo to Neo4j integration — real-time, two-way sync

Yes. Stacksync provides a managed, real-time two-way integration between Marketo and Neo4j: authenticate both systems, choose the objects to sync (such as Marketo's Companies and Opportunities and Opportunity Roles), map fields visually, and changes propagate both ways in milliseconds — no code required.

Change detection on Marketo: Polling: Get Lead Changes and Get Lead Activities from a paging token seeded by a sinceDatetime, plus Get Deleted Leads, or Bulk Extract filtered on createdAt/updatedAt. Marketo's Webhooks are Smart Campaign flow-step outbound HTTP calls to a URL, not a general record-change subscription, so there is no push feed of arbitrary CRUD. On Neo4j: Neo4j Change Data Capture on Enterprise and Aura streams graph changes; otherwise Cypher polling on timestamp properties. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.

On the Neo4j side: Properties, Labels, Indexes & Constraints, Databases, plus custom fields where Neo4j exposes them. On the Marketo side: Activities and Lead Changes, Static Lists, Programs and Program Members, Smart Campaigns. Stacksync auto-detects both schemas and converts types between the two systems.

Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.

Common patterns for Marketo and Neo4j: Query Marketo like a database; Build audiences from your own data; Engagement and results next to the customer. Contacts, leads, audiences, and campaign metrics from Marketo live in Neo4j as ordinary tables or collections, joinable with the rest of your data and reachable without touching the vendor API.

Marketo: Marketo REST API (JSON over HTTPS) for Leads, Companies, Opportunities, Custom Objects, Activities, Lists, Programs, and Campaigns, plus an asynchronous Bulk Import (leads) and Bulk Extract (leads/activities/program members/custom objects) API and an Asset REST API for emails, forms, and landing pages. Authentication: OAuth 2.0 client_credentials (2-legged): GET the Identity URL /oauth/token?grant_type=client_credentials with a Custom Service client_id and client_secret to receive an access token valid for 3600 seconds, then send it as Authorization: Bearer on each call. The instance base URL is https://{munchkinId}.mktorest.com; passing the token as an access_token query parameter is deprecated (removal July 31, 2026). Neo4j: Bolt binary protocol with Cypher via official drivers, plus an HTTP query API. Authentication: Username/password (basic auth); enterprise deployments add SSO options. Stacksync manages authentication, retries, and rate limits on both sides.