Skip to content

Unofficial parody. The software is real. Unofficial parody of infloww.com. Not affiliated with Infloww. The software is real; the jokes are ours.

Inflowwww
Menu

Log a creator in from the Inflowwww page, even on your phone

How Try Browserbase login links a creator's OnlyFans account from the Add creator flow, with no capture extension, on a phone or a laptop.

By the maintainers 4 min read

Inflowwww login on desktop and phone

Linking a creator used to mean the capture extension: log in to OnlyFans in desktop Chrome, open a chat, click Copy cURL, paste it into Inflowwww. That needs a laptop with the extension installed. Try Browserbase login does the login from the Inflowwww page itself, so it works on a phone too.

Video coming soon
Logging a creator in from the Inflowwww page on a phone

What you need

  • The owner login. The login runs from Creators > Manage creators, which chatters do not see.
  • A server with BROWSERBASE_API_KEY and BROWSERBASE_PROJECT_ID set in the relay's environment, on a Browserbase plan that includes proxies. Without them the login refuses to start.
  • The creator's OnlyFans email and password, and the creator within reach if OnlyFans asks for a 2FA code.

The steps

The Try Browserbase login form on a phone: OnlyFans email, password and the start button
The sign-in step on a phone fits the first screen. Demo data.
  1. Open Creators > Manage creators and tap Add creator.
  2. Under Creator details, enter the creator's name and tap Next: Link creator account.
  3. Pick OnlyFans.
  4. Under Proxy selection, keep Inflowwww proxy (the default when your server has a proxy pool), or pick No proxy or one of your custom proxies. Tap Connect OnlyFans.
  5. The sign-in step opens. On a phone it shows only Try Browserbase login, with a line saying Paste cURL needs the desktop browser extension. On a laptop both are there. How it works unfolds the explanation on a phone; it stays folded so the form fits the first screen.
  6. Type the OnlyFans email and password and tap Try Browserbase login.
  7. The card reports each stage: starting the remote browser (about 10 to 20 seconds), then entering the email and password.
  8. If OnlyFans shows a verification check, or asks for a 2FA code, the card says so and shows Browserbase's live view. Solve it there, or tap Open live view full screen, solve it, and come back to the Inflowwww tab. The login finishes there. Nothing solves the check for you.
  9. The card reads "Signed in. Saving the session", then "Account ... added" and names the proxy now attached. The flow moves on to Creator account is linked to Inflowwww, which shows the account and its proxy, and Next opens Account details (nickname, tag, assigned employees, internal notes).

Stop login ends the job at any point. The remote browser lives about five minutes and the login, your part included, has to land within about three and three quarter minutes. If time runs out, the card shows the error and Try again.

The same card handles a re-login. From a creator row whose session died, it opens straight on the sign-in step, and the account keeps the proxy it is already on.

Which network the login uses

The login runs in a Browserbase browser, on Browserbase's own managed proxies. Your proxy is never sent to Browserbase.

Once OnlyFans has signed in, the relay attaches the proxy you chose under Proxy selection to the account, then saves the session. From then on every request for that account, chats, vault and stats, goes out through that proxy, the same as a login captured with the extension. With No proxy, nothing is attached.

What chatters never see

  • The password. It is sent once to start the login and cleared from the form. The server never stores, logs or audits it, and the status the page polls carries no secrets.
  • The login itself. The remote login endpoints are owner-only. A chatter session is refused, and the Creators page is hidden from chatters.
  • OnlyFans. Chatters sign in to Inflowwww with their own logins and work through the saved session. Passwordless account sharing covers inviting them and limiting what each one sees.

When it fails

  • If the remote browser cannot start, or the OnlyFans page will not load, the job stops at once and the card shows the error.
  • If the proxy you picked is Inflowwww proxy and your server has no pool, the login refuses to start. Pick another proxy.
  • If OnlyFans keeps asking for checks, finish the login with the extension on a laptop instead. Both paths save the same kind of session.

The pitch. Linking a creator now takes a phone, the creator's password once, and a minute in a live view. Your proxy takes over the account the moment it is in. Deploy it yourself.

More in Product

All posts in Product

Get started with Inflowwww today

Deploying it yourself means installing it once on a server you rent; after that, everyone works in a browser.

After the one-time setup (docker network create n8n_default, the state files and an .env), this is the install. Docker Engine 25+ with Compose 2.20+.

docker compose up -d --build

Before chatters reach it from outside, read the security notes: today it belongs on a private network or a VPN, not on the open internet.

Using it on a live OnlyFans account may violate OnlyFans' Terms of Service; the risk sits with the creator's account. Read the disclaimer first.