Custom verify
Let your own server decide whether a step passed or failed.
A custom verify requirement hands the pass/fail decision to your own backend. The installer completes the step, and Inboard asks your server whether the setup is correct — useful when success depends on state only you can see.
When to use it
Use custom verify when no simple URL probe can confirm the install: the proof lives inside your system (an account flag flipped, a record created, a key validated against your database). It's the most flexible verifier and the right choice for anything the other types can't observe.
How to configure it
You point the requirement at your own validation, and Inboard calls it when the installer reaches the step:
- The check runs server-side and returns a clear pass or fail to the widget.
- Reference variables so your server knows which installer to check — for example passing
{{domain}}or{{accountId}}.
On reaching this step, Inboard calls your validation for {{accountId}}.
Return pass once the account shows the integration as connected.Keep the result fast and deterministic so the installer gets immediate feedback.
How it's verified
This requirement is verified by a custom check — your server-side validation is the source of truth for pass/fail. If your server is unreachable or returns failure, the step stays incomplete until it passes.