What kinds of integration we build.
The technical landscape of a 50-500 employee company is heterogeneous by default: an eight-year-old ERP, a new CRM, two marketing platforms, a critical database maintained by the person about to retire, a payment gateway, and a Drive with six spreadsheets sustaining reports nobody wants to document. Integrating this stack without replacing it is what we do — and we do it without locking you into vendor contracts.
REST and GraphQL APIs
80% of your modern tools have documented APIs. We consume them respecting rate limits, pagination, authentication (OAuth2, API key, HMAC), and transient errors with exponential backoff. We never leave a flow without failure handling.
Bidirectional webhooks with signature
When an app needs to notify you of an event (new lead, payment processed, ticket updated), we expose an n8n endpoint with HMAC verification, idempotency, and replay protection. And vice versa: we emit webhooks to external systems with the same security.
Direct database connection when needed
Legacy ERPs sometimes lack a decent API. We connect via direct SQL (PostgreSQL, MySQL, SQL Server, Oracle) with limited permissions, explicit transactions, and full operation logs. For Active Directory / LDAP, the same. It works on any system where data exists.
RPA when there's no other option
For the few cases where there's no API or database access (legacy intranets, locked supplier portals), we automate the browser with Playwright or similar tools. It's not our first choice, but when it's the only one, we make it maintainable.
We'd been trying for two years to get the ERP and CRM talking. They told us we needed to replace one. FlowProp connected them in six weeks with n8n. We still have both systems.
What we don't do
- We don't ask you to switch ERPs / CRMs. We work with what you have.
- We don't use Zapier or Make. Self-host with n8n; your credentials don't leave your infra.
- We don't deploy "to production" without staging. We test against real data first.