Social Tasks
Off-chain signup and quest flows fanned across your burner accounts.
Social tasks are off-chain jobs run across burner accounts: Google Forms, X/Discord tasks, signup flows, allowlist forms, and curated quest submissions. They do not touch a chain directly.
What You Need
- Accounts - each account can hold wallet address, Gmail, X handle/cookies, Discord username, and an assigned proxy.
- Captcha Solver - only needed for modules with Turnstile or reCAPTCHA fields. Configure the provider and API Key in Settings.
- Browser session - only needed when a Google Form or browser-engine module needs a real logged-in session.
Google Forms
Inside a social task group, click +New Social Task.
Paste a Google Forms URL and choose an account group. The app first tries to parse the form anonymously. If Google gates the form, it falls back to a connected Google account from the selected account group. When the form needs Google session submission, the runner uses each row’s account session when it fires.
The parser renders the questions so you can map answers from account fields, fixed task values, random choices, or auto-fill behavior.
Social Modules
Social modules are not picked from the normal +New Social Task button. Start them from the Home Modules panel. The dialog opens locked to that module and renders the module’s fields.
Modules are descriptors published by the team. They can run through:
| Engine | Used for |
|---|---|
http | Plain API or form requests |
browser | Sites that need real browser cookies, TLS fingerprinting, or Cloudflare challenge handling |
The module author picks the engine. You fill only the fields the module exposes.
Account Isolation
Each social task uses one account:
- account profile fields such as wallet, X handle, Discord username, and Gmail
- that account’s assigned proxy
- that account’s browser profile when browser execution is needed
Tasks without the required account field are skipped or failed with a clear message in the row log.
Captcha Handling
Captcha fields are declared by the module. At run time the tasks looks up the selected solver provider and API key from Settings, solves the challenge, and injects the returned token into the request template.
If a module has captcha fields and no solver is configured, the dialog blocks or the row fails with a solver setup error.