Use cases

1. Your HR department chooses to extend a job offer to a candidate from one of your apps.
2. Your app calls the Workflow Builder API Workflows: triggerWorkflow endpoint to start your onboarding Workflow Builder workflow to start the agreement process.
3. Your workflow starts. The first step is a web forms module, which collects personal information from the customer that you need to create a new profile. You can optionally prefill this form with candidate info from your HR app by using data IO extension app.
4. The Docusign ID Verification (IDV) module verifies that the user’s government-issued identification matches the identity documents they provide. Within a Workflow Builder workflow, IDV can be used before or after collecting information from web forms.
5. Next, the customer signs employment documents with Docusign eSignature, including tax forms based on location using branching rules. The customer’s data provided in step 1 is added, generating a personalized and pre-filled document for their review and signature.
6. Finally, the workflow calls the Google Drive extension app and saves a copy of the completed agreement in a Google Drive cloud archive folder named for your workflow process.
7. After the workflow is completed, your app’s subscribed Docusign Connect listener receives a workflow-completed event, enabling it to respond by starting additional processes and alerting your users.

Note: Extension apps such as the example Salesforce and Google extension apps referenced in the use case must be installed and enabled from the App Center by an account administrator.

1. A sales representative from within your app has been notified via the Agreement Manager API that an important customer contract will soon expire. In response, they choose to send a new contract for renewal.
2. Your app calls the Workflow Builder API Workflows: triggerWorkflow endpoint to start your renewal workflow.
3. A Data IO extension app pulls data from your system of record to personalize and prefill the contract with the client’s information.
4. Present the customer with a web form to collect any new or additional information.
5. The customer signs the contract with Docusign eSignature.
6. The new contract data is updated to your system of record using a Data IO extension app and archived in your cloud storage system.
7. After the workflow is completed, your app’s subscribed Docusign Connect listener receives a workflow-completed event, enabling it to respond by starting additional processes and alerting your users.

Note: Extension apps such as the example Salesforce and Google extension apps referenced in the use case must be installed and enabled from the App Center by an account administrator.

1. One of your customers chooses to update their account information, such as their name, address, or beneficiary. They select an option in your app to begin this workflow.
2. Your app calls the Workflow Builder API Workflows: triggerWorkflow endpoint to start your update account workflow.
3. The customer fills out a web form and provides information required to verify their identity.
4. The Docusign ID Verification (IDV) module verifies that the user’s government-issued identification matches the identity documents they provide. Within a Workflow Builder workflow, IDV can be used before or after collecting information from web forms.
5. A Data IO extension app looks up the customer’s account record.
6. The customer fills out a change-of-information web form. Data from previous steps is used to personalize and prefill the form with the client’s information.
7. The user signs with Docusign eSignature.
8. A Data IO extension app updates the customer’s information in your system of record.
9. After the workflow is completed, your app’s subscribed Docusign Connect listener receives a workflow-completed event, enabling it to respond by starting additional processes and alerting your users.

Note: Extension apps such as the example Salesforce and Google extension apps referenced in the use case must be installed and enabled from the App Center by an account administrator.