Content & Documents · Integration
Zeplin
Add Zeplin to your product for your customers, and give your AI agents governed access to it.
Zeplin's API is at api.zeplin.dev and accepts a personal access token or an OAuth2 token, which catches people out because the product itself sits on zeplin.io. The object graph runs organisation, project, screen and screen version, with styleguides, components and design tokens on a separate branch, so resolving one design reference usually takes two or three calls. Screen versions are immutable snapshots, which is what you compare when you need to know what actually changed between two handoffs. Most resources are read only, with notes among the few write paths, so plan on Zeplin as a source rather than a target. Webhooks fire on project screen and project screen version events and are the practical alternative to polling large projects. fastn holds the per customer token, manages webhook registration and keeps up with 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 Zeplin organisation so their projects and screens are readable inside your tool
Show the latest screen version alongside a linked ticket so developers see the current design without leaving your app
Detect new screen versions through webhooks and notify the owning team that a handoff has changed
Pull styleguide components and design tokens to keep your own component catalogue aligned with the design source
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent what changed between two screen versions and have it summarise the difference for a release note
Let an agent post a note on a screen when an automated check finds a mismatch, with the write audited per tenant
Have an agent list which screens in a project have not been updated since a given date
Example prompt
What changed on the checkout screen in the mobile project since last Tuesday's version?
Set up Zeplin in 4 steps
- 01Enable the Zeplin connector from your fastn dashboard.
- 02Have each customer authorise their own Zeplin 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 Zeplin integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Zeplin integration without building it. Your customers connect their own Zeplin 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 Zeplin update is not your on-call problem.
- One integration serves your product and your agents. The same governed Zeplin 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 Zeplin, across other categories.
Shopify
Stripe
Jira
AsanaZeplin integration FAQ
How do I add a Zeplin integration to my product?
Enable the Zeplin connector in your fastn dashboard, then let each customer authenticate their own Zeplin account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Zeplin client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Zeplin account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Zeplin 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 Zeplin integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Ask an agent what changed between two screen versions and have it summarise the difference for a release note
Who maintains the Zeplin integration?
fastn does. When Zeplin 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 Zeplin integration run under?
Each customer's own Zeplin grant. Where Zeplin 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 Zeplin automatically?
Where Zeplin 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 Zeplin integration?
A common starting point: let a customer connect their own Zeplin organisation so their projects and screens are readable inside your tool. 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 Zeplin integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Zeplin does not change your per-connector cost. You can start free with 3 connected accounts.
Add Zeplin to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.