Social Templates & Modules

Custom templates solve repeated-answer assignment. Social modules define site-specific submission workflows. They work together, but they are different features.

Custom answer templates#

Open Settings → Social → Custom Templates, click Add Template, give the pool a lowercase name such as punkanswer, and paste one answer per line. Type {punkanswer} in any Google Form or social-module text field.

When the task is created, Zyper replaces the custom token with a literal answer for each account:

• Random deterministically shuffles the pool for that account group.
• Order deals answers from top to bottom.
• Answers do not repeat until the account count exceeds the pool size, then the pool wraps.

Assignments are stable for the same group, pool name, and account position. Removing an account from the middle of a group shifts the positions—and therefore answers—of later accounts.

Names must start with a letter and contain only lowercase letters, digits, or underscores. They cannot duplicate a pool or shadow built-ins such as {wallet}, {xhandle}, {xtweet}, {discordhandle}, {gmail}, and {random:…}.

Published social modules#

Start a site-specific module from the Modules panel on Home. The module descriptor locks the target workflow, chooses an http or browser engine, and exposes only the fields its author supports. Select an account group, fill those fields, and configure a captcha solver when the descriptor requires hCaptcha, Turnstile, or reCAPTCHA.

Modules are reviewed descriptors published by the Zyper team, not arbitrary user code pasted into the desktop app. A normal +New Social Task creates a Google Forms task; it is not the module picker.

Each task row still uses its account’s mapped fields, assigned proxy, and browser profile where required. Missing account data or solver configuration produces a row-level skip/failure instead of silently substituting another identity.