Productivity · Integration
SciNote
Add SciNote to your product for your customers, and give your AI agents governed access to it.
SciNote is an electronic lab notebook, so the work it holds is arranged as projects, the experiments inside them, and the tasks that make up each experiment, with protocols describing the steps and results attached as the evidence. An embedded SciNote integration matters when your product is upstream or downstream of bench work: an instrument reading, a sample record or a calculation can be written into the task it belongs to, and the inventory items a task consumed can be read back. Two practical points. SciNote can be run in the cloud or self hosted, so each customer supplies their own base URL and token. And a notebook entry is evidence, so results are versioned and reads and writes are attributable rather than anonymous. fastn holds the per-tenant credentials and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own SciNote instance, cloud or self hosted, by supplying their base URL and token.
Write a result or a measurement into the task it belongs to, so evidence lands in the notebook rather than in an attachment somewhere else.
Read projects, experiments and task state so your product can show where a piece of work has actually got to.
Read the inventory items a task used so your product can trace a result back to the samples and reagents behind it.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which experiments in one team's projects have tasks still open and how long they have been there.
An agent writes a result into a task within governed permissions, with the write attributed to the user who authorised it.
An agent reads a protocol and its steps before answering how a measurement was produced.
Example prompt
In this project, which experiments have open tasks, and which results were added in the last week?
Set up SciNote in 4 steps
- 01Enable the SciNote connector in your fastn dashboard.
- 02Have each customer supply their own SciNote base URL and API token, since instances can be cloud or self hosted.
- 03Map the project, experiment, task, protocol and result fields your product uses, plus the inventory repositories you read.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the SciNote integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a SciNote integration without building it. Your customers connect their own SciNote 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 SciNote update is not your on-call problem.
- One integration serves your product and your agents. The same governed SciNote 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
Works well with
Notion
Confluence
AirtableOften used alongside
Tools the same teams tend to run next to SciNote, across other categories.
Box
Docusign
AWS Simple Storage Service
Adobe Acrobat SignSciNote integration FAQ
How do I add a SciNote integration to my product?
Enable the SciNote connector in your fastn dashboard, then let each customer authenticate their own SciNote account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no SciNote client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own SciNote account?
Yes. Every connection is scoped to the individual customer, so each authorises their own SciNote 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 SciNote 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 reports which experiments in one team's projects have tasks still open and how long they have been there.
Who maintains the SciNote integration?
fastn does. When SciNote 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 SciNote automatically?
Yes. Items can be created, updated, assigned and transitioned from your product, and changes made in SciNote can trigger your workflows in return.
Does it adapt to each team's own SciNote setup?
Yes. However a team has configured SciNote, 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 SciNote integration?
A common starting point: let each customer connect their own SciNote instance, cloud or self hosted, by supplying their base URL and token. 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 SciNote integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding SciNote does not change your per-connector cost. You can start free with 3 connected accounts.
Add SciNote to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.