Content & Documents · Integration
Objective ECM
Add Objective ECM to your product for your customers, and give your AI agents governed access to it.
Embed an Objective ECM integration so your product can work with documents and records where a customer already governs them. Objective ECM, from Objective Corporation, is the content and records management system used across government and other regulated organisations, and its API covers files and folders, metadata, versions and renditions, with the retention and records controls those organisations have to satisfy. Access runs through each customer's own grant, so their existing permissions apply and your product cannot read content the connected account could not read itself. fastn owns the auth, retries, pagination and API upkeep, and the same governed connection is what your AI agents use.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Objective ECM repository so documents and folders are reachable inside your product with no per-customer code.
File a document your product generated into the right folder with the metadata a customer's records rules require.
Read metadata and version history per tenant so your product can show which version is current and how it got there.
Support each organisation's own folder structures, metadata schemes and permissions as configuration rather than code.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent finds the current version of a document and summarises it, reading only what the connected account is allowed to read.
An agent files a new document with the correct metadata within scoped permissions, with the write logged.
An agent answers which version of a record was in force on a given date from its version history.
Example prompt
Find the current approved version of this document in Objective ECM and tell me what changed from the last one.
Set up Objective ECM in 4 steps
- 01Enable the Objective ECM connector in your fastn dashboard.
- 02Have each customer authorise their own repository so calls run under their credentials and permissions.
- 03Map the folder structure, metadata fields and document types your product uses, per customer.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Objective ECM integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Objective ECM integration without building it. Your customers connect their own Objective ECM account inside your product and work their files, documents and versions there, with no per-customer code on your side.
- Handle the part that actually costs time: permissions and versioning are easy to get subtly wrong, and mistakes expose content. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an Objective ECM update is not your on-call problem.
- One integration serves your product and your agents. The same governed Objective ECM connection powers in-product features and gives AI agents scoped, audited access, so you let your product work with your customers' documents in place without wiring it twice.
Used by these teams
Compare with
Egnyte
Box
DocusignOften used alongside
Tools the same teams tend to run next to Objective ECM, across other categories.
Shopify
Stripe
Jira
AsanaObjective ECM integration FAQ
How do I add an Objective ECM integration to my product?
Enable the Objective ECM connector in your fastn dashboard, then let each customer authenticate their own Objective ECM account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Objective ECM client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Objective ECM account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Objective ECM account and only ever sees their own files, documents and versions. 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 Objective ECM 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 finds the current version of a document and summarises it, reading only what the connected account is allowed to read.
Who maintains the Objective ECM integration?
fastn does. When Objective ECM 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.
Whose permissions does the Objective ECM integration run under?
Each customer's own Objective ECM grant. Where Objective ECM holds a library, their existing folder and item permissions apply and your product cannot reach content the connected account could not reach itself. Where it processes content you supply rather than storing it, the call runs under that customer's own credentials and is logged per tenant.
Can my product create or update content in Objective ECM automatically?
Where Objective ECM supports writes, documents, entries and assets can be created, updated and filed from your product or by an agent within scoped permissions, with each action logged. Where it is a read surface, the same connection serves reads only.
What can I build with the Objective ECM integration?
A common starting point: let each customer connect their own Objective ECM repository so documents and folders are reachable inside your product with no per-customer code. 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 Objective ECM integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Objective ECM does not change your per-connector cost. You can start free with 3 connected accounts.
Add Objective ECM to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.