Skip to main content
If you’ve got a spreadsheet — a vendor list, a content syndication export, a CRM pull — you can import it into an allGood worksheet entirely through a chat with an MCP-connected assistant, instead of using the upload screen. The assistant finds the right template, maps your columns to it, and walks the import through to a running worksheet.
This is a different interaction model from the Marketo MCP tools. Those talk to Marketo directly — programs, emails, tokens. Importing a list works through allGood’s own worksheet model instead: you’re creating and running a worksheet in allGood, and Marketo — if the template’s steps use it — is one of the systems that worksheet acts on, not something these tools touch directly. See the Marketo MCP overview for how to connect an MCP-enabled assistant in the first place.

​
Before you begin

You’ll need:
  • An MCP-connected assistant (Claude Desktop or ChatGPT Desktop)
  • An allGood account with permission to create worksheets
  • A spreadsheet ready to import (CSV or Excel)

​
How this works

The import happens in a session — a place to collect the import’s artifacts. Opening one clones nothing and imports nothing. It costs nothing to start, review, or even abandon. Only one step, committing, actually creates anything in allGood, and that step can’t be undone.

​
Steps

1

Find the right template

Ask the assistant to look up worksheet templates by name, or list every list-upload template if you’re not sure which one fits. It presents candidates for you to confirm. Always confirm the template before moving on — everything after this step depends on it.
2

Review the template's import contract

The assistant fetches the template’s required columns and the column-name aliases it already recognizes, so near-matches in your spreadsheet don’t need manual mapping. It also fetches any worksheet-level settings the template expects.
3

Check for a prior import

Before going further, the assistant checks whether a file with the same name or the same contents has already been imported. This is a warning, not a block — you decide whether to continue.
4

Open an upload session

This creates a place to collect the import’s artifacts. Nothing is created in allGood yet, so abandoning a session here costs nothing.
5

Upload the source file, the canonical CSV, and the manifest

The assistant transforms your spreadsheet into the canonical CSV the template expects, and writes a manifest explaining how it got from one to the other. It then uploads all three — your original file, the CSV, and the manifest — using upload links it requests for this purpose. Your data moves directly to allGood’s file storage, rather than being retyped into the conversation.
Upload links expire a few minutes after they’re issued. If an upload doesn’t complete in time, the assistant requests fresh links rather than reusing old ones.
6

Commit the import

Committing checks the three artifacts against the template’s contract. It then clones the template into a real worksheet, creates one item per row, and starts the worksheet’s configured steps.
This is the point of no return. There’s no undo — make sure you’ve reviewed the mapping and any worksheet-level settings before agreeing to this step.
7

Track progress

Committing returns as soon as the worksheet’s items exist — the worksheet’s steps keep running afterward. Ask the assistant to check the worksheet’s execution summary to see how far along it is.
You’ll see the import finish when the execution summary shows a status and category for every item, and confirms whether anything needs your approval. “Finished” only means nothing is still running — check the category breakdown to confirm items finished well, not just that they stopped.

​
Troubleshooting

This isn’t a hard stop — it just means a file with the same name or the same bytes has come through before. Confirm whether that’s expected (a legitimate re-run) or a mistake before continuing.
Upload links expire quickly. Ask the assistant to request fresh links and try again — the session itself is unaffected.
The backend re-checks all three artifacts before creating anything. The manifest must match the template’s expected shape. The CSV needs unique, non-empty headers covering every column the template requires, and its row count has to match the manifest. If any check fails, nothing is created, and the session records the reason. Ask the assistant what failed, and have it correct the CSV or manifest before retrying.
Worksheet metadata has to be resolved before committing. Anything left unresolved simply won’t be there afterward, even if the template shows a placeholder value in its place. If a step later reads a missing setting, go back and set it explicitly rather than relying on the template’s own default.
If the issue persists, contact allGood support.