Proxy Mail QA

Custom fields

Every field of your sign-up form, filled.

Tell Proxy Mail QA once what goes in your form’s own fields, such as company size or “How did you hear about us?”. Your coding agent gets the same answers from form_values on every run as your team does from Proxy Mail QA for Chrome, and anything nobody has taught is guessed and marked for checking.

Free plan · 50 custom fields per project · ready-made phone, ID and tax number fields · form_values on the MCP server, REST, npm and Python · Proxy Mail QA for Chrome

How it works

Teach it once.

  1. Ask your agent

    “Set up custom fields for our sign-up form.” It sends each screen’s fields to form_values, lists the ones that would be guessed or left empty, and saves the custom fields you agree to.

  2. Teach it from the page

    After Proxy Mail QA for Chrome fills the form, choose Teach beside a field it guessed or left, pick what goes in, then Save and fill.

  3. Or add one in Project settings

    Name it, say how to recognise the field (a test ID, its name, or words in its label, in each of your site’s languages) and what goes in it. Keep it to one page in every language, one site, or use it everywhere.

  4. Every fill uses it

    Every agent, test and teammate on the project gets the same answer for that field, and the same account gets the same answer every time.

For coding agents

Your agent gets the same answers.

form_values answers each field the page describes. A field a custom field decides comes back with kind custom, and a field nobody taught with kind guess and where the guess came from, so the agent checks it before it submits.

Ask what goes in each field

form_values on the MCP server, or POST /v1/form-values. Send site and page on every screen, so custom fields kept to that site or page apply.

form_values
{
  "site": "staging.acme.dev",
  "page": "/signup",
  "fields": [
    { "id": "size", "type": "select", "label": "Company size",
      "test_id": "company-size", "options": [ … ] },
    { "id": "web", "type": "url", "label": "Website" }
  ]
}

Type in what comes back

The values come from the same test address, so the same account gets the same answers next time.

The answer
{ "values": [
  { "id": "size", "kind": "custom", "value": "11-50",
    "rule": { "id": "…", "name": "Company size" } },
  { "id": "web", "kind": "guess", "from": "type",
    "value": "https://www.example.com",
    "note": "Guessed from its type. Check it suits your test, …" }
] }

Save one when a field blocks the form

Agents save a custom field only when you ask, or when a required field would otherwise block the form and you agree.

save_custom_field
{
  "name": "Company size",
  "match": { "on": "test_id", "text": "company-size" },
  "value": { "kind": "option", "option": "11–50" },
  "tag_answer": true
}

Or from your tests

The npm package and the Python helper have the same calls, with one call per screen for a sign-up over several.

signup.spec.ts
const first = await qa.formValues({ fields, site: 'staging.acme.dev', page: '/signup' });
// …fill it, press Continue, then on the next screen:
const next = await qa.formValues({ fields: teamFields, address: first.address, site: 'staging.acme.dev', page: '/signup/team' });
await qa.saveCustomField({ name: 'Team size', match: { on: 'name', text: 'team_size' }, value: { kind: 'option', option: '2–10' } });

form_values in the MCP docsCustom fields over REST

Ready-made fields

Phone and ID numbers, filled the safe way.

Some fields shouldn’t get a value anyone made up. A phone number might reach someone, and random digits in an ID field might be a real person’s. Add a ready-made field and Proxy Mail QA fills them with values that can’t, for every agent and test. Where it has no such value, the field stays empty with a note.

Phone number

Every project has one. It puts in a number set aside for fiction in the UK, Australia, the US and Canada, and your app’s own test number for each other country you add, so nobody is texted by a test.

National ID, tax and passport numbers

National ID, personal tax and passport numbers that follow the format and never match a real person, where Proxy Mail QA has a safe one, or a KYC vendor’s sandbox values for checks in test mode. Only the project’s leads add them. Personal tax numbers come only from a KYC vendor.

VAT and business tax numbers

The same for a business’s numbers. Proxy Mail QA has no safe VAT number, and the UK’s VAT check refuses every fake, so a VAT number field stays empty with a note unless a KYC vendor’s sandbox values have one.

Common choices

Gender, language, role, team size, business type and how someone heard about you get one of the field’s own options, the same one for the same account.

The terms box

Ticked, or left unticked to test what your form says when the terms aren’t accepted.

In your site’s languages

Each one finds its field by what it asks for, in English, German, French, Spanish, Italian, Portuguese, Dutch, Chinese and Japanese. Your own custom field for that field still comes first.

Ready-made fields in the docsTest phone and ID fields safely

Guesses

Fills the rest, and shows what it guessed.

A field with no custom field gets a value from what it suggests, marked as guessed. The same account gets the same guesses every time.

An example in the placeholder

“Acme Ltd” or “e.g. Hiring manager” is typed as it is. An instruction such as “Enter your company size” never is.

One of the options

A different real option for each account, so a run of test accounts covers the drop-down. Placeholder options such as “Choose…” are skipped.

Its type, pattern or label

https://www.example.com for a website, a number inside the field’s range, QA Engineer for a job title, a postcode for the persona’s country.

Every field, by default

