Creating workflows
Creating a workflow from a set of templates
Before you start, create the templates the workflow will use. Workflow creation requires an Enterprise plan and permission to create workflows in the selected Studio location.
-
Open Studio and navigate to the destination folder.
-
Open the menu beside New, then choose Workflow.
-
In Select Workflow Type, choose API or Fillable Form, then click Select. Public Form appears only when enabled for your organization.

-
In Workflow Details, enter a required Name and optional Description. Review the Active switch and click Next.

-
In Packet Builder, find templates by browsing Studio folders or using Search templates. Select up to five templates and click Add to Workflow. Review the selected packet, remove unwanted entries, and arrange the output order before continuing.

Local demonstration using production application code and fictional data.
-
In Destinations, review the available destinations described below.

Local demonstration using production application code and fictional data.
-
In Mapping, supply or map the values required by your templates and selected destinations, including the output’s Inkit folder and applicable signer information.
-
In Forms, configure the form inputs as applicable to the selected workflow type. For a Fillable Form, arrange the fields, add instructions, and review preset values with Preview.

Local demonstration using production application code and fictional data.
-
Click Finish to create the workflow. Resolve any validation errors before leaving the builder.
The builder enables Next only when the current step is valid. Leaving with unsaved changes requires a choice to stay or discard them.
Adding additional destinations to a workflow
The current builder uses destination selections, not the old drag-and-drop destination cards.
| Destination | Current behavior |
|---|---|
| Inkit Storage | Included automatically. Choose the output folder in Mapping. Access to generated documents follows folder permissions. |
| Digital Signature | Detected from digital-signature fields in selected templates. Configure signers and rules in Mapping. |
| Salesforce | Available in supported commercial environments; configure the connection and mappings for the intended environment. |
| Magic Link | Appears when Magic Link is enabled for the organization/environment. |
| User Activation | Appears only when the feature is available and the packet contains an eligible signature field. It invites the requester and creates organization access when approved. |
Adding Salesforce as a document destination
Connect the correct Salesforce environment, select Salesforce in Destinations, and configure its required values in Mapping. Salesforce is not offered in the IL5 workflow builder.
Adding Magic Link as a document destination
When available, select Magic Link in Destinations and configure its required recipient and access settings in Mapping. Do not assume the legacy App Shop setup instructions apply to your environment.
Adding DocuSign as a document destination
DocuSign is not listed in the current workflow builder’s destination selector. For Inkit-native signing, use templates with Digital Signature fields and review the detected Digital Signature destination.
Adding Amazon S3 as a document destination
Amazon S3 is not listed in the current builder’s destination selector. The current Apps catalog marks AWS S3 as coming soon; confirm any existing account-specific integration with your administrator.
Adding Google Drive as a document destination
Google Drive is not listed in the current builder’s destination selector and is marked coming soon in Apps.
Adding Dropbox as a document destination
Dropbox is not listed in the current builder’s destination selector and is marked coming soon in Apps.
Adding Box as a document destination
Box is not listed in the current builder’s destination selector and is marked coming soon in Apps.
Adding Sepire as a document destination
Sepire is not listed in the current builder’s destination selector. Historical delivery integrations are not evidence that this action is available in the current UI.
Updated 11 days ago