AI assistants (Claude, ChatGPT, Copilot)
You can use Hashdata straight from an AI assistant such as Claude, ChatGPT or Microsoft 365 Copilot. Once connected, you ask in plain language and the assistant reads or changes the data in your account, always with the same permissions you have in the portal.
Example requests
If you create forms
- "Create a machine inspection checklist from a template and require a photo when the answer is Non-compliant."
- "Make every question in the PPE section required."
- "Show the question 'Describe the deviation' only when the previous one is No."
- "Generate 20 test responses so I can check the scores before publishing."
If you analyze results
- "Compare the average inspection score month by month over the last 3 months."
- "Which questions had the most Non-compliant answers in October?"
- "Generate a PDF with last week's audits from the ABC plant."
- "Change the date of the inspection John submitted yesterday to 11/10."
If you follow up on actions
- "List the overdue actions, grouped by owner."
- "Open the action plan 'Fix the leak on line 3', with Maria as owner and a 30-day deadline."
- "Move the deadline of the action 'Replace the fire extinguisher in warehouse 2' to 12/15."
- "Record the effectiveness verification of that action with today's date."
Ask for the result in the format you will use: a table, a summary for the meeting or a draft email.
Before you start
| What | Who does it |
|---|---|
| Have a plan with AI access. If your plan doesn't include it, contact support | Whoever is responsible for the workspace |
| Set the AI / MCP access option, in the Integrations menu, to Access enabled. It comes enabled when the plan includes the feature | Whoever manages the workspace integrations |
| Allow Hashdata in the company's assistant, when that applies: the connector in Claude Team or Enterprise, custom MCP servers in ChatGPT Business or Enterprise, the Hashdata agent in Microsoft 365 | The company's admin for the assistant |
| Have an account with the assistant and a Hashdata account | You |
Form responses may contain personal data. The data the assistant reads is sent to the assistant's provider (Anthropic for Claude, OpenAI for ChatGPT, Microsoft for Microsoft 365 Copilot) so it can answer. Whoever manages the integrations decides whether the workspace may do this: if it may not, disable AI / MCP access.
Connect
Each assistant has its own name for this link: Claude calls it a connector, ChatGPT a plugin and Microsoft 365 Copilot an agent. When asked, the Hashdata address is:
https://mcp.hashdata.app/mcp
- Claude
- ChatGPT
- Microsoft 365 Copilot
This works for claude.ai, Claude Desktop and the Claude mobile app.
- On claude.ai, open Settings and go to Connectors.
- Look for Hashdata in the connector directory and click Connect. If Hashdata isn't listed, click Add custom
connector, enter the name
Hashdataand the address above, and click Add. Leave the advanced options blank. - Sign in with your Hashdata account if asked, and authorize the access.
- In a conversation, turn on the Hashdata connector in the tools menu of the message box.
You set it up on chatgpt.com, in the browser. If the option to add an MCP server doesn't show up, your ChatGPT plan or your company's ChatGPT admin doesn't allow it.
- Open chatgpt.com/plugins, click + and choose Add custom MCP server.
- Enter the name
Hashdataand, in Server URL, the address above. - For authentication, choose OAuth: it means signing in with your Hashdata account.
- ChatGPT shows a risk warning, which appears for any server not made by OpenAI. Read it and confirm with I understand and want to continue.
- Click Create as a plugin, install the plugin, sign in with your Hashdata account and authorize the access.
- In a conversation, choose the Hashdata plugin.
Hashdata is a Microsoft 365 Copilot agent. It works in Copilot Chat, including in Teams, and doesn't need a Microsoft 365 Copilot license.
- Company admin: in the Microsoft 365 admin center, make the Hashdata agent available to the organization or to the groups that will use it.
- You: in Copilot Chat, open the agent list and choose Hashdata. If it isn't there, search for Hashdata in Get agents.
- On your first request, click Sign in to Hashdata, sign in with your Hashdata account and authorize the access, keeping every permission checked.
Authorize the access
On the first connection, the Hashdata Authorize access page opens (my.hashdata.app/connect), showing the
application that requests access and the Requested permissions. Check that the application is the one you are
connecting and click Authorize; to refuse, click Deny.
First conversation
Make a simple request to test it: "Which Hashdata workspaces do I collaborate in?". If the list shows up, the connection works. If you collaborate in several workspaces, say which one you want to work in. The assistant may call a workspace a space.
What to expect
| Claude | ChatGPT | Microsoft 365 Copilot | |
|---|---|---|---|
| Permissions | Asks for the read permissions when connecting, and for the write ones when you ask for a change | Asks when connecting; if one is missing, asks again or shows an error | Asks for all of them at once |
| Confirming changes | Asks before each change, unless you choose Always allow | Asks before each change; your choice may last only until the end of the conversation | Asks before each change |
| Disconnect | Settings > Connectors | ChatGPT plugins page | Chat settings > Agents |
- When you ask for a PDF, the assistant requests the Submit and edit responses permission. This is expected: it doesn't change anything without your confirmation.
- If the assistant can't find a form, give its exact name and the workspace.
- A connection that goes unused for 30 days expires, and every connection expires after 180 days. In these cases, just connect again.
What the assistant can do
| Area | What the assistant does |
|---|---|
| Workspaces | Lists the workspaces you collaborate in, shows their plan, quotas and folders, and lists the collaborators and the available form templates |
| Forms | Searches and reads forms; creates forms from scratch, from a template or by copying another one; adds, edits, moves and deletes questions, sections and text; sets up comments, photos and action plans on each question; adjusts many questions at once; changes a question's type; sets formulas, visibility rules and page navigation; changes the settings; publishes, unpublishes, archives and deletes forms |
| Responses | Searches and reads responses, calculates totals and the answer distribution of each question, and generates PDFs with one or many responses; submits, edits, follows up on and deletes responses; creates collective verifications; generates simulated answers in draft forms |
| Action plans | Reads the action plan configuration, searches actions (for example, overdue ones or those of one owner) and reads a full action plan; creates and edits action plans, including rescheduling due dates; records the execution, verification and cancellation of actions; deletes action plans |
The assistant only sees and changes what you can see and change in Hashdata. If you can't access a folder or edit a form in the portal, you can't do it through the assistant either.
Permissions
These are the permissions shown on the authorization page:
| Permission | What it allows |
|---|---|
| Read your forms | Search and read forms, workspaces, collaborators and templates |
| Create and edit your forms | Create, edit, publish, archive and delete forms |
| Read your form responses | Search, read and total responses |
| Submit and edit responses | Submit, edit, follow up on, delete, verify and simulate responses, and generate PDFs with responses |
| Read your action plans | Read the configuration, the actions and the action plans |
| Create and edit your action plans | Create, edit and delete action plans, and record the execution, verification and cancellation of actions |
These permissions limit what the assistant can do on your behalf, but they never extend your access: your collaborator permissions in the workspace still apply.
Limitations
- The assistant doesn't see the content of photos and attachments, only the file names.
- The assistant doesn't work with workflows, routines, invitations, auxiliary tables or advanced reports.
- For analyses over many responses, give the period, the site or other filters.
- Form templates can't be created or changed by the assistant, only used as a starting point.
- While a formula recalculation is running, the form can't be edited by the assistant.
- Some question types can't be created by the assistant yet; it tells you which ones are supported.
- Response PDFs are generated in the background. The assistant follows the processing and gives you the link when the file is ready. Each PDF holds up to 500 responses and doesn't include the action plan.
- The assistant deletes up to 100 responses at a time, always named one by one, and never "all the responses" of a form.
- Simulated answers can only be generated in draft forms, up to 50 at a time, and they replace the previous simulated ones.
- The assistant doesn't submit responses to forms that limit the number of responses per IP address.
- An action plan with completed actions can't be deleted.
- Creating and deleting action plans follows the same profile permissions as the portal.
Security and good practices
- Confirm the changes: don't choose "always allow" for actions that delete data, such as deleting forms, questions, responses or action plans. A deletion can't be undone.
- Mind sensitive actions: changing a question's type converts the responses already collected, and publishing a form creates a public link.
- Ask for a preview: before changing a form, a response or an action plan, the assistant can show the result without saving anything. Ask it to "show me a preview before saving" when you want to review.
- Change log: the changes the assistant makes to forms and responses are recorded in the Changelog (in the form list, the form's View logs option, depending on the plan) with the via AI mark and the application name. In these records, the IP address is the assistant provider's, not yours.
- Hashdata doesn't see your conversation: Hashdata only receives the requests the assistant makes to the server (for example, "search the responses of form X") and returns the requested data.
Disconnect
- Any assistant, from Hashdata: in your profile menu, open Account and Credentials > Connected apps and click Revoke (or Revoke all). The access is cut off right away.
- From the assistant: see the Disconnect row in What to expect.
- For the whole workspace: in the Hashdata Integrations menu, disable AI / MCP access. No assistant can access the workspace data until the access is enabled again.
Troubleshooting
The assistant may reword the messages below.
| Message or symptom | What to do |
|---|---|
| AI/MCP access is turned off for this space. | AI / MCP access is disabled in that workspace. Ask whoever manages the integrations to enable it |
| AI/MCP access is not available for this space's plan. | The workspace plan doesn't include the feature. Contact support |
| The user did not grant this permission to the assistant. | You didn't authorize the required permission. Disconnect and connect Hashdata again, authorizing the requested permission |
| The authorization page shows Could not complete | Close the tab and start again from the assistant. The authorization page expires after a few minutes |
| A workspace or a form doesn't show up | Check that you can access it in the Hashdata portal with the same account used in the authorization |
For developers: Claude Code
In the terminal, add the server:
claude mcp add --transport http hashdata https://mcp.hashdata.app/mcp
Then, inside Claude Code, type /mcp, choose hashdata and complete the authorization in the browser.
The connection uses MCP (Model Context Protocol), an open standard for connecting AI assistants to other systems.