Integrations & Workato Recipes
Reusable patterns for connecting your MAP, CRM, and data layer — and the guardrails that keep syncs from silently breaking.
Integrations are an operating layer, not a connector
"We integrated Marketo and Salesforce" usually means a connector is turned on. That is not an integration — it is a pipe. The integration is the set of decisions about what data flows, in which direction, who owns each field, what happens on conflict, and how you know when it breaks. Get those decisions right and the tooling barely matters. Get them wrong and the cleanest iPaaS in the world just moves bad data faster.
Four principles that keep syncs honest
Direction of truth. Every synced field has exactly one system that owns it. Write it down. Bi-directional sync on a field with no owner is how records ping-pong and overwrite human-curated context.
Suppression survives everything. Enrichment and re-sync must respect unsubscribes and suppression. An integration that re-adds opted-out contacts is a compliance incident waiting to happen.
Identity before automation. Decide how people and accounts are matched (email, domain, CRM ID) before you wire actions on top. Most "the routing is broken" tickets are really identity-resolution problems.
Observability is part of the build. If no one reads the sync log, the sync is unmonitored. Bake in error alerts, a dead-letter path for failed records, and a weekly reconciliation check.
Recipes worth standardizing
MAP ↔ CRM lifecycle sync. Map lifecycle status both ways with one owner per transition; route on status change, not on raw score.
Enrichment waterfall with guardrails. Enrich net-new only, never overwrite human-entered fields, and exclude the suppression list from the input set.
Intent → action. Translate 6sense / intent signals into a Marketo segment or a routed task with enough context that the rep acts — and a rule for when a signal is too noisy to fire.
Data hygiene jobs. Scheduled normalization (country, state, picklists), dedup by identity key, and stale-field flagging so smart lists don't silently shrink.
Native vs. iPaaS (Workato / Zapier)
Use the native connector for the high-volume, well-supported path (MAP ↔ CRM person/lead sync). Reach for an iPaaS like Workato when you need multi-step logic, transformation, or systems the native connector doesn't reach — enrichment routing, custom object sync, cross-tool orchestration. Zapier is fine for low-volume, low-stakes glue; it is not where your lead-to-revenue path should live. The test: if the recipe failing would corrupt the system of record or lose a lead, it belongs in a monitored, version-controlled iPaaS flow with error handling — not a fire-and-forget zap.
Before you build anything
Write the one-page integration contract: every field, its owner, its direction, its conflict rule, and its monitoring. That document prevents more outages than any tool feature. If you don't have it, that's the first deliverable.
Want this run on your own stack? Request a free MAP health audit — a focused review of your Marketo, Salesforce, and 6sense setup with the highest-leverage fixes prioritized.