Sample Workflow: Single Custodian RIA Using APIs
This use case is ideal for an RIA firm that wants a higher level of automation than the Quik! App provides but wants to keep the workflow simple. The focus of this case is on a single custodian, but it could be extended to multiple custodians.
Workflow Overview
The ideal scenario is as follows:
- From within the CRM, choose a client and then click on a button or link to initiate the forms workflow.
- Still within the CRM, a custom screen asks the user to pick a form bundle from Quik!.
- Configure the form bundle directly within the Quik! Customer Central website (https://qcc.quikforms.com/QFE/)
- Call the Form Group API to get the forms:
- API guide: Form Groups Services
- Swagger: Swagger UI
- Method: Get FormGroups
- Display the list of form groups to the user
- The user clicks a button or link to generate the forms
- Call the Quik! authentication API (REST APIs (Preferred Method))
- Pass the following info to the Quik! Forms Engine API (Execute HTML Generate Forms - Quik! Forms Engine Services)
- FormGroupID = the form group the user selected
- Client Data Fields = all of the CRM fields for the selected client(s)
- Form Configuration Settings = all of the settings for e-sign, form viewer control, etc.
- Quik! Forms Engine Property List
- Configurations
- Receive the HTML form to display to the user
- Display the form to the user
- User completes the form and either prints or sends for e-signature (using the SIGN button in the form viewer).
Assumptions
This workflow assumes the following:
- Your CRM environment can call Quik! REST APIs
- Your CRM environment can display the HTML form returned by the Quik! Forms Engine
- Your user doesn’t need a complex form search and can rely only on form bundles.
- Form Bundles should be named intelligently, like (Custodian + Account Type, or Company + Form Bundle Purpose, etc.) “Schwab Individual Account”, “Fidelity IRA”, etc.
- Your allows you to map your CRM fields to the Quik! Field Definition so you can prefill forms
- Field Mapping could be done directly in the Quik! API call or you could build a custom mapping interface in the CRM (which is more complex)
- Field Mapping Guide

