Embedding Workflows on Your Website

This article explains how to embed an Intellistack Streamline workflow on your website, portal, or application so that users can complete workflows without leaving your site.

Before You Begin

To embed a workflow, the following conditions must be met:

• The workflow must be set to No authentication
• The workflow's first step must be either an Incoming Webhook step or a Form (New) step
• The first step must not be assigned to a specific user or group

If the first step of the workflow is of a different type than those listed above, the embedded workflow will fail to load, and users will see an error message. This also applies to the older Form step type, which must be replaced with a Form (New) step for embedding to work. 

Generating an Embed Code

1. Open your project and navigate to the workflow you want to embed
2. Select the Share drawer from the project details page
3. Under the Embed section, copy the provided iframe code snippet
4. Provide the code snippet to your web team or paste it into your website's HTML

The embed code works on any platform that supports HTML, including WordPress, Webflow, Drupal, SharePoint, and custom-built sites. No additional SDKs, build tools, or package managers are required.

For more technical details - including auto-resize behavior, iframe configuration, and postMessage event handling - see Embedding Workflows on the Intellistack Developer Portal.

How Embedded Workflows Work

Once the embed code is placed on your site, the workflow loads automatically when the page loads. Users can begin interacting with the workflow immediately.

Embedded workflows support the full range of Streamline workflow functionality, including:

• User-facing steps such as forms and document signing
• Background steps such as data activation, integrations, and routing
• Multi-step workflows with conditional logic
• Responsive layout across desktop, tablet, and mobile devices

When a workflow includes non-user-facing steps (for example, document generation or integration calls), users see appropriate status messages while those steps run in the background.

Session Behaviour

A session is created when the first step of the workflow is completed. For workflows that begin with a Form step, this means the session starts after the user submits the form. For workflows that begin with an Incoming Webhook step, session creation depends on your implementation. If your application triggers the webhook on page load, a new session is created each time the page loads. If your application requires a user action (such as a button click) to trigger the webhook, a new session is only created when that action occurs.

Embedding Behind an Authenticated Portal (Secure Embed)

If you want to embed a workflow behind your own authenticated portal - for example, an employee intranet, customer portal, or partner site - and prefill workflow fields with data from your logged-in user, you can use the secure embed approach.

To set this up:

1. Set the workflow to No authentication
2. Add an Incoming Webhook step as the first step of the workflow
3. Enable HMAC authentication on the incoming webhook step

With HMAC enabled, your system controls who can start workflow sessions, even though the workflow itself is not authenticated. This is useful for authenticated portals, but also applies to any scenario where you want to control who can initiate a session - for example, triggering a workflow from a backend service or restricting access to a specific application.

For step-by-step setup instructions, see HMAC Authentication for Incoming Webhooks .

For technical implementation details and API reference, see Embedding with HMAC Authentication on the Intellistack Developer Portal.

Updating an Embedded Workflow

When you make changes to a workflow in Workflow Builder and publish them, all embedded instances of that workflow update automatically. You do not need to regenerate or replace the embed code.

Removing an Embedded Workflow

To stop an embedded workflow from being accessible:

• Remove the embed code from your website, or
• Change the workflow from No Authentication to Login Required in Workflow Builder. Users will not be able to submit the workflow.

Troubleshooting