Data & Storage · Integration
Pigment
Add Pigment to your product for your customers, and give your AI agents governed access to it.
Embed a Pigment integration so your customers can move data in and out of their own planning models from inside your product instead of running exports. Pigment is a business planning platform, and its data lives in blocks: dimension lists, transaction lists, metrics and tables, with a metadata API that tells you what a given application actually contains. Every model is built to the business, so block and field mapping is configuration per customer rather than code, and large imports and exports are paginated and throttled so a first load does not exhaust an allowance. fastn handles per-customer credentials and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own Pigment workspace so your product reads the lists, metrics and tables they plan with.
Write actuals or updated figures into a block so a plan reflects what your product knows.
Read block metadata per tenant so your setup screens show that customer's real model instead of a hard-coded list.
Handle each customer's own model structure as mapping rather than a release on your side when they change it.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads metric values across a model before summarising a variance.
An agent writes an updated figure into a block within governed permissions, with the change logged.
An agent reacts to a completed import and reports what landed.
Example prompt
Compare the current forecast metric with actuals and list the largest gaps by dimension.
Set up Pigment in 4 steps
- 01Open the Pigment connector from your fastn dashboard.
- 02Have each customer authorise their own Pigment workspace.
- 03Use the metadata API to map the blocks, lists and metrics your product reads and 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 Pigment integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Pigment integration without building it. Your customers connect their own Pigment 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 Pigment update is not your on-call problem.
- One integration serves your product and your agents. The same governed Pigment 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
Anaplan
SnowflakeWorks well with
NetSuiteOften used alongside
Tools the same teams tend to run next to Pigment, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FacePigment integration FAQ
How do I add a Pigment integration to my product?
Enable the Pigment connector in your fastn dashboard, then let each customer authenticate their own Pigment account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Pigment client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Pigment account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Pigment 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 Pigment 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 metric values across a model before summarising a variance.
Who maintains the Pigment integration?
fastn does. When Pigment 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 Pigment 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 Pigment 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 Pigment integration?
A common starting point: connect their own Pigment workspace so your product reads the lists, metrics and tables they plan with. 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 Pigment integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Pigment does not change your per-connector cost. You can start free with 3 connected accounts.
Add Pigment to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.