What No-code does
An invite opens the same platform-hosted pages that a Low-code journey uses. Only the way the journey starts differs, so your journey configuration, modules, and outcomes behave identically. Your organisation’s branding therefore applies to a No-code journey exactly as it does to a Low-code one. Branding covers the logo, colours, and theme on the hosted screens, and you configure it on the journey rather than per invite. To learn more, see Branding. No-code suits customer-facing teams who verify one customer on request, such as support agents onboarding a new client or compliance staff running an ad hoc check. It also suits organisations evaluating GBG Go who want to test a journey end-to-end before building an interface.How No-code works
You build and publish the journey once, and then send an invite for each customer you want to verify.1
Create and publish a Hosted journey
Build the journey in the Journey builder with the modules your check needs, and then publish it to an environment. Select Preview while you test, and Production when you go live.
2
Invite your customer
Open the journey, click the Actions list, and then click Invite a customer. Enter an email address, a mobile number, or both.
3
The platform sends the link
The GBG Go platform sends your customer a verification link. An invite is valid for one customer, and by default it expires after seven days.
4
Your customer completes the journey
Your customer opens the link and submits their details on each hosted screen. The platform then processes the data through the modules in your journey.
5
Review the outcome
Review the result and the decision in Investigation once your customer completes the journey.
Check which modules work with No-code
An invite carries no data, so every input a module requires must be collected from your customer on a hosted screen. Inputs marked Pre-filled are supplied through the API at journey start, which No-code can’t do. To check a module before you invite a customer:- Open your journey in the Journey builder.
- Click the module you want to check.
- Select the Data tab.
- Review the Source column of the Inputs table. Confirm that every required input names an interaction group rather than Pre-filled.
- The module and variant must be enabled in your contract. Modules and variants marked with an orange warning icon require activation by the GBG team.
- Some module variants aren’t supported by hosted screens yet. Any input without a hosted card moves to pre-fill.