Data & Storage · Integration
Lobster
Add Lobster to your product for your customers, and give your AI agents governed access to it.
Embed a Lobster integration so your product can reach the data integration and EDI environment a customer already runs rather than asking them to build a bridge to you. Lobster is a no-code integration platform that handles ETL, EDI and API traffic in the formats trading partners actually use, including EDIFACT, ANSI X12, SAP IDoc, XML and JSON, so handing a document to it is usually cheaper than implementing those formats yourself. Each customer connects their own environment, mappings and partner profiles are per-tenant configuration, and fastn owns the auth, retries, pagination and API upkeep. The same governed connection serves your product features and your AI agents.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own Lobster environment so your product can hand documents to the integration and EDI flows they already operate.
Send structured messages in the format a customer's trading partners expect without implementing EDIFACT or X12 handling in your own codebase.
Read processed data back out so records that arrived from a partner land in your product instead of in a file share.
Support the long tail of customer setups, where each one has its own profiles, mappings and partner formats, as configuration rather than code.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent checks whether a document a customer expected has been processed, reading only that tenant's environment.
An agent explains why a message was rejected by pulling the processing detail behind it, with the read audited.
An agent hands a document to a customer's Lobster flow within scoped permissions, with the write attributed.
Example prompt
Did the order file we sent this partner get processed in Lobster, and if not, what failed?
Set up Lobster in 4 steps
- 01Enable the Lobster connector in your fastn dashboard.
- 02Have each customer connect their own Lobster environment with their own credentials.
- 03Map the documents and message formats you exchange, per customer, as configuration.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Lobster integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Lobster integration without building it. Your customers connect their own Lobster account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Lobster update is not your on-call problem.
- One integration serves your product and your agents. The same governed Lobster connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Works well with
Apache KafkaOften used alongside
Tools the same teams tend to run next to Lobster, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceLobster integration FAQ
How do I add a Lobster integration to my product?
Enable the Lobster connector in your fastn dashboard, then let each customer authenticate their own Lobster account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Lobster client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Lobster account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Lobster account and only ever sees their own records, datasets and fields. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Lobster integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent checks whether a document a customer expected has been processed, reading only that tenant's environment.
Who maintains the Lobster integration?
fastn does. When Lobster changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the Lobster integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large Lobster reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the Lobster integration?
A common starting point: connect their own Lobster environment so your product can hand documents to the integration and EDI flows they already operate. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Lobster integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Lobster does not change your per-connector cost. You can start free with 3 connected accounts.
Add Lobster to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.