The Challenge
ERP Integrations Without an In-House API Team
- They needed a Sage Evolution integration but could not justify the cost of Sage’s developer license or the internal effort to build and maintain custom integrations.
- They did not have a dedicated API integration team and did not want their core developers tied up on long, brittle integration projects.
- SDKs and ERPs change over time, and keeping custom code aligned with every new version was going to be an ongoing burden.
- Provided ready-made building blocks for ERPs like Sage Evolution.
- Allowed “half-technical” support staff to build and maintain integrations.
- Reduced dependence on writing and maintaining low-level integration code.
Integration without an API team
“We needed Sage Evolution integration but couldn’t afford the developer licence or a full‑time API team. Flowgear solved that problem without us having to build and maintain everything ourselves,” said Dave B, Founder at FIGJAM Mobile.
From code to “Lego”
“We don’t have to put devs on long integration projects. Our support team can build Flowgear workflows instead. It’s more like Lego than writing 10,000 lines of code,” said Dave B.
The Solution
Flowgear as FIGJAM’s Integration Toolkit
FIGJAM selected Flowgear largely because of its Sage Evolution connector, and over time it has become their go-to platform for integrations.
Flowgear now helps FIGJAM to:
- Avoid low-level API work – support staff can assemble integrations in Flowgear rather than developers writing thousands of lines of custom code.
- Handle multiple ERPs and APIs, FIGJAM uses Flowgear most often for Sage Evolution, but also in scenarios involving other ERPs and APIs (e.g. SAP Business One, Acumatica, and newer platforms they encounter in East and Central Africa). Where no dedicated connector exists, they rely on generic web request nodes to integrate via APIs.
- Maintain integrations as ERPs evolve because Flowgear keeps pace with ERP changes (SDK updates, new API endpoints), FIGJAM avoids re-engineering every time the underlying systems shift.
Flowgear has effectively become FIGJAM’s standard way to connect its mobile apps to
customer systems, especially where ERP integration is involved.
The Results
Faster Integrations, Less Maintenance, Happier Teams
- Faster delivery of integrations time to integrate with customer ERPs is significantly reduced compared to building from scratch. FIGJAM can stand up new flows quickly using out-of-the-box nodes.
- Reduced dependence on specialist developers. Support and implementation staff build and adjust many integrations themselves, freeing developers to focus on FIGJAM’s core products.
- Operational transparency and troubleshooting. The team can see what is happening inside workflows via logs, troubleshoot issues themselves, and involve Flowgear support when needed. Over the years they have jointly uncovered bugs in SDKs and APIs and resolved issues across both sides.
- Consistent support experience. FIGJAM leans on Flowgear’s training content, examples, and ticket-based support to keep projects moving. Questions are answered quickly enough that integrations do not become a bottleneck.
Faster ERP projects, fewer headaches
“Time to integrate with Flowgear is much shorter for us now. There are solid tools out the box, the courses are good, and support is responsive, so we get integrations done without building everything from scratch,” said Dave B.
Default choice for new integrations
“When customers bring us a new ERP or API, our first instinct is to see how to do it in Flowgear. It’s become our default way to build and maintain those integrations,” said Dave B.
Looking Ahead
New ERPs, Data Pipelines, and AI-Assisted Workflows
Looking forward, FIGJAM plans to keep expanding how it uses Flowgear:
- New ERPs and regions. Ongoing and planned work includes Microsoft Dynamics 365 Business Central and ERPs common in East Africa and India (such as Tally and other smaller systems). When they meet a new platform, the default question is how to connect it via Flowgear.
- Data movement and warehousing. FIGJAM expects to use Flowgear more for moving data between FIGJAM’s systems, customer ERPs, and data warehouses, alongside tools like BigQuery.
- Exploring Flowgear’s MCP server and AI features. FIGJAM is interested in testing Flowgear’s MCP server and AI-assisted workflow building to prototype and simplify workflows faster, especially for recurring tasks like extracting data and building reports.
Flowgear remains their primary choice when a customer asks, “Can you integrate with our
system?”