Every field with no custom field gets a guess unless the project says otherwise, for new and existing projects alike.

Or required fields only

Only fields the form marks as required get a guess, for apps that refuse odd values in optional fields. Optional ones are left for you.

Or off

Only built-in values and custom fields are filled, as before. Change it in Project settings, or for one call with guess in form_values.

What it never fills

Some fields stay yours.

Whatever the setting, these are never guessed, and they come back empty with the reason.

  • Payment fields

    Card numbers, CVC, expiry, IBAN and billing. Test cards belong in your payment provider’s test mode, so they can’t have a custom field either.

  • ID and tax numbers

    Passport, national insurance, VAT and tax IDs are never guessed. A ready-made field fills one with a fake value that never matches a real person, where Proxy Mail QA has a safe one, and a custom field with a fixed test value your team publishes, but random digits never go in a personal ID.

  • Passwords and secrets

    Only the account’s own password is filled. PINs, keys, tokens and security questions never are, and a value that looks like a card number, a private key, or an API key or token in one of the listed formats is refused.

  • Codes from somewhere else

    One-time, promo, coupon and referral codes come from email or from you. A made-up one would fail the form.

  • CAPTCHAs and uploads

    Never filled, and neither are colour pickers or hidden, disabled and read-only fields.

  • Consent boxes

    Unticked is a valid answer, and ticking a box agrees to something. Teach Ticked for the ones your team always ticks.

Sign-ups over several screens

The same account on every screen.

Company details, a team size or onboarding questions often come after Next. Proxy Mail QA for Chrome fills them with the account it made on the first screen. It never presses Next or submits.

  1. Fill this step

    On a later screen, a button in its first empty field fills it with the same test account, its custom fields and guesses. The card counts the screens, such as “Filled step 2 of 3”.

  2. Or the shortcut

    Alt+Shift+F does the same, and Fill this page in the popup works there too, for a sign-up started in the page or the popup. Change the shortcut at chrome://extensions/shortcuts.

  3. The question after Next

    After you press Next or Continue (the button words are read in nine languages), it asks whether the new screen is part of the sign-up. Keep this screen fills each later screen on that site by itself from then on, or asks your project’s leads first where only they change sites.

  4. Or fill each screen by itself

    For a site whose sign-up always goes on, choose Keep this screen, or switch on Project settings → Sites → Sign-up goes over several screens. Each new screen after you press Next is filled, and the card shows what went in.

Agents and tests call form_values once per screen with the same address, and each screen’s site and page (or a native app screen’s name as screen). Each site’s sign-up screens are listed in Project settings → Sites → Sign-up screens.

Your team stays in control

Leads decide, members ask.

Lock changes to leads

One switch in Project settings → General lets only the project’s leads change its sites and custom fields. It’s off until a lead turns it on.

Members ask instead

Members ask a lead from Teach in the extension, from the app or through their agent, with a note. Leads approve or decline it in Project settings, and get an email at most once an hour.

Everything in the activity log

Every custom field saved or removed, every change to the guesses setting, and every request and answer, with who and from where, “from Claude Code” included.

FAQ

Questions

Does Proxy Mail QA check that my form works?

No. It hands over values for each field, and your app does the checking. Whether the form accepts them, and what it does next, is what your test or your agent checks.

Do agents and the extension get the same values?

Yes, for your team’s own custom fields. They belong to the project, and their lists, random digits and guesses are drawn from the test address, so the same account gets the same answers from form_values and Proxy Mail QA for Chrome. Proxy Mail QA for Chrome 0.9.0 doesn’t fill ready-made fields, though, and guesses a phone number, street, city, region or postcode its own way.

What happens on a field it doesn’t know?

It gets a guess from its placeholder, options, pattern, label or type, marked as guessed with where it came from, unless the project guesses required fields only or not at all. Payment fields, ID numbers, secrets, codes, CAPTCHAs, consent boxes and uploads are never guessed.

Does it work on a site in several languages?

Yes. A page such as /signup covers /de/signup and /fr/signup too, and a custom field that recognises a field by its label can hold the label in each language, such as Referral code, Empfehlungscode and Code de parrainage. A test ID or name usually stays the same in every language, so it needs only one.

Can it fill payment fields?

No. Card and bank fields are never filled and can’t have a custom field. Use your payment provider’s test mode and its test cards.

What goes in a phone or ID number field?

In form_values, only what the project’s ready-made fields give. Every project has a Phone number, which puts in a number set aside for fiction or your app’s test number for the account’s country. ID and tax number fields stay empty until a lead adds their ready-made fields, which give values that follow the format and never match a real person. A phone, ID or tax number field with no safe value stays empty with a note.

Can I stop the guesses?

Yes. In Project settings → Custom fields, Fill fields it doesn’t know has three choices, Every field, Required fields only and Off, and an agent can pass guess off to form_values for one call.

How many custom fields can a project have?

50, on Free and Team alike, each looking for up to 10 phrases. Each can be kept to one site, or one page of it in every language, or used on every site.

More features

Your whole sign-up form, filled the same way every time.

Create a free account, connect your agent, and tell it what goes in your form’s own fields.