--- title: "How Kalpana works" description: "From Figma frame to finished campaign: your designer sends the design, your team adds the product sheet, fixes photos and previews every row before paying." url: https://kalpana.one/how-it-works --- # How Kalpana works Your designer works in Figma; your team works in Kalpana. The layout rules your designer set apply to every row of data, and every row is previewed before you pay for it. 1. Design (your designer, in Figma). The Figma frame becomes a template. Send it with the plugin; auto-layout, fonts and effects arrive intact, and the layers that change per row are marked once. Nobody else needs to open Figma. 2. Data (your team, in Kalpana). Upload a CSV or paste rows from Excel or Google Sheets. Columns match the template's layers by name, and a campaign feed runs the same rows through every template, one per size. 3. Fix photos (when a photo needs it). Click a row's image to remove the background, expand it to a new ratio, upscale it, edit it with a prompt or put a garment on a model. The fixed photo fills that row. 4. Preview (free). See any row on the same engine that makes the final files, fix a price or a photo in the batch grid, then generate. Credits are used only when a creative finishes. 5. Deliver. Download ZIPs or save to Google Drive, Dropbox or OneDrive. File names come from a column in your sheet. ## Product facts - Imports designs from Figma with a plugin, keeping layers, fonts, effects and auto-layout. - Re-resolves auto-layout for every data row; text can auto-fit to a minimum size. - Data sources: Shopify, Google Sheets, CSV or TSV upload, and rows pasted from a spreadsheet. Airtable bases can be connected, but record import is not released yet. Connections are read-only. - Kalpana stores your assets and finished creatives itself. Each workspace has an asset library for product images, logos and fonts. Storage is included in every plan for the whole organisation (10 GB to 750 GB, more as an add-on). Finished creatives stay in Kalpana and download as ZIP packs named from your data. - Google Drive, Dropbox and OneDrive are optional integrations: import images from them into the asset library, or save finished creatives out to a folder. Kalpana does not depend on them. - Images used in a batch come from the Kalpana asset library. Public image URLs in a campaign-feed CSV are downloaded into the library first, so nothing is fetched from an external link at render time. - Batches are validated first, then created, then run. Only running uses credits. - Outputs: PNG, JPEG or WebP for still templates; MP4, GIF or animated WebP for animated ones. Video runs up to 30 seconds and has no audio. - Each template renders at the size it was designed at. Kalpana does not resize a template to other sizes; each extra size is its own template, or its own page of one template. - Campaign feeds: one product feed run through several templates in one batch. - AI image editing: background removal, upscale (2x or 4x), generative expand to a new ratio, prompt edits with reference images and virtual try-on, plus free colour expansion, crop and resize. Each tool opens from the asset library or from a batch row's image, and the result fills that row as a new image in the library. - Roles: the designer sends frames from Figma; Managers and Owners fill rows, fix photos and run batches in Kalpana without opening Figma. Designers manage templates and assets but do not run batches. - REST API: https://app.kalpana.one/api (API key via x-api-key header). Reference: https://docs.kalpana.one/api-reference. - AI agents: two MCP servers, each over OAuth and scoped to the one workspace chosen when connecting. They work with Claude, ChatGPT, Grok, Claude Code, Codex and Cursor, and a template's id is the same on both. In Claude, add them from the Claude directory: Kalpana Batch (https://claude.ai/directory/kalpana-batch) and Kalpana Designer (https://claude.ai/directory/kalpana-designer). In the official MCP Registry they are one.kalpana/batch and one.kalpana/designer. - Batch MCP server at https://mcp.kalpana.one/mcp/batch (18 tools): find templates and assets, validate rows, create, edit, run and cancel batches, and fetch outputs. Only run_batch uses credits. - Designer MCP server at https://mcp.kalpana.one/mcp/designer (41 tools): an agent creates and edits templates with layers, layout flows, fonts from Kalpana's library, workspace images, pages per size and motion, and checks them with a layout check and rendered previews. It does not render batches or export video; the batch server and the app do. - Not available yet: direct publishing to Meta or Google Ads; Zapier, Make or n8n apps. ## FAQ **Who does what in Kalpana?** Your designer designs in Figma and sends frames with the plugin. A Manager or Owner adds the product rows, fixes photos, previews and runs the batches. Reviewers check the outputs and Viewers can only look. Designers manage templates and assets but do not run batches. **Does my marketing team need to learn Figma?** No. Only the designer works in Figma. Everything after the plugin, from filling rows to fixing photos and generating, happens in Kalpana. **Can Kalpana publish to Meta or Google Ads?** Not yet. Today you download the pack or save it to cloud storage, then upload it to your ad platform. **Is there a REST API?** Yes. Create a key in Settings, under API Keys, and call the REST API to find templates, validate rows, run batches and fetch outputs. Zapier, Make and n8n apps are not available yet. **Does Kalpana design for me?** Not on its own. Templates come from Figma, the template editor or the gallery, and Kalpana fills them for every row. If you connect an AI agent such as Claude or ChatGPT to the Kalpana designer MCP, the agent can design templates in your workspace with Kalpana's design tools; you can then edit them like any other. **Which formats can it produce?** PNG, JPEG or WebP for still templates; MP4, GIF or animated WebP for animated ones. Video runs up to 30 seconds and has no audio. Each template renders at the size it was designed at, so each extra size is its own template or template page.