Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.conversion.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
General

Conversion AI is connected to your workspace. It can read your contacts, audiences, emails, forms, workflows, and campaigns, and it can create or edit those assets through previews you approve. A generic chatbot doesn’t know anything about your data; Conversion AI does.
No. Conversion AI cannot send a blast on its own. Blasts always land in draft and you publish them yourself. For anything that creates or edits an asset (other than building previews), Conversion AI asks for an explicit approval before it runs. See Approvals.
No. Each chat is independent. There’s no shared memory across chats today.
No. Conversion AI cannot delete contacts, audiences, emails, forms, workflows, campaigns, folders, fields, or tokens. If you ask, it’ll tell you it can’t and that you’ll need to do it from the UI.
No. Every workflow artifact creates a new workflow. To replace an existing workflow’s behavior, apply the new one and deactivate (or rebuild against) the old one yourself.

​
Files and uploads

5 MB per file. Files larger than that are rejected when you try to attach them. There’s no fixed limit on the number of files per message, only the per-file size cap.
Images (JPEG, PNG, GIF, WebP), PDFs, and text-based formats (CSV, TSV, JSON, XML, YAML, plain text, code files, and similar). Conversion AI reads these directly.Other formats (like .xlsx or .zip) are dropped from the message itself, but the file is still saved to the sandbox at /vercel/sandbox/uploads/. You can still ask Conversion AI to open it with a script.See Files and sandbox for the full breakdown.
Yes. CSVs and TSVs are read as text. For large CSVs, Conversion AI typically opens them in its sandbox with Python and processes them there before answering.
Yes. Conversion AI reads PDFs directly, including text and embedded images.
Yes. Conversion AI can see and reason about images you attach. For example, “use this logo’s color palette” or “what’s wrong with this email screenshot”.
When Conversion AI generates a file, it surfaces it as a card in the chat with view and download actions. You don’t need to go anywhere else for it.

​
Sandbox and code

Yes. Conversion AI has a Linux sandbox with bash, Python 3.12+, and Node.js 20+. It uses the sandbox when a task needs real computation, like parsing a large file, generating a chart, or building a downloadable report.It also avoids writing code when a tool call would do. For example, “how many contacts match this filter?” is answered with a tool call, not a script.
Yes. The sandbox has network access. Conversion AI sticks to well-known libraries (e.g. pandas, openpyxl, requests).
No. The sandbox is isolated. Conversion AI uses tool calls to read or change anything in your workspace. The sandbox is just for files and scripts.
Within a single chat, files in the sandbox persist across messages, so Conversion AI can save something now and use it next turn. Between chats, sandboxes are separate. Don’t rely on the sandbox for long-term storage; if you want to keep a file, download it.

​
Artifacts and approvals

For emails, forms, and workflows, the change is significant enough that you should see it before it lands. Previews (called artifacts) let you review, edit, and revise before you commit. Once you apply, the change takes effect.
Yes. Open the artifact card to see the full editor for that asset type. You can edit directly there, and Conversion AI will see your edits the next time you message it.
It’s locked. Further changes go through a new preview that Conversion AI links to the now-live asset.
Renames change a live asset directly. There’s no preview step. The approval is the only chance to catch a wrong name before it lands. Artifact creation, by contrast, doesn’t ask for approval because the artifact itself is just a preview; the approval is on the apply instead.