Technical Architecture for Automated Financial Communications: Migrating a Mexican Bank to Intercom via Apache NiFi
A Mexican retail bank faced legal exposure because unsegmented core banking data was triggering non-compliant messaging. We replaced the legacy stack with Intercom, integrated through Apache NiFi, which buffers the communication logic and applies granular segmentation before anything is sent. Local APIs enforce 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, with 240+ employees, offers credit, lending and investment products.
What We Built
We built a governed communication system: 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 had been through a bad automation rollout once already. A previous implementation had let unfiltered data trigger massive, unsegmented email campaigns, which created legal friction and eventually ended the bank's prior CRM contract. The team approached any new automation with that history in mind.
The legacy core banking system could not run the logic that real-time, behavior-triggered communication requires, and its API limitations regularly caused synchronization lag. On top of that the bank had a fixed deadline: it had to be off Infobip by September 30, 2022.
Our Approach
We moved the design from a direct sync to a middleware-led architecture, with Apache NiFi between the core banking system and Intercom. Financial data is cleaned and validated in NiFi before it ever reaches the communication layer, and the hard-coded safety valves in that layer prevent the accidental mass messaging that had caused the earlier trouble.
For SMS and WhatsApp we weighed standard international gateways against a localized Mexican provider. We chose Airmovil, the local provider, because regional data residency expectations required it.
This engagement is part of our systems integration work for finance & insurance organisations.
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, which rebuilt organizational trust in automation and satisfied the bank's internal legal requirements on customer contact frequency.
Faster Loan Disbursement Notifications
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, which ended the redundant licensing costs. 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, which prevents API saturation. 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. Credit card interest questions and debt consolidation applications each run their own flow, and a human agent is notified only after the customer is qualified.
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 are built into the NiFi workflow. Each gate checks a dynamic Do Not Contact list maintained in the core system, giving the bank a second layer of protection against non-compliant outreach that operates outside Intercom's standard unsubscribes.
A previous rollout let unfiltered data trigger mass unsegmented email campaigns, and it ended the bank's prior CRM contract. The legacy core banking system also couldn't run real-time, behavior-triggered logic. Now Apache NiFi sits between the core banking system and Intercom. Financial data is cleaned and validated before it reaches the communication layer, and hard-coded safety valves block accidental mass messaging. SMS and WhatsApp go through Airmovil, a local provider, because regional data residency expectations required it.
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.
Mexico's federal data protection law (LFPDPPP) governs how the bank handles personal data. 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.
