Setting the file. One moment.
Subchapter 27.5
references/credential-setup-with-browser-use.mdMarkdown4 KBView on GitHub
Use this skill only when Browser Use tools are available. Handle credential setup directly with the browser tools — do not use any other browser bridge.
research(action="fetch-url") when a docs URL
is available. Use only when docs are missing
or clearly outdated. Do not navigate the browser to docs.research(action="web-search")browser_connect if no browser session is active, then open or navigate
to the external service console with browser_tab_open or
browser_navigate.browser_content for page text and browser_snapshot when you need refs
for browser_click, browser_type, or secret capture.ask_user when the user must choose a project, app name, account,
workspace, scope set, description, or resource. Do not invent these values.ask_user.browser_snapshot first. Use
interactive: false when the secret is static page text rather than an input.browser_capture_secret using either a snapshot ref
for an input or a redactedKey marker for visible text.credentialsKey for every captured field in one credential.browser_create_credential. Put literal,
non-secret values in data; put captured secret field names in
resolveData.browser_snapshot before clicking, typing, selecting, or
capturing. Refs from old snapshots are stale.browser_content for reading and browser_snapshot for interaction.
Use screenshots only when visual layout matters.After browser_create_credential succeeds, call the relevant n8n credential or
workflow setup tool again so the new credential can be selected or applied. If
the user must finish sign-in, 2FA, consent, or manual entry, tell them exactly
what to do in the browser or n8n setup card, without asking for secrets in chat.