Business Intelligence · Beta

Pigment
API integration

Ship Business Intelligence features without building the integration. Full Pigment API access via Proxy and 10+ MCP-ready tools for AI agents — extend models and mappings to fit your product.

Built for specific customer use cases. Issues are resolved quickly.

Talk to us

Use Cases

Why integrate with Pigment

Common scenarios for SaaS companies building Pigment integrations for their customers.

Sync HRIS Actuals into Pigment for Headcount Planning

HRIS and payroll platforms can offer customers a native way to push monthly employee census, salary, and benefits data into Pigment, so FP&A teams can run headcount and compensation forecasts without manual CSV handoffs.

Enforce Live Budgets in Spend Management Tools

Spend management and procurement platforms can pull approved departmental budgets directly from Pigment metrics, letting their product flag or block purchase requests that exceed real-time, FP&A-approved limits.

Provision Sales Quotas from Pigment Models

Commission and sales performance tools can extract finalized territory maps and quota lists from Pigment, automatically provisioning new comp plans the moment the CRO finalizes capacity modeling.

Close the Loop on Marketing Spend and Pipeline

Marketing operations and attribution platforms can push campaign spend and pipeline actuals into Pigment, enabling Finance to dynamically model marketing ROI and adjust budgets without waiting for quarter-end reconciliation.

Orchestrate Model Recalculations After Data Loads

Workflow and iPaaS-style products can push operational data into Pigment and immediately trigger data flows to recalculate downstream financial models, giving customers always-fresh forecasts.

What You Can Build

Ship these features with Truto + Pigment

Concrete product features your team can ship faster by leveraging Truto’s Pigment integration instead of building from scratch.

Dynamic Pigment Schema Mapper

Use list_all_pigment_applications, list_all_pigment_blocks, and list_all_pigment_views to render in-product dropdowns so end users map their fields directly to their own Pigment application structure.

Async Bulk CSV Push Pipeline

Ship a background job that calls create_a_pigment_push_csv (or create_a_pigment_file plus create_a_pigment_import_trigger) against a selected import configuration, with polling on get_single_pigment_import_status_by_id to surface row-level errors.

Data Flow Trigger & Status Monitor

Let customers kick off Pigment data flows via create_a_pigment_data_flow_trigger after each sync and display live recalculation status using get_single_pigment_data_flow_status_by_id.

Scheduled Metric & List Exports

Build recurring exports using create_a_pigment_export_metric, create_a_pigment_export_table, and create_a_pigment_export_list to pull approved budgets, quotas, or forecasts into your product on a schedule.

Looker-Backed Push Jobs

For customers with Looker as a source, expose create_a_pigment_push_looker so they can ingest Looker-derived datasets into Pigment import configurations without a separate ETL layer.

Import Configuration Browser

Use list_all_pigment_import_configurations and list_all_pigment_data_flows to let admins pick exactly which import target and downstream flow should run for each sync they configure.

SuperAI

Pigment AI agent tools

Comprehensive AI agent toolset with fine-grained control. Integrates with MCP clients like Cursor and Claude, or frameworks like LangChain.

list_all_pigment_data_flows

List the Data Flows configured in a Pigment application. Returns: dataFlowId, name, description, application_id, steps. Required: application_id.

create_a_pigment_data_flow_trigger

Trigger an execution of a Data Flow in Pigment. Returns: dataFlowExecutionId. Required: dataFlowId. 400 if the Data Flow has no runnable steps; 429 if too many concurrent executions are already running.

create_a_pigment_push_csv

Push a CSV file to a Pigment import configuration. The import starts asynchronously and Returns: importId. Required: configuration_id, file.

create_a_pigment_push_looker

Trigger a Looker Look import in Pigment. Pigment pulls the Look data and runs the import asynchronously. Returns: importId. Required: configuration_id.

list_all_pigment_import_configurations

List Pigment import configurations for the given application and block. Returns: id, name. The returned id is the configurationId needed to trigger imports or push data.

create_a_pigment_import_trigger

Trigger an automated import operation in Pigment for an integration-based import, list data copy or metric data copy; the pipeline type is detected from the configuration. Returns: importId. Required: configuration_id.

list_all_pigment_applications

List metadata for every Pigment Application in the Workspace associated with the API key. Returns each application's id (UUID) and name — the values used to scope the other Pigment metadata calls. The source documents no additional fields or filters for this endpoint.

list_all_pigment_applications_snapshots

List metadata for all application snapshots in Pigment, including scheduled, in progress and failed ones. Returns: id, name, status, date, applications.

list_all_pigment_blocks

List Pigment block metadata (metrics, lists, and tables) for an application. Returns: id, name, type.

get_single_pigment_export_view_by_id

Export the data of a specific Pigment view as a CSV file. Returns the view's data as a CSV file (text/csv). Optional date_format (Legacy or Iso8601) and field_delimiter (Semicolon or Comma) control output formatting. Fails with 413 if the view is too big (use block export APIs instead) or 422 if the view type is not…. Required: id.

create_a_pigment_export_list

Export the data of a specific Pigment list as a CSV file. Returns the exported list data as a CSV file (text/csv). An optional ListRequest JSON body refines the export; sending {} accepts the list's defaults. Required: list_id.

create_a_pigment_export_metric

Export the data of a specific Pigment metric as CSV. Returns the exported data as a CSV file (text/csv). The optional MetricRequest JSON body refines the export; omit it or send an empty object to accept upstream defaults. Required: metric_id.

create_a_pigment_export_table

Export the data of a specific Pigment table as a CSV file. Returns the table's exported data as a CSV file (text/csv), not a JSON object, so its contents are content-type-specific. Optional TableRequest body refines the export; an empty {} body accepts defaults. Required: table_id.

list_all_pigment_files

List the file metadata of a Pigment application with cursor-based pagination. Returns: organizationId, application_id, id, displayFilename, contentType, mimeType, sizeBytes, uploadedBy, uploadedAt. Required: application_id.

create_a_pigment_file

Upload a file to a Pigment application as multipart form-data. Returns the uploaded file's metadata: id, displayFilename, contentType, sizeBytes, uploadedAt. Required: application_id, file.

get_single_pigment_content_by_id

Download a file's content from a Pigment application. Returns the raw file bytes (binary download, not a JSON object). Required: id, application_id.

list_all_pigment_views

List view metadata for a block in Pigment. Returns: id, name, type. Use the returned view ids with the view export endpoint.

get_single_pigment_data_flow_status_by_id

Get the status of a Data Flow execution in Pigment. Returns: dataFlowExecutionId, dataFlowId, status, createdAt, completedAt, steps. Status is InProgress, Completed, PartialFailure, or Failed. Required: id. Rate limited — on 429, retry after the Retry-After delay.

get_single_pigment_import_status_by_id

Get the status of a csv import, integration import, list data copy or metric data copy operation in Pigment by id. Returns: importId, createdAt, completedAt, importStatus, errorsDetails, detailedReport. Required: id. Set included_detailed_report=true for summary statistics; defaults to false.

Why Truto

Why use Truto’s MCP server for Pigment

Other MCP servers give you a static tool list for one app. Truto gives you a managed, multi-tenant MCP infrastructure across 1000+ integrations.

Auto-generated, always up to date

Tools are dynamically generated from curated documentation — not hand-coded. As integrations evolve, tools stay current without manual maintenance.

Fine-grained access control

Scope each MCP server to read-only, write-only, specific methods, or tagged tool groups. Expose only what your AI agent needs — nothing more.

Multi-tenant by design

Each MCP server is scoped to a single connected account with its own credentials. The URL itself is the auth token — no shared secrets, no credential leaking across tenants.

Works with every MCP client

Standard JSON-RPC 2.0 protocol. Paste the URL into Claude, ChatGPT, Cursor, or any MCP-compatible agent framework — tools are discovered automatically.

Built-in auth, rate limits, and error handling

Tool calls execute through Truto’s proxy layer with automatic OAuth refresh, rate-limit handling, and normalized error responses. No raw API plumbing in your agent.

Expiring and auditable servers

Create time-limited MCP servers for contractors or automated workflows. Optional dual-auth requires both the URL and a Truto API token for high-security environments.

How It Works

From zero to integrated

Start with Pigment in a free sandbox, usually ready within one business day. No boilerplate, no maintenance burden.

Link your customer’s Pigment account

Use Truto’s frontend SDK to connect your customer’s Pigment account. We handle all OAuth and API key flows — you don’t need to create the OAuth app.

We handle authentication

Don’t spend time refreshing access tokens or figuring out secure storage. We handle it and inject credentials into every API request.

Call our API, we call Pigment

Truto’s Proxy API is a 1-to-1 mapping of the Pigment API. You call us, we call Pigment, and pass the response back in the same cycle.

Unified response format

Every response follows a single format across all integrations. We translate Pigment’s pagination into unified cursor-based pagination. Data is always in the result attribute.

FAQs

Common questions about Pigment on Truto

Authentication, rate limits, data freshness, and everything else you need to know before you integrate.

How do end users authenticate their Pigment account?

Truto handles the Pigment auth handshake and token storage for you. Your product only needs to launch Truto's connect flow — credentials, refresh, and secure storage are managed on our side.

Can we push large datasets without hitting synchronous timeouts?

Yes. Pigment's import endpoints are asynchronous. You use create_a_pigment_push_csv or create_a_pigment_file + create_a_pigment_import_trigger to submit the data, then poll get_single_pigment_import_status_by_id for completion and row-level errors.

Can we trigger model recalculations after pushing data?

Yes. After an import completes, call create_a_pigment_data_flow_trigger to run the relevant data flow and get_single_pigment_data_flow_status_by_id to monitor the compute job until it finishes.

How do we read planning data back out of Pigment?

Use create_a_pigment_export_metric, create_a_pigment_export_table, or create_a_pigment_export_list with a JSON body that specifies the dimensions you need. Pigment returns structured CSV output you can parse downstream.

How do we handle customers with different Pigment model structures?

Call list_all_pigment_applications, list_all_pigment_blocks, list_all_pigment_views, and list_all_pigment_import_configurations at setup time to discover each tenant's schema, then let the end user map their fields against it in your UI.

Is there a unified BI API we can use instead of Pigment-specific calls?

Not currently. Pigment is available as a native integration with dedicated tools covering imports, exports, data flows, and schema discovery. If you need a unified BI abstraction, reach out and we can prioritize it based on your use case.

From the Blog

Pigment integration guides

Deep dives, architecture guides, and practical tutorials for building Pigment integrations.

Pigment

Get Pigment integrated into your app

Our team understands what it takes to make a Pigment integration successful. A short, crisp 30 minute call with folks who understand the problem.