Productivity · Integration
SmartSuite
Add SmartSuite to your product for your customers, and give your AI agents governed access to it.
SmartSuite organises work as solutions containing applications, and each application defines its own fields, so two customers doing the same job will have described it differently. An embedded SmartSuite integration lists solutions and applications, reads the field definitions behind them, reads, creates and updates records, and reacts when a record changes. That structure is the whole integration problem here: a field list compiled into your code is already wrong for the second customer, so discovery at connect time and mapping per tenant is what turns onboarding into configuration. fastn holds each workspace's credentials, handles pagination and rate limits, and keeps the connector current.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own SmartSuite workspace so your product writes into the applications they built.
Read solution, application and field metadata so your setup screens list what that customer genuinely built.
Write a record from your product so a status in SmartSuite reflects what just happened in yours.
React to a record change so work moves without anybody copying it across by hand.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads records from a nominated application to answer a question about current work.
An agent creates or updates a record within scoped permissions, with the write attributed.
An agent inspects field definitions before writing so it maps to fields that genuinely exist.
Example prompt
What is sitting in this application with no owner, and how long has each item been there?
Set up SmartSuite in 4 steps
- 01Enable the SmartSuite connector in your fastn dashboard.
- 02Have each customer authorise their own SmartSuite workspace so records stay theirs.
- 03List their solutions and applications, map the fields you use, then enable the actions and change triggers you need.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the SmartSuite integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a SmartSuite integration without building it. Your customers connect their own SmartSuite account inside your product and work their work items, assignees and due dates there, with no per-customer code on your side.
- Handle the part that actually costs time: every team configures its own fields, statuses and workflow stages. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a SmartSuite update is not your on-call problem.
- One integration serves your product and your agents. The same governed SmartSuite connection powers in-product features and gives AI agents scoped, audited access, so you keep work items in step with what happens in your product without wiring it twice.
Used by these teams
Compare with
Smartsheet
monday.comWorks well with
AirtableOften used alongside
Tools the same teams tend to run next to SmartSuite, across other categories.
Notion
Box
Docusign
AWS Simple Storage ServiceSmartSuite integration FAQ
How do I add a SmartSuite integration to my product?
Enable the SmartSuite connector in your fastn dashboard, then let each customer authenticate their own SmartSuite account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no SmartSuite client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own SmartSuite account?
Yes. Every connection is scoped to the individual customer, so each authorises their own SmartSuite account and only ever sees their own work items, assignees and due dates. 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 SmartSuite 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 records from a nominated application to answer a question about current work.
Who maintains the SmartSuite integration?
fastn does. When SmartSuite 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 my product create and update work in SmartSuite automatically?
Yes. Items can be created, updated, assigned and transitioned from your product, and changes made in SmartSuite can trigger your workflows in return.
Does it adapt to each team's own SmartSuite setup?
Yes. However a team has configured SmartSuite, whether that is custom fields, statuses and workflow stages or its own calendars and working hours, those are mapped per customer, so an unusual setup works without custom code from you.
What can I build with the SmartSuite integration?
A common starting point: let each customer connect their own SmartSuite workspace so your product writes into the applications they built. 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 SmartSuite integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding SmartSuite does not change your per-connector cost. You can start free with 3 connected accounts.
Add SmartSuite to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.