Skip to main content

Execute workflow

Y
Written by Yuliia Biletska
Updated over 2 months ago

Once you have created the workflow or obtained the corresponding permissions for already built one, you can execute it and send documents.

To execute a workflow, you must first create it by following the instructions in this article.

There are three ways to send documents once the setup process is completed: executing a published workflow, using the Start link, or using the autostart trigger.

Execute workflow

Hover over the desired workflow and click Execute.

Alternatively, the Execute option is available on the page of the desired workflow. Simply click on the workflow name to access it.

Select Execute.

If the signers have already been added to steps, the invitations to complete the documents will be sent out. Otherwise, you'll be prompted to enter their email address, phone number, or name from your contacts. By default, the step is assigned to the workspace owner.

By selecting the Customize message option, you can modify the message sent to the workflow signers.

Once done, click Execute and proceed to the package monitoring. To learn more about the Status page, check this article.

Note: The unpublished drafted versions are marked as Draft.

Start link

Another convenient way to initiate a workflow and share documents is through the Start link feature. With this functionality, you can easily distribute a link via email, messaging platforms, or any other preferred method of communication.

Click on the workflow name to access it.

Select the Start link option.

Tick the toggle to activate the Start link functionality. Now you can copy and send the link to anyone who needs to fill out the documents in your workflow.

Trigger for automatic workflow execution

A trigger in a workflow is an event or action that initiates its execution. When certain conditions are met—such as data being updated or added—the trigger activates the workflow, leading to actions like sending documents.

Check the instructions for setting triggers in this section of the Support portal.

Did this answer your question?