Every adapter, and where it stands.

197 adapters, each with a sample project, a message schema, a documented parameter set and an engineer who owns it. The ones most people need first are available today. The rest of the catalogue is in beta, and we say so on every row rather than letting you find out later.

Ask about an adapter Adapter docs ↗

Adapter	Category	In	Out	HL7 v2	FHIR	X12 / EDI	Bulk & file	Real-time API	Streaming	Status

No adapter matches those filters.

That doesn't mean we can't connect it. Grid's Custom nodes speak anything you can describe, and building a new adapter is normal work rather than a special project.

Ask us about it

Columns describe what the adapter is tested for, not what the vendor theoretically supports. “Bulk & file” covers batch, SFTP and flat-file exchange. Available today means the template is hardened and running across multiple customers. Beta means it works and runs somewhere, but the template is still being finished, so expect one of our engineers alongside you on the first deployment. Around 95% of the catalogue is beta today, and that share falls every month.

Not on the list?

Then it's a Tuesday.

The catalogue is what we've already tested and templated, not the boundary of what Grid can talk to. A Custom node plus a schema handles anything with a documented format, and most “bespoke” endpoints turn out to be a familiar shape wearing a different hat.

New adapters are included. When we build one, every customer gets it. We don't charge the person who asked first.
Typical turnaround is two weeks for a documented endpoint, from spec to a tested template in your project.
Undocumented endpoints too. Send us a packet capture and a sample. We've reverse-engineered worse.

Request an adapter

What ships with every adapter

Sample project

A working source → transform → destination you can start and watch.

Message schema

The grammar as that vendor actually sends it, quirks included.

Parameter docs

Every field explained in the console, next to the field.

Test samples

De-identified messages to run the transform against before go-live.

Known-issues note

The thing that will bite you, written down before it does.

A named owner

An engineer here who maintains it and answers for it.

Migrating from another engine?

Adapters for Rhapsody, Mirth, Iguana, Cloverleaf, Corepoint, BizTalk and Ensemble let Grid run alongside your incumbent while we prove parity on live traffic, so cutover is a routing change rather than a weekend. How that works →