All updates

Reshape roles when a trader hits a milestone, and send completions out over a webhook

Reward, replace, or remove roles when a trader clears a milestone stage, point a condition at a member field, and send completions out over webhooks.

01 ·Reward, replace, or remove roles and tags at a milestone or referral stage

A milestone or referral stage can now do more than hand a trader new roles and tags when they clear it. A broker still rewards roles and tags, now grouped together, and gains two more choices. Reward and overwrite replaces every role and tag a trader already holds with the chosen set, so a trader carrying two roles ends a stage holding only what the stage grants. A remove section strips chosen roles and tags from any trader who holds them as they clear the stage.

Clear a stage
One of three does
RewardAdds the chosen roles/tags
Reward + overwriteReplaces everything held
RemoveStrips the chosen ones
Illustration · Clearing a stage can add roles, replace them all, or remove them
Why it matters

A broker running a ladder of tiers wants each rung to set a trader's standing cleanly, not pile new roles on old ones. Replacing or removing roles at a stage lets a broker move a trader onto the right tier as they progress, in VIP tier progression, rather than leaving a stack of every level they passed.

02 ·Point a milestone or referral condition at a member field

The value a milestone or referral condition compares against can now read from a member field, not a fixed number a broker types in. When building a condition a broker picks the reference from a dropdown, and the choices are the default and custom fields whose data type matches, so a date condition lists date fields such as join date. Picking a date opens a calendar.

Why it matters

A broker setting a condition against a moving target, such as days since a trader joined, wants it to read the trader's own record rather than a number that goes stale. Pointing the comparison at a member field keeps the condition true to each trader, tying the rewards they earn to what the broker already holds on them.

03 ·Send purchases and completions out over a webhook

Three outgoing webhook events join the set. A store purchase sends the item name, cost, and description, the voucher code where one is issued, and the buyer's username and email. A milestone completion and a referral condition completion each send the group and stage name, the rewards granted, and the trader's username and email. Each carries the time it happened.

Why it matters

A broker who runs reporting or fulfilment outside the community wants a purchase or a completion to reach those systems as it lands. Sending each event out over a webhook lets a broker book a redemption or act on a milestone in their own stack without watching the community for it.

04 ·Track workflow runs and write a currency from a workflow

A workflow now keeps a run history, each run marked running, queued, success, or error, with up to three running at once per community and the rest queued. Opening a completed run shows each step's input and output, and a link returns to the workflow to edit it. A workflow's field actions can also target a currency, listed alongside the custom fields a step can write to.

Run history
Running ×3QueuedSuccessError
Each step
Its input and output
Illustration · Each run is marked running, queued, success, or error, with per-step detail
Why it matters

A broker leaning on a workflow to keep records current wants to see whether each run did its job and to act on a currency, not only a custom field. A run history with each step's output lets a broker confirm a flow worked, and writing to a currency ties an outside figure straight into the earn-and-spend loop.

Also in this build
Improvement

XP and coin values can now carry decimal places.

14 May