Content & Documents · Integration
Slite
Add Slite to your product for your customers, and give your AI agents governed access to it.
Slite's public API lives at api.slite.com/v1 and authenticates with an x-slite-api-key header rather than OAuth, so the key carries the permissions of the account that issued it. Notes are effectively the only object: you create one with markdown content and an optional parent note ID, and document hierarchy is expressed purely through that parent link rather than through folders. Reading a note gives markdown back, so anything you write has to survive a round trip through Slite's own formatting rules, and rich blocks do not always come back as they went in. Search is a separate endpoint that returns note references rather than full bodies, so crawling a workspace means a second call per result. fastn stores each customer's Slite key in its own tenant and keeps the note mapping working as the API changes.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Slite workspace so your product can publish notes into it
Write meeting or incident write-ups from your app into a parent note so they nest under the right doc
Mirror a customer's Slite handbook into your in-app help so support answers match their internal wording
Keep a generated status document in Slite up to date by rewriting the same note rather than creating new ones
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent draft a note from a conversation and file it under a named parent, with the note ID and author recorded per tenant for audit
Have an agent search a customer's Slite and answer questions only from notes it can cite
Let an agent update an existing note in place when a source system changes, rather than duplicating it
Example prompt
Find the onboarding checklist in our Slite and tell me which steps mention security review.
Set up Slite in 4 steps
- 01Enable the Slite connector from your fastn dashboard.
- 02Have each customer authorise their own Slite account, so calls run under their credentials rather than a shared key.
- 03Decide which files, documents and versions your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Slite integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Slite integration without building it. Your customers connect their own Slite 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 a Slite update is not your on-call problem.
- One integration serves your product and your agents. The same governed Slite 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
Notion
Box
DocusignOften used alongside
Tools the same teams tend to run next to Slite, across other categories.
Shopify
Stripe
Jira
AsanaSlite integration FAQ
How do I add a Slite integration to my product?
Enable the Slite connector in your fastn dashboard, then let each customer authenticate their own Slite account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Slite client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Slite account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Slite 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 Slite integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent draft a note from a conversation and file it under a named parent, with the note ID and author recorded per tenant for audit
Who maintains the Slite integration?
fastn does. When Slite 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 Slite integration run under?
Each customer's own Slite grant. Where Slite 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 Slite automatically?
Where Slite 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 Slite integration?
A common starting point: let a customer connect their own Slite workspace so your product can publish notes into it. 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 Slite integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Slite does not change your per-connector cost. You can start free with 3 connected accounts.
Add Slite to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.