NewLink Testing catches survey errors before fieldwork.Try it free

Program and test surveys from your AI assistant.

Connect Questra to Claude, Codex, or Slack. Ask in plain language, and your assistant uploads the questionnaire, brings you Questra’s clarifying questions, confirms the price with you, and returns a tester link.

Read the setup guide
  1. Program this yogurt survey on Decipher, and link test it once it’s built.

    Yogurt survey.docx
  2. Calls Questra tool create_surveyCalls Questra tool create_upload_urlCalls Questra tool get_clarifying_questions

  3. Assistant

    Questra has a question before programming: the S6 termination mentions cereal, but S6 has no cereal option. How should it work?

    • Terminate if “Cereal” isn’t selected at S5
    • Terminate if “Cereal” isn’t selected at S6

COMMON REQUESTS

Program, test, and edit surveys by asking.

Your assistant calls Questra’s tools for each request and reports back in the chat. Pick a request to see how it goes.

  1. Use S5 for the cereal termination. Program it on our Questra Decipher account.

  2. Assistant

    Standard programming is 4 credits, and link testing at that tier is 2 credits for 5 runs. Finish programming on Decipher for 6 credits?

  3. Yes, finish programming.

  4. Assistant

    Done. Yogurt survey is saved to Decipher, with code review and the first link test run. I’ll send you a preview link for testers; they don’t need a Questra login.

YOUR ASSISTANT

Works with any AI assistant that supports MCP.

MCP is the open standard AI assistants use to connect to tools, so Questra works with whichever one your team already uses. Register Questra’s MCP server and sign in with your Questra account. There’s no API key to manage.

https://api.program.questra.ai/mcp
  • Claude

    Claude Desktop and Claude.ai

    1. Open Settings and add a custom connector.
    2. Paste the MCP URL.
    3. Sign in to Questra in the browser.
  • Codex

    Added in config.toml

    [mcp_servers.questra]
    url = "https://api.program.questra.ai/mcp"
    
    $ codex mcp login questra
  • Slack AI

    Slackbot in your workspace

    1. An admin adds the MCP URL to a Slack app, with Dynamic Client Registration.
    2. Members sign in to Questra the first time they ask Slackbot to use it.
  • Any MCP assistant

    ChatGPT, Cursor, VS Code, and more

    1. Add a remote MCP server with the MCP URL.
    2. Sign in to Questra in the browser.
Step-by-step setup for each assistant

YOU STAY IN CONTROL

Your assistant asks before it acts.

The decisions that shape a study, and anything that spends credits, come back to you in the chat.

  • Clarifying questions wait for you.

    Your assistant brings you every question Questra finds in the questionnaire and waits for your answers, rather than guessing.

  • You choose where it’s programmed.

    It asks which platform and account to use before programming, even when you have only one connected.

  • No credits without your OK.

    Analysis is free. Programming and link-testing runs start only after you confirm the quote.

  • Status and links, not source.

    You sign in as yourself. The assistant sees survey status, questions and preview links, never platform source code or integration secrets.

REST API

Building your own integration? Use the API.

Use the REST API with a workspace key for scripts, backends, and CI.

Read the API reference

CONNECT YOUR ASSISTANT

Your next survey, one message away.

Sign up, then add Questra to your assistant. See how.