Shopify Flow app
Shopify Flow is a 1st-party app developed by Shopify that is free to use, giving merchants the ability to automate all sorts of processes within Shopify. Newer Shopify stores may already have the Flow app installed by default, while older stores may need to install it manually from the app store.
New to Flow? If you're unfamiliar with Shopify Flow and would like to learn more, we suggest reading the manual in Shopify's Help Center: https://help.shopify.com/en/manual/shopify-flow
Company application metaobjects
All of the data collected from Onboard's company application form is saved directly into Shopify as a metaobject. Every application that is submitted is recorded as a separate metaobject entry, with each entry referencing the customer who submitted the application form. Most of the fields within the metaobject are used to store the unique field values customers provide, while other fields are used to store attributes about the application, such as the application status (pending, approved, etc.) and a timestamp of submission.
Onboard B2B triggers and actions
The Onboard app has its own set of Flow triggers and actions that allow you to create custom automations based on application events or to interact with applications and companies. In the Flow editor, search for Onboard B2B when selecting a trigger or action. The app is listed as Onboard B2B: Company Profiles.
Triggers
Each trigger returns data for the customer to which the application belongs, as well as the metaobject ID and metaobject handle of the application itself.
Application received
Trigger a workflow when a new company application is created
Application rejected
Trigger a workflow when a company application is rejected, and a revision has been requested
Application revised
Trigger a workflow when a customer submits a new revision for their company application
Application approved
Trigger a workflow when a company application is approved
This trigger also returns the ID of the company that was created
Application declined
Trigger a workflow when a company application is rejected and closed without a request for revision
Actions
Create company application
Creates a pending company application in the Onboard app and the corresponding application metaobject entry in Shopify.
This action requires a customer reference from the workflow trigger or previous action, as well as a variable for company name. There are additional optional company fields which can be set on the application.
Create company
Creates a company and company location in Shopify, without a company application.
This action requires a company name. You can also set the tax registration ID, external company ID, location name, shipping and billing addresses, and a company note.
Returns the IDs of the new company and company location.
Assign customer as company contact
Assigns an existing customer as a contact at a specific company location.
This action requires the customer ID and the company location ID. Check Grant location admin role to give the customer the Location admin role, or leave it unchecked for Ordering only.
Approve company application
Approves a pending application in the Onboard app and creates a company in Shopify.
This action requires the application metaobject ID which can be returned from one of the Onboard app's triggers or the Create company application action. Additionally, you can click Select preset to choose which approval preset is used, which allows applying certain attributes to the created company. If you don't select a preset, the Default preset is used.
Approvals made with this action count toward your plan's company approvals. If your store has reached its approval limit for the billing period, the action will fail.
This action does not send the Application approved email to the customer.
Standard metaobject support in Flow
Shopify Flow supports using metaobjects in triggers and actions, meaning you can create custom workflows to automate all sorts of business processes that relate to your B2B applications.
Example use cases
Use the Shopify trigger for 'Metaobject entry created' to trigger workflows whenever a customer submits a company application, including actions like sending an internal email notification or adding a tag to a customer.
Use condition blocks to check fields in the metaobject to add conditional logic.
Example: Send separate internal email notifications and assign different customer tags based on the value of a custom field on the application form.
Use variables within an action to include specific values from the company application.
Example: Include the company's name and physical address on internal email notifications.