Custom Code & Experiences

Add Run custom code to the After-Survey Actions step to do things a webhook can't: personalised lines, numbered editions, prize draws, quiz badges or QR coupons on the print. The code runs on the guest's device when the survey is finished, before the answers are saved, also offline. It fills Outputs (text or a picture) with setField. Map them onto your design in Dynamic Survey Mapping (they appear as "Code: …") or use {code:name} in messages. Try it runs the code with sample answers. If the code fails or takes too long, the guest just continues and the response shows the error.

What the code can use

answers (answers.Q1 or by question ID) · answer("Question title") · event · survey · guestNumber · setField(name, value) · await counter(name) (this device) · await sharedCounter(name, step, max) (every booth of the event) · random(min, max) · pick(list) · images(set) · pickImage(set, group) · groups(set) · await recall(key) · await remember(key, data, { merge }) · await faceRead() (smile, head tilt, number of people in the guest's photo) · await qrCode(text) · printOptions({ copies, printer, skip, message }) · tally(board, name, amount) · highScore(board, name, score) · confetti() · fireworks() · message({ text }) · sound(name) · wait(ms) · fetch()

Print routing: printOptions({ copies: 2, printer: 'Photo printer' }) prints this guest's design with that many copies on that print-server printer, and printOptions({ skip: true, message: '…' }) shows the message instead of printing. Live leaderboard: tally('teams', 'Blue') adds to a total and highScore('quiz', 'Alex', 8) keeps each name's best score. Show them on a TV with /leaderboard?event_id=… or on the second screen with the Cast button (Live leaderboard). Offline, the scores wait on the device and are sent with the next guest.

Guest memory: await remember(key, data) saves up to 2 KB for a guest and await recall(key) gives it back on their next visit (or null). Guests are matched by the key you pass in, for example their email (trimmed, lower case). Only a SHA-256 hash of the key is stored, never the email itself. Offline, a copy on the device is used and saves are sent when it is back online. In Try it both work in memory only. The event's Analytics page lists Remembered guests, with Clear all for after the event and Forget guests (never, or 1 to 365 days after a guest's last save). Several booths, one guest: with { merge: true } a save is added to what every booth saved (lists are joined, empty values never overwrite) and remember returns the combined data, so booths on different devices can fill the same passport. Shared counters: await sharedCounter('coupon') counts across every booth and device of the event; sharedCounter('win-bag', 1, 20) returns null once 20 is reached (prize stock). Offline, a booth counts from the last value it saw and catches up later. See or reset them under Shared counters in the event's Analytics.

const email = answer('Email');
const past = await recall(email);
const color = past?.color || pick(colors);
let style;
do { style = pick(styles); } while (styles.length > 1 && style === past?.style);
await remember(email, { color, style, visits: (past?.visits || 0) + 1 });

Choose Experience in the guided wizard to get one of these fully working. The wizard writes the custom code, the output fields for your design and the image sets from your answers, so you only fine-tune the code if you want to.

A few more ideas you can build with the helpers above: