Overview
The onboarding process involves:- Creating an Onboard - When a buyer accepts a connection invitation, an onboard record is created with status
created. Optionally, the UI can send aflow_idif already available - In Progress - The UI sends a PUT with the user’s
flow_idand statusin_progress - Completing Setup - The UI must send a PUT with status
completedto notify the backend that the onboard process is finished. The backend then calls/onboard/buyerto finish the flow synchronization
/onboard/buyer endpoint can also be called directly by the UI modal when the user has already completed a previous onboard process.
Onboard Statuses
| Status | Description |
|---|---|
created | Initial state when the onboard is first created |
in_progress | The UI has sent the user’s flow_id |
completed | The backend triggers the buyer delivery setup by calling /onboard/buyer |
failed | The setup process encountered an error |
Buyer Setup Process
The backend automatically triggers the buyer delivery setup when the onboard status is set tocompleted. This process performs:
- Connection Validation - Verifies the connection exists and hasn’t already been set up
- Seller Flow Discovery - Finds all seller flows that have a buyer step pointing to this buyer
- Buyer Flow Setup - Creates or updates the buyer’s flow to receive leads from the seller
- Seller Flow Updates - Adds the buyer’s
flow_idto the seller’s flow mappings - Notifications - Sends email notifications to seller account users about the new connection
- Connection Flagging - Marks the connection as having buyer delivery configured