Connect Claude or ChatGPT to Acquainto

One link connects an AI app to this Acquainto account. After that you can ask Claude or ChatGPT what eflows you have, how one is performing, or to start a new one from a template — without leaving the chat. There is nothing to install and no code to write.

Everything about the connection lives in Settings → Workspace → AI assistants: the link, the steps for each app, what is currently connected, and the button that switches one off.

Copy your connection link

Open Settings → Workspace → AI assistants and press Copy next to Your connection link.

It is not a password. Nobody gets into your account with it alone — you sign in to Acquainto part-way through the setup, and that sign-in is what grants the access. So the link is safe to paste into an app, and safe to send to a teammate who is setting up their own.

Connect it

Claude — website or desktop app

1. Open Settings, then Connectors.
2. Choose Add custom connector.
3. Paste the link and choose Add.
4. Claude opens an Acquainto page — sign in and choose Allow.

Custom connectors need a paid Claude plan (Pro, Max, Team, or Enterprise).

ChatGPT — website

1. Open Settings, then Connectors.
2. Choose Create, or Add custom connector.
3. Paste the link and choose Create.
4. ChatGPT opens an Acquainto page — sign in and choose Allow.

Custom connectors need a paid ChatGPT plan, and are on the website rather than the phone app.

Another app — Cursor, VS Code, Zed, and others

1. Look in its settings for Connectors, Integrations, or “MCP servers” — different apps use different words for the same thing.
2. Add a new one and paste the link.
3. When it asks how to sign in, choose the option that opens a browser window.
4. Sign in to Acquainto and choose Allow.

“MCP” is the shared standard these apps use to talk to tools like ours. If an app supports it, this link is all it needs.

The Acquainto page in the middle

Whichever app you started in, it hands you to a page of ours to sign in. Three things happen there.

You sign in the way you normally do. Email and password, or Continue with Google if that is how you signed up. If you have two-step sign-in turned on it asks for your code, as usual.

You choose what the app is allowed to do. Two options, with View and edit already selected:

• View only — it can read your eflows, your response data, and who you have invited. It cannot change anything.
• View and edit — everything above, plus create, edit, and publish eflows, update responses, and create invite links. Pick this if you want to ask it to build or change something.

Either way it can never see your password, invite or remove people, change your billing, or delete your account.

You choose Allow, and the app is connected.

The choice is made at connect time, not afterwards. To change it, disconnect the app and connect it again. Until you do, the AI assistants card says Can only read next to it, so a refusal later is not a mystery.

Some apps ask only to read, and then the page has no choice on it — it says so, and the fix is a write or full-access option in that app’s own settings before you connect again.

Then say “help acquainto”

That is the one thing worth typing first. It replies with what Acquainto is, everything the connection can do for you, and what it can’t — so you do not have to learn a vocabulary before you get an answer.

Four that work from a standing start:

• “What eflows do I have?” — the fastest way to check the connection is working.
• “Start a customer-feedback eflow from a template, then show it to me.”
• “How is Onboarding survey doing, and where are people dropping out?”
• “Give me the code to put Onboarding survey on my website.”

What you can ask for

See what you have. The eflows in the account and whether each is published. One eflow’s settings, or the questions it actually asks, including the follow-ups that open depending on what someone picks. How one is performing over a date range, and where people give up. What one invited person answered, by their email address.

Make a new one. The ready-made templates and what each is for; a new draft started from one; or a copy of an eflow you already have, questions and all.

Change one. An eflow’s name, description, tone of voice, opening and closing lines, and where completed answers get sent. Publishing and unpublishing too — and if an eflow is not ready to go live, it says so rather than publishing something broken.

Get it in front of people. The few lines of code to drop an eflow into your own site, or a ready-made page to link to instead. A private link for one named person, or for a list of up to 500 at once. Who you have invited already. A preview of exactly what someone will read before you send anything. A QR code for a poster or a table card.

What it cannot do

• Write or reword the questions themselves. It can read them but not change them. Start from a template or copy an existing eflow, then edit the questions in Acquainto on the web.
• Read through everyone’s answers. It can look up one invited person by email; browsing or exporting the whole set is the Responses screen.
• Send anything. Invite links come back to you as text — mail, message, or print them however you like.
• Touch the account itself. Billing, branding, team members, and settings are all web-only.

It switches off after 30 unused days

A connection nobody uses for 30 days stops working, and the row on the AI assistants card says Switched off. Using it resets the clock — asking the app anything about your eflows is enough — and in the last week before it would lapse, the row warns you with the date.

Nothing is lost when one does switch off. Connect it again with the steps above and it picks up where it left off.

Switching one off yourself

On the AI assistants card, press Disconnect next to it. The app loses access straight away. Your eflows and responses are untouched, and nothing it already created is removed. You can connect it again whenever you like.

Each connection belongs to the person who signed in to authorize it, but the list is shared: anyone signed in to the account can see every connection and disconnect any of them. That is deliberate — a teammate who has left should not leave a live connection behind that nobody else can switch off.