In the Workiva platform, there are several ways to initiate a chain. This article explores the different options available, their benefits, and why you might choose one method over another.

Here is a link to a support article that covers these methods in detail:

Run Chains

Manual Execution (Ad Hoc)

Users can manually start a chain by selecting the "Run Chain" option directly within the Chains interface. This method is ideal when you need to provide variable inputs each time the chain is run.

For example, if you're running a chain that loads data into a table and requires a different file name for each execution, manually running the chain allows you to specify these inputs as needed.

Run Chain Link

Workiva provides the option to generate a "Run Chain" link, which can be embedded in a spreadsheet, document, presentation, or any other accessible location. Clicking this link takes the user directly to the chain, ready to be executed.

This method is particularly useful when a chain process is documented in a spreadsheet and you want a straightforward way to run the chain without having to navigate through the chain builder tool.

Here is a support article that covers how to find a chain’s external run URL:

Find a chain’s external run URL

Scheduled Execution

Scheduling is one of the most common methods for starting a chain. This option is typically used when minimal user intervention is required. For example, you might schedule a chain to run automatically at specific intervals to retrieve updated data from a source system, refresh connections, or maintain an up-to-date spreadsheet within the platform.

Workiva’s scheduler is user-friendly and offers advanced customization, allowing you to specify exactly when and how often a chain should run.

The Run Chains support article covers scheduling a chain execution in further detail:

Run Chains

API Execution

For those who prefer to use external tools to initiate a chain, the Workiva platform offers the Execute a Chain API. This method is ideal when users don't need to interact with the platform directly to start a chain.

With API execution, you can pass specific runtime parameters to the chain and monitor its success based on the API response. This method is commonly used by IT and security teams for tasks like audit-specific chains or data retrieval processes that are part of a larger API-driven workflow.

Webhook Execution

Another method for executing a chain via an HTTP POST request is by using a webhook event. This can be set up by utilizing the HTTP Webhook command within chains.

For this to work, the HTTP Webhook command must be the first command in your chain, as it initiates the chain upon execution.

The command will generate a URL that you will use to call the webhook through an HTTP POST request. You'll also need to manually add a Bearer Token for authentication.

For more detailed instructions on setting up a webhook trigger event, refer to our support article:

HTTP Webhook Trigger Event

Run Chain Events

Users can execute one chain within another by using the Run Chain command. This feature is particularly useful for running sub-processes that are triggered by a top-level chain.

Additionally, it's often employed when scheduling multiple chains, as it allows you to pass runtime parameters to the targeted chain efficiently.

For more detailed guidance on using Run Chain events, visit our support page:

Run a Chain Within Another Chain