Technical Architecture for Automated Financial Communications: Migrating a Mexican Bank to Intercom via Apache NiFi
A Mexican retail bank risked legal exposure. Unsegmented core banking data was triggering non-compliant messaging.
We replaced the legacy stack by integrating Intercom through Apache NiFi. The middleware buffers communication logic and applies granular segmentation. Local APIs enforce strict compliance with Mexican financial regulations.
Executive Summary
Context
A Mexican retail bank needed to replace an aging Infobip implementation. It also had to remediate significant technical debt from a previous failed CRM deployment. The bank's 240+ employees provide credit, lending, and investment products.
What We Built
A governed communication ecosystem. Data routes from the legacy banking core through Apache NiFi middleware into Intercom, and specialized local APIs handle compliant SMS and WhatsApp delivery.
Tech Stack
- Intercom (Central hub), Apache NiFi (Middleware), Airmovil API (Local SMS/WA), Legacy Core Banking System.
Not a fit if you want a "plug-and-play" SaaS integration, or if you lack the internal resources to manage a middleware layer like Apache NiFi.
The Challenge
The bank carried a history of "automation trauma." A previous implementation let unfiltered data trigger massive, unsegmented email campaigns. That caused legal friction and eventually ended their prior CRM contract. The legacy core banking system couldn't natively handle the sophisticated logic that real-time customer behavior triggers require, and its API limitations frequently caused synchronization lag. On top of that, the bank had a hard deadline: migrate away from Infobip by September 30, 2022.
Our Approach
We shifted the strategy from a direct sync to a middleware-led architecture. Apache NiFi sits between the core system and Intercom and acts as the "brain." Financial data gets cleaned and validated before it ever reaches the communication layer. Those hard-coded "safety valves" prevent the accidental mass-messaging that plagued previous efforts. Integrating SMS and WhatsApp forced a real choice: standard international gateways, or a localized Mexican provider. We picked Airmovil, the local provider, because compliance with regional data residency expectations demanded it.
Impact
30% Reduction in Agent Redirection
Intercom's automated bot flows, governed by NiFi segmentation, now resolve routine inquiries with no human intervention at all. The bank's support staff spend their time on high-complexity lending consultations instead.
Governed Communication Safety
Moving logic into the middleware layer removed the risk of uncontrolled automated outreach. Organizational trust in automation came back. Internal legal requirements on customer contact frequency were satisfied.
55% Target Conversion Alignment
Loan disbursement notifications now fire with more precise timing. Messages reach customers through preferred channels like WhatsApp via Airmovil, which shortened the feedback loop between lead qualification and final disbursement.
Successful Vendor Decommissioning
The migration finished inside the strict window needed to terminate the Infobip contract. Redundant licensing costs disappeared. The bank's communication stack now runs from a single interface.
NiFi polls the legacy core system, transforms raw financial data into Intercom-compatible attributes, and manages the "rate limiting" of outbound data. API saturation stops there. The setup also allows complex filtering the core system can't perform natively.
Intercom's Resolution Bot and Custom Bots handle the conversations. Each bot is programmed with branching logic that references NiFi-fed custom objects, so a customer's specific loan status or credit tier dictates the automated response they receive.
A custom bridge connects Intercom to the Airmovil API to meet Mexican regulatory standards. Intercom can trigger localized SMS alerts for sensitive financial transactions. Every interaction still lands as a record in the customer's unified profile.
"Suppression Gates" sit inside the NiFi workflow. Each gate checks a dynamic "Do Not Contact" list maintained in the core system. That gives the bank a second layer of protection against non-compliant outreach, one that lives outside Intercom's standard unsubscribes.
An integration architecture mapping data flow from a legacy core banking system through an Apache NiFi governance layer into Intercom. It solves legacy API saturation by transforming, rate-limiting, and applying suppression gates before executing customer outreach. This enables compliant SMS workflows that reduce agent load while aligning with strict regional data residency laws.
FAQ
NiFi acts as a sandbox. Data is validated and filtered there before it ever touches the customer-facing communication platform. Direct integrations in high-compliance financial environments often lack the "circuit breaker" logic that prevents mass-messaging errors when a legacy core system syncs incorrectly. The middleware layer protects the bank from those legal and contractual risks.
The bank keeps greater control over where its data is processed and stored when NiFi and a local API like Airmovil sit in the path. Sensitive PII (Personally Identifiable Information) only passes to the communication hub when a specific interaction requires it. All SMS/WhatsApp traffic stays inside compliant regional gateways.
