Data & Storage · Integration
kintone
Add kintone to your product for your customers, and give your AI agents governed access to it.
Embed a kintone integration so your customers can work their own apps and records from inside your product rather than switching between tools. Every app is built by the team that uses it, so its fields differ per customer and change without notice, which is why field mapping is configuration rather than code. fastn handles per-customer authentication, pagination, and throttling, so a large read is paged for you.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers read records from their own apps into your product, mapped to their fields.
Create and update records from your product so users do not re-enter data.
Read an app's field definitions at runtime so your product adapts to each customer's app.
Trigger your workflows when a record is added or updated.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads records from an app to ground an answer in the customer's own data.
An agent inspects an app's fields before it writes, so it uses fields that exist.
An agent creates or updates a record within governed permissions, with every write logged per tenant.
Example prompt
Find records in this app with no assignee that were created more than three days ago.
Set up kintone in 4 steps
- 01Open the kintone connector from your fastn dashboard.
- 02Have each customer authenticate their own kintone subdomain and select apps.
- 03Map the apps and fields your product reads or writes, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the kintone integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a kintone integration without building it. Your customers connect their own kintone 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 kintone update is not your on-call problem.
- One integration serves your product and your agents. The same governed kintone 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
Compare with
Airtable
PostgreSQLWorks well with
NotionOften used alongside
Tools the same teams tend to run next to kintone, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging Facekintone integration FAQ
How do I add a kintone integration to my product?
Enable the kintone connector in your fastn dashboard, then let each customer authenticate their own kintone account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no kintone client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own kintone account?
Yes. Every connection is scoped to the individual customer, so each authorises their own kintone 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 kintone 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 an app to ground an answer in the customer's own data.
Who maintains the kintone integration?
fastn does. When kintone 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 kintone 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 kintone 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 kintone integration?
A common starting point: read records from their own apps into your product, mapped to their fields. 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 kintone integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding kintone does not change your per-connector cost. You can start free with 3 connected accounts.
Add kintone to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.