ChatGPT and Claude Connectors
Use ChatGPT or Claude as a conversational front end for your Quali-Fi workspace. Plan surveys in plain language, review drafts in chat, then create or update real surveys, check response metrics, and start open-end coding jobs in your organization — without leaving the assistant you already use.
Quali-Fi remains the system of record. ChatGPT and Claude are the thinking layer; Quali-Fi is the execution layer. Nothing is saved to your account until a write action runs (and, for ChatGPT, until you confirm).
Note
This is different from Rhoxi inside Quali-Fi. Rhoxi Research Agent lives in your organization dashboard and uses approval drafts before changes apply. ChatGPT and Claude connectors work in those external apps and follow their own connect and confirmation patterns. See Rhoxi Research Agent (Beta) for the in-app experience.
What connecting does
When you connect your Quali-Fi account:
- The assistant can read surveys you are allowed to see (list, details, response counts, completion rates).
- The assistant can write to Quali-Fi when you approve (create or update surveys, change status, start open-end coding — subject to your role and plan).
- Access is scoped to your Quali-Fi user and your organization. The assistant cannot act outside that boundary.
Typical workflow:
- Describe what you need (audience, length, draft vs. live).
- Review outlines and wording in chat.
- Confirm when you want changes saved in Quali-Fi.
- Spot-check in the Quali-Fi survey builder or test link before you distribute.
Prerequisites
For everyone
| Requirement | Details |
|---|---|
| Quali-Fi account | Active user in your organization |
| Permissions | View or manage surveys depending on what you ask the assistant to do (see Permissions) |
| External AI account | ChatGPT or Claude plan that supports Custom GPTs or custom connectors (typically Plus, Team, or Enterprise tiers) |
For ChatGPT (organization setup)
Your organization needs the API Access package feature enabled. An org admin generates OAuth credentials in Quali-Fi and builds a Custom GPT (for example, Quali-Fi Survey Assistant) that your team opens in ChatGPT.
If API Access is not on your plan, admins see a message that REST APIs are not enabled when they open API Access in admin settings. Contact your Quali-Fi account team to upgrade.
For Claude
Each user adds a custom connector in Claude using an MCP server URL provided by your administrator. You do not paste org credentials into Claude — you sign in with your own Quali-Fi email and password when Claude asks to connect.
Claude connector availability depends on your Quali-Fi environment. If connect fails with a connector error, your administrator may need to enable the Claude connector for that environment.
ChatGPT vs. Claude at a glance
| ChatGPT (Custom GPT) | Claude (connector) | |
|---|---|---|
| Who sets it up | Org admin creates the GPT once; users open a shared link | Each user adds the connector in Claude settings |
| Org credentials | Admin copies Client ID and Client Secret from API Access into the GPT Actions setup | Not required for users |
| Sign-in | Per user, when ChatGPT prompts during a chat | Per user, Connect on the connector |
| Confirmation before writes | Assistant asks “Do you want me to do this inside Quali-Fi?” before saving | You approve Claude’s tool step; Quali-Fi runs the write when you allow the tool |
| Create full question sets in one step | Yes — supported question types only (see below) | No — creates survey metadata; add questions in Quali-Fi builder |
| Edit a single question | Yes | Not yet — use Quali-Fi builder or ChatGPT |
What you can do after connecting
View and explore (read)
These do not change your data.
| Goal | Example prompts |
|---|---|
| List surveys | “Show my surveys.” / “List active surveys.” |
| Open one survey | “Show details for [survey title or id].” |
| Check performance | “How many responses does [survey] have?” / “What’s the completion rate?” |
| Coding job status | “What’s the status of coding job [id]?” |
Create and change (write)
You need manage-level permissions for these. ChatGPT also requires a clear “yes” after it asks to save in Quali-Fi.
| Goal | Example prompts |
|---|---|
| Create a survey | “Create a private draft titled Employee Pulse with these questions…” |
| Update title or status | “Rename [survey] to …” / “Set [survey] to active.” / “Pause [survey].” |
| Edit one question (ChatGPT) | “In [survey], change the question ‘How satisfied are you?’ to …” |
| Open-end coding | “Start an open-end coding job for [survey / question]…” (requires plan entitlement) |
After a successful create, the assistant may return test or live survey links. Always preview in Quali-Fi before wide distribution.
Survey statuses you can work with
draft, active, paused, closed, and archived. Visibility is typically private or public.
Supported question types (ChatGPT create/update)
When creating or updating surveys through ChatGPT, only these builder types are supported:
| Builder type | Use when |
|---|---|
| Information Block | Instructions or context (not answered) |
| Yes/No | Binary yes / no |
| Single Choice | Pick exactly one option |
| Multiple Choice | Select all that apply |
| Short Text | Short written answer |
| Long Text | Longer written answer |
Choice questions need at least two options. For matrix, ranking, conjoint, and other advanced types, finish the survey in the Survey Builder or use Rhoxi inside Quali-Fi.
Brainstorm only (nothing saved)
Say explicitly that you are not ready to save yet:
- “Draft a 5-minute onboarding survey. Don’t create it in Quali-Fi.”
- “Rewrite this question shorter. Stay in chat only.”
Connect with ChatGPT
For administrators — set up the Custom GPT
Do this once per Quali-Fi environment (for example, staging vs. production). Use separate GPTs and credentials for each — never reuse secrets across environments.
Sign in to Quali-Fi as an org admin and open Admin Settings → API Access (or go to API Access from the admin sidebar).
Click Generate credentials or Rotate credentials. Copy the Client ID and Client Secret. The secret is shown only once — store it in a password manager. Do not paste secrets into chat or email.
In ChatGPT, go to GPTs → Create and open the Configure tab.
Set a name such as Quali-Fi Survey Assistant and a short description (for example, “Plan surveys in chat, then create them in Quali-Fi when you confirm.”).
Paste the full GPT instructions your Quali-Fi deployment provides for Custom GPT setup (your account team or internal admin docs). Do not shorten the confirmation rules.
Under Actions, import the OpenAPI schema for ChatGPT Actions from your Quali-Fi API Access / public API documentation. Confirm the server URL matches your organization’s Quali-Fi API host.
Configure Authentication as OAuth using the Client ID and Client Secret from API Access. Use scopes surveys:read and surveys:write. Set the authorization and token URLs from your API documentation (shown on the API Access page and public API reference).
When ChatGPT shows an OAuth Callback URL, you do not register it inside Quali-Fi — Quali-Fi allows standard ChatGPT callback patterns automatically.
Add the Quali-Fi privacy policy URL if ChatGPT requires one: https://www.qfisolutions.io/privacy-policy
Share the GPT (Anyone with a link is typical for org use) and send the link to your team.
Warning
Rotating credentials in API Access breaks the GPT until you update Client ID and Client Secret in ChatGPT Actions.
For users — connect your account in ChatGPT
Open the Quali-Fi Survey Assistant (or your org’s Custom GPT) link from your administrator.
Start a chat that needs Quali-Fi data, for example: “List my surveys.”
When ChatGPT asks to sign in, continue to the Quali-Fi sign-in page.
Enter your Quali-Fi email and password.
Review the requested access on the Approve access screen and click Approve, or Cancel to decline.
You return to ChatGPT. Your session is linked to your Quali-Fi organization.
You can identify surveys by id, slug, or exact title (title must be unique in your org).
Connect with Claude
On Claude.ai (or Claude Desktop), open Settings → Connectors (sometimes under Capabilities).
Click Add custom connector (or Add connector).
Enter a display name such as Q-Fi or Quali-Fi Surveys.
Paste the MCP server URL from your administrator (must be HTTPS and end with /mcp).
Save the connector.
On the connector row, click Connect.
When Claude opens Quali-Fi in the browser, sign in with your Quali-Fi email and password.
Review access and click Approve, or cancel on the consent screen.
Return to Claude. The connector should show as connected.
In a new chat, enable the Q-Fi connector if Claude asks which tools to use, then try: “List my Quali-Fi surveys.”
Practical pattern with Claude today: draft questions in chat, create a private draft survey when ready, then open Quali-Fi and add questions in the builder. Use Claude again for metrics, status changes, or coding jobs.
Tip
Label connectors clearly if you have access to more than one environment (for example, “Q-Fi staging” vs. “Q-Fi production”) so you do not mix accounts.
Permissions
Your Quali-Fi role controls what the connectors can do. Access is evaluated as you, not as a blanket org admin unless your role includes those permissions.
| Action type | Typical permissions needed |
|---|---|
| List / get surveys, metrics, coding status | One of: view reports, view org analytics, manage surveys, manage projects, manage org settings, manage org users |
| Create / update surveys, update questions (ChatGPT), start coding jobs | One of: manage surveys, manage projects, manage org settings, manage org users |
Open-end coding also requires your organization’s open-end coding entitlement. If coding fails with a permission or entitlement message, contact your Quali-Fi admin.
Security and privacy
- Connectors use OAuth. You sign in with your Quali-Fi credentials and explicitly Approve access on the consent screen.
- Survey and response data accessed through connectors stays within your organization’s boundary for your user.
- Do not paste passwords, API secrets, or OAuth client secrets into ChatGPT or Claude chats.
- Prefer summarizing respondent themes over pasting large amounts of personal data into external AI chats when it is not necessary.
- API and connector traffic is rate-limited (about 30 requests per minute per organization). If many actions fail in a burst, wait a minute and retry.
Disconnecting
- ChatGPT: Remove or disconnect the Custom GPT’s Actions authentication in the GPT editor, or stop using the shared GPT link. Org admins can Rotate credentials under API Access to invalidate org-level OAuth clients used by the GPT (this affects all users of that GPT until credentials are updated in ChatGPT).
- Claude: Open Settings → Connectors, disconnect or remove the Quali-Fi connector. Use Reconnect if your token expired and you want to sign in again.
If you approved access by mistake, disconnect on the assistant side and ask your admin whether org credentials should be rotated.
Limitations
Connectors are powerful for common survey workflows but do not replace the full Quali-Fi app:
- ChatGPT cannot use unsupported question types in create/update actions.
- Claude cannot add or edit individual questions via the connector yet — use the Quali-Fi builder after creating a draft shell.
- Neither connector replaces deep analytics, full report builder workflows, campaign sending, or admin configuration.
- Rhoxi inside Quali-Fi supports broader in-app actions (translations, focus group study creation, deploy how-tos) with approval drafts — see Rhoxi Research Agent (Beta).
Troubleshooting
| Symptom | What to try |
|---|---|
| Cannot open API Access or “REST APIs not enabled” | Your org needs the API Access package feature. Ask your admin or account team. |
| ChatGPT never asks to sign in | Confirm the GPT has Actions and OAuth configured, and ask for something that needs Quali-Fi (for example “List my surveys”). |
| Sign-in works, then errors on actions | Client ID/secret in the GPT must match the current credentials in API Access. After rotation, update the GPT. |
| Wrong or empty survey list | You may be connected to a different environment or signed in as a different Quali-Fi user. |
| Permission or entitlement errors | Your role or plan may not allow the action. See Permissions. |
| ChatGPT created a survey while you were drafting | Say you are brainstorming only. The GPT should ask before saving. |
| Claude connector cannot be added | Confirm the MCP URL is HTTPS, includes /mcp, and matches what your admin provided. |
| Claude connect fails after sign-in | Claude connector may not be enabled for your Quali-Fi environment — contact your administrator. |
| Claude created a survey with no questions | Expected today — add questions in the Quali-Fi survey builder. |
| Burst of failures | Wait about one minute (rate limit) and retry. |
Related documentation
- API Overview — REST API access, credentials, and developer integrations
- Rhoxi Research Agent (Beta) — in-app AI workspace with approval drafts
- Creating Surveys with Rhoxi AI — Word import on New Survey
- Creating Surveys — build surveys in Quali-Fi
- Survey Analytics — review responses after fielding
- Open-End Coding Studio — coding workflows in Quali-Fi
- Zapier Integration — automate on survey events