Build automated workflows, slice the user list into segments, and create members over the API
Build workflows that pull outside data into a member field, save user-list segments, create members over the API, and cap store purchases by role.
01 ·Build a workflow that pulls outside data into a member field
A broker can build a workflow from a sequence of steps. It starts on a trigger, an incoming webhook or a trader joining or visiting the community, and runs HTTP request steps that call an outside service with the method, parameters, headers, body, and authentication a broker sets. A platform action then writes the result into a custom field, with numerical fields set to overwrite, add to, or subtract from the current value. A data selector carries a value from an earlier step into a later one, each step has a test that shows its output, and a broker deploys the workflow to run on its trigger.
A broker who keeps a trader's standing in an outside system wants it reflected in the loyalty community without re-entering it. Building a workflow that calls the source and writes the result onto a member field lets a broker keep the record current, which milestones, tiers, and referral conditions then act on.
02 ·Save user-list segments and build filters
The user list gained a segments panel down the side, grouped under user management, penalty management, and gamification management, each opening the list against a default view: a penalty segment sorts by when a penalty started, a gamification segment sorts by total XP. Above the list a broker builds a filter by picking a field and a value, adds more conditions a tag at a time, and a filter option is greyed out where the feature behind it, such as tiers or levels, is off. A broker saves a set of filters as a segment to return to.
A broker working a community of any size wants to land on a defined group, the penalised members or the holders of a field value, without rebuilding the view each time. Saving segments and filtering on any field lets a broker keep the cuts they work from a click away.
03 ·Create members over the API
A Create User endpoint joins the API, governed by its own Create User permission a broker grants on an API key. The call takes a flag that decides whether the new member is sent a verification email or treated as already verified, so a broker brings members in from their own system without each one confirming the account.
A broker who already holds an account list wants those traders in the loyalty community without each one signing up individually. Creating members over the API, and choosing whether they skip verification, lets a broker stand up a community from records they already keep.
04 ·Cap how many times a role can buy a store item
A store item's purchase permission gained a purchase limit a broker sets per role or tag. On the storefront a trader carrying the role sees a counter of how many they have left, a trader who can view but not buy sees a locked price button, and an Exclusive Access panel on the item lists the roles that can buy it and their limits.
A broker putting a scarce reward in the store wants it held for the traders it is meant for and capped per trader. Setting a purchase limit by role turns a store item into a controlled perk for a tier, with the counter showing each trader what they have left in the earn-and-spend loop.
The unsubscribe link now appears on batch and immediate email notifications, alongside the daily digest.
25 AprThe outgoing webhook for a trader joining a community now carries first name and last name as separate fields.
23 Apr