Developer Tools · Integration
SOAP
Add SOAP to your product for your customers, and give your AI agents governed access to it.
SOAP is still how a great deal of enterprise software talks, particularly the systems built before REST won, and its shape differs enough to matter: operations are described by a WSDL, requests and responses are XML envelopes with namespaces, faults come back as structured errors rather than status codes, and authentication is often WS-Security headers instead of a bearer token. An embedded SOAP integration reads a customer's WSDL, executes the operations it describes, and maps the XML in and out so your product deals in fields rather than envelopes. Each customer supplies their own endpoint and credentials, so a call runs against their system under their access. fastn handles credential storage, retries and mapping, so a customer with an unusual service does not need a release from you.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer describe their own SOAP service to your product once, with a WSDL and credentials, at setup.
Call an operation on a legacy internal service without shipping an XML client inside your product.
Map request and response elements per customer so one flow serves services that describe the same thing differently.
Handle a fault as a result your workflow can act on rather than an unexplained failure.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads the operations a WSDL describes before deciding which one to call.
An agent calls a read-only operation and grounds its answer in what the service returned.
An agent invokes an approved operation within the set you allow, with every call logged.
Example prompt
Call the customer's policy lookup operation for this reference and tell me the status it returns.
Set up SOAP in 4 steps
- 01Open the SOAP connector from your fastn dashboard.
- 02Have each customer supply their own WSDL location, service endpoint and credentials, including any WS-Security detail.
- 03Choose the operations your product calls, map the request and response elements, then enable them.
- 04Call them from your product, or expose the same connection to an agent through the MCP server.
Why teams use the SOAP integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a SOAP integration without building it. Your customers point it at their own endpoint and credentials and work their services, builds and deployments through it, with no per-customer code on your side.
- Handle the part that actually costs time: these systems emit a lot of webhooks, and replay after downtime has to be handled. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a SOAP update is not your on-call problem.
- One integration serves your product and your agents. The same governed SOAP connection powers in-product features and gives AI agents scoped, audited access, so you connect engineering activity to the rest of the business without wiring it twice.
Used by these teams
Compare with
GraphQL
OpenAPIOften used alongside
Tools the same teams tend to run next to SOAP, across other categories.
Slack
Snowflake
Airtable
PostgreSQLSOAP integration FAQ
How do I add a SOAP integration to my product?
Enable the SOAP connector in your fastn dashboard, then let each customer authenticate their own SOAP account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no SOAP client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
How is a SOAP connection configured per customer?
SOAP is a specification rather than a service you sign up for, so there is no SOAP account. Each customer supplies their own endpoint and credentials, and that connection is scoped to them, so they only ever reach their own services, builds and deployments. The per-tenant isolation works the same way it does for a vendor product.
Can AI agents use this SOAP 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 reads the operations a WSDL describes before deciding which one to call.
Who maintains the SOAP integration?
fastn does. When SOAP 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.
Can I react to SOAP events in real time?
Yes, through event triggers. Events are delivered per tenant and can be replayed after an outage, so a webhook missed during downtime is not silently lost.
Can an agent open or update items in SOAP?
Yes, within scoped permissions, and every action is audited so an agent's changes are attributable.
What can I build with the SOAP integration?
A common starting point: let each customer describe their own SOAP service to your product once, with a WSDL and credentials, at setup. 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 SOAP integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding SOAP does not change your per-connector cost. You can start free with 3 connected accounts.
Add SOAP to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.