> ## Documentation Index
> Fetch the complete documentation index at: https://developers.scrunch.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Bulk Prompt Import from a Spreadsheet
> Read a spreadsheet of seed queries, tags, and personas you already have and bulk-create them as tracked Scrunch prompts in one conversation.
Most teams don't start from zero — there's already a spreadsheet somewhere with a curated list of queries a client cares about, or one inherited from a previous tool. This workflow reads that spreadsheet directly and creates every row as a tracked Scrunch prompt, instead of re-typing the list one by one.
**Tools used in this workflow**
| Tool | Required? | Used for |
| ------------------------------ | --------------------- | ----------------------------------------- |
| Google Sheets MCP or Excel MCP | Required (choose one) | Reading the source list of queries |
| Scrunch MCP | Required | Bulk-creating prompts, tags, and personas |
***
Replace the bracketed values, then paste the whole thing into Claude.
```text theme={null}
For [brand name] in Scrunch, bulk-import the prompt list from [spreadsheet name or URL].
Step 1 — Read the source list:
Open [spreadsheet name or URL] and read the [sheet/tab name] tab. Expect columns for: query text, tag (optional), persona (optional), platform (optional). Show me the first 10 rows so I can confirm the column mapping is right before continuing.
Step 2 — Check for duplicates:
List existing prompt variants for [brand name]. Flag any rows from Step 1 that closely match a prompt that's already tracked, so we don't create duplicates.
Step 3 — Create the new prompts:
For every non-duplicate row, create a Scrunch prompt using the query text. If a tag column has a value, apply that tag (creating it first if it doesn't exist). If a persona column has a value and that persona exists on this brand, assign it.
Step 4 — Confirm:
Summarize: how many prompts were created, how many were skipped as duplicates, and how many tags were newly created versus reused.
```
**What you get:** Every row in the spreadsheet turned into a tracked Scrunch prompt with its tags and persona already applied — a full prompt library migrated from a spreadsheet in one pass instead of hundreds of individual clicks.
Replace the bracketed values, then paste the whole thing into Claude.
```text theme={null}
For [brand name] in Scrunch, bulk-import the prompt list from [workbook name or path].
Step 1 — Read the source list:
Open [workbook name or path] and read the [worksheet name] sheet. Expect columns for: query text, tag (optional), persona (optional), platform (optional). Show me the first 10 rows so I can confirm the column mapping is right before continuing.
Step 2 — Check for duplicates:
List existing prompt variants for [brand name]. Flag any rows from Step 1 that closely match a prompt that's already tracked, so we don't create duplicates.
Step 3 — Create the new prompts:
For every non-duplicate row, create a Scrunch prompt using the query text. If a tag column has a value, apply that tag (creating it first if it doesn't exist). If a persona column has a value and that persona exists on this brand, assign it.
Step 4 — Confirm:
Summarize: how many prompts were created, how many were skipped as duplicates, and how many tags were newly created versus reused.
```
**What you get:** Every row in the workbook turned into a tracked Scrunch prompt with its tags and persona already applied — a full prompt library migrated from a spreadsheet in one pass instead of hundreds of individual clicks.
***
## Tips
Step 1 deliberately stops to show you a preview before creating anything — spreadsheets inherited from another tool or another teammate don't always have consistent column names, so it's worth a quick sanity check before hundreds of prompts get created from a misread column.
For lists longer than a few hundred rows, ask Claude to process and confirm in batches of 100 rather than all at once — it's easier to catch and fix a mapping error early than to discover it after everything's already been created.
This workflow works fine with just a query column — tags and personas are optional. You can always run the Configuration & Maintenance prompts afterward to apply tags in bulk once everything's imported.
If you're moving brands, competitors, and personas over as well — not just the prompt list — use the Switch from Another AI Visibility Tool workflow instead; it covers the full migration in one pass.
***
For a full account migration, not just the prompt list.
Pair this with brand and competitor setup when onboarding from scratch.