Spark ERP

Platform · Integration

Connect every system, without bespoke code per connection.

A connector framework and Integration Flow engine handle inbound and outbound integration as configured connectors — banking, payments, identity, payroll, e-commerce and more.

Integration Platform StudioAPIs & eventsPlugins 123456789 SecurityDesign Multi-tenancyExtend
How the platform fits together
StudioAPIs & eventsPluginsSecurityMulti-tenancyIntegrationsSpark ERP
From idea to running feature
Design

Model data and pages

1
Configure

Rules and workflows

2
Extend

Plugins and APIs

3
Publish

Versioned release

4
Run

Per-tenant, isolated

5
BankingPaymentsIdentity / SSOPayrollE-CommerceEmail & SMSCloud StorageAnalyticsAI ProvidersSpark ERP

What connects to Spark ERP.

BankingPaymentsIdentity / SSOPayrollE-CommerceEmail & SMSCloud StorageAnalyticsAI Providers

Everything after the connector is set up.

Flows you design, test and switch on

Build a flow visually or describe it in plain words, test one step or a whole run without switching it on, and use a sandbox connection so tests never touch the live system.

Queues with retries and replay

Messages wait until a flow has handled them, are retried with growing delays, and land in a dead state that a person can replay, instead of silently disappearing.

Message brokers

A queue can send its messages to, or read them from, a message broker such as Kafka or RabbitMQ, with the same retries, replay and tracing as any other queue.

Two-way synchronization

Keep records in step with an outside system, compare before changing anything, and decide what happens when both sides changed.

Files, folders and databases

Read CSV, XML and Excel files, watch SFTP folders, and read from or write to a customer database with bound parameters.

Follow one event end to end

Paste a correlation id and see every flow run, event, queue message and synchronization that belonged to it, in order, and where it failed.

A second pair of eyes before go-live

Require a different person to approve before a flow or synchronization is switched on, and pause a running flow until someone approves.

Ship it to another environment

Move flows, queues, synchronizations and connections between environments, or ship them inside a plugin. They arrive switched off and passwords never travel.

One flow engine, not one integration per system.

The Integration Flow engine defines connections, mappings and triggers as configuration, so adding a new integration is closer to configuring a connector than writing and maintaining a bespoke service.

Have a specific system to connect?

Talk to us about the connectors available today and what a custom connector looks like.