Minds in Zapier: private integration and creative drafts

The Minds Zapier app connects automation to canonical Minds Audiences and Studies. Minds is the end-to-end platform for commercial synthetic research, with qualitative and quantitative work in one connected platform. The app is private; a public Zapier App Directory release has not been established. The creative extension reuses the existing Minds registration rather than creating a duplicate integration.

Registration, versions and release status

Status checked on 2026-10-01. Existing integration 246865 remains the registered Minds app. Version 1.0.0 is private with one Zap user; private 1.2.0 adds Review URL output and Get Completed Research Results. A real hosted 1.2.0 invocation created a private QA Study, saved a draft with its review link, and returned no results before confirmation. This is hosted-runtime evidence, not a claim of native Zap editor acceptance or public listing approval. Existing users were not automatically migrated.

Version 1.2.0 validation returned 27 passing checks and no publishing warnings. Its general D004 warning reflects a Draft Plan ID mapped from Preview Research Plan rather than a separate draft-list endpoint. Public promotion reported S001: at least three users with live Zaps are required, while the registration currently has one. This is a genuine-usage requirement. Build useful Zaps for real testers; do not fabricate accounts or events to pass publication checks.

A successful push or validation is not provider approval. Private distribution, version migration, promotion and public directory review are separate operations.

Prerequisites and secure connection

You need a Zapier account with authorized private-app access, a Minds account and a Minds API key issued through the supported API-key settings. Create an existing Study with the intended Audience before previewing research. Verify that the key belongs to the intended account and workspace.

Enter the key only in Zapier's native Minds connection form. Do not place it in a research request, asset URL, Zap title, guide or screenshot. Zapier uses API-key authentication, while the Canva, Figma and Adobe panels use an OAuth gateway; these are separate connection mechanisms.

The app owner provides tester access through Zapier. Keep private invitation links out of public documentation. Check the version shown in the editor before mapping fields from the creative extension.

Existing operations

New Study polls the newest 100 Studies and uses Study ID for Zapier deduplication. The Audience list supplies existing research populations. Create Study creates the research container, rather than executing respondent research. Find Study locates an existing Study.

Preview Research Plan creates a saved research draft. Get Study Summary reads a generated summary from an existing Study. Check returned status before passing results downstream: a successful creation or preview is not completed research, and a missing summary is not findings.

Build a creative-review Zap

Choose a source trigger for approved material, then add the private Minds Preview Research Plan step. Select an existing Study and map a concrete Research Request and Study Language. Use a question such as: “Which claims in this campaign message need explanation for the Study's Audience?”

The extension accepts either exact text in Material to Review or a readable HTTPS Material URL, never both. When using a URL, choose image, video, document/PDF or webpage as Material Type. Add a short Material Label so a reviewer can recognize the intended asset.

Links requiring sign-in, unreadable resources and URLs with embedded credentials are unsuitable. Do not remove access protection from confidential material to make a Zap work. Use a permitted readable resource or supported owned-source path according to account controls. Minds imports the source while preparing the preview; a saved URL string alone does not prove successful import.

Inspect the draft's source, objective, language and questions. Keep unnecessary private identifiers out of the request and use only material you are permitted to transfer.

Retry identifiers

Preview Request Identifier is an optional stable identity from the source event. Reuse it for retries of the same Study, request and material. Change it when those inputs change. The adapter accepts up to 128 letters, digits, underscores or hyphens.

Without an explicit identifier, do not assume independent Zap retries point to the same draft. Keep source-event identity separate from research outcome. When an upstream trigger replays an event, decide whether the correct action is to retry the existing preview or create a new one.

Confirmation, execution and summaries

Open the exact saved draft in Minds to review its material, questions, Audience and usage before explicitly confirming research. Return only findings from that draft’s completed run. Provider registration and public marketplace approval remain separate gates.

Map the Preview Research Plan output's Study ID and Draft Plan ID into Get Completed Research Results. Share its Review URL with the intended reviewer through your own configured workflow, wait for that reviewer to confirm and complete research in Minds, then test the search. The search returns no item until the run completes; configure your Zap's retry or follow-up schedule accordingly. It does not start research or remain running while a human decides. Pass only completed artifacts and calculations downstream.

Get Study Summary remains a separate operation for existing aggregate Study summaries. Do not substitute it for draft-specific results: that can return findings from earlier research. Test the new search against both a completed draft and a draft that has not run before enabling downstream writes.

Review, confirm and run the saved plan

The saved-draft workflow opens the exact research plan in Minds. The gateway and private Zapier 1.2.0 package return completed findings tied to that draft. Review and execution happen in Minds; public marketplace availability depends on each provider’s registration and approval. Follow these steps:

1. Open Study in Minds from the panel, or open the Review URL returned by Zapier. Sign in to the account that created the draft.
2. Inspect the imported source, research objective, language, every question and the selected Audience. Verify that the material and population match the decision you want to make.
3. Answer any missing-input or clarification questions and save the revised plan. Review the updated questions again; the confirmation applies to that exact revision.
4. Review the available response allowance and estimated usage where the method allows an estimate. Methods that prepare additional questions during execution do not present a false fixed total. Resolve missing Audiences, empty populations or account limits before confirming.
5. Tick the explicit research confirmation. If the plan uses an advanced method, review and accept its separate opt-in. Select Confirm and run once. Opening the link, importing material and previewing a plan do not execute research.
6. Follow this run's queued, running, completed or failed status. Reloading the same draft resumes its confirmed run rather than creating another one. Before confirmation, reloading requires fresh consent. An error preserves the saved draft for inspection and retry.
7. Return to the original panel and select Load findings, or use Zapier's Get Completed Research Results search with the saved Study ID and Draft Plan ID. Only completed results from this draft's confirmed run are returned. Incomplete, failed or missing runs do not fall back to an older Study summary.

Keep the original panel open while research runs. Its short-lived connection and draft selection live in memory. Reloading the host panel or reconnecting may require selecting material and drafting again. The saved draft and its confirmed run remain in Minds even when the panel session ends. Return to the Study in Minds to inspect retained results.

Private testing and timing

Test the actual triggers, actions and searches used by the workflow. Cover invalid authentication, missing Study access, unreadable sources, wrong type, repeated events and missing summaries. Keep test material anonymized and avoid copying private step payloads into tickets.

Zapier applies execution-time limits to polling, action and search steps. Use bounded requests and inspect timeouts rather than blindly rerunning planning. Coordinate private migration with the app owner: pushing a new package does not move every user to it. Revoke unused keys through the native account controls and manage retained material under the Minds privacy policy.

Troubleshooting

Publication gates and related guides

Finish genuine private-user validation, supported preview-to-execution handling, reviewer access and publication checks before directory submission. Re-run checks for the exact promoted version; a previous package's result is not approval for its successor. Do not label the private integration public or create artificial usage to clear the gate.

Read Zapier integration checks and publishing requirements. Compare Canva, Figma Creative Review, Adobe Express, GenStudio and the integration directory.