Embed a Streamline Workflow in Salesforce Experience Cloud

Use the Streamline Form Embed Lightning Web Component (LWC) to let users signed in to your Experience Cloud site start and complete a Streamline workflow without leaving Salesforce. The component supports Lightning Web Runtime (LWR) sites, passes the signed-in user's identity to the workflow, and displays the workflow in an iframe on the same page.

Who Has Access?

Key Capabilities

• Stay inside Experience Cloud: The workflow opens in the page component instead of a new browser tab.

• Customize the Start view: Set the message, button label, button color, and component height in Experience Builder.

• Pass signed-in user context: Use the current Salesforce user's ID, first name, last name, email, and username in the Streamline workflow.

• Complete multi-step workflows: Continue from the HMAC incoming webhook to forms, document generation, Sign, and other supported workflow steps.

Before You Begin

Make sure you have:

• A published Experience Cloud site. Streamline Form Embed is an LWC and supports LWR sites.

• Streamline for Salesforce installed and connected.

• A published Streamline workflow that begins with an incoming webhook.

• A Streamline for Salesforce workflow trigger for that incoming webhook.

• The Streamline Experience Cloud permission set available for signed-in site users.

Part 1: Prepare the Streamline Workflow

1. In Streamline, open the workflow you want to embed.
2. Add or confirm an Incoming Webhook as the first step.
3. Set Authentication to HMAC and select the incoming-webhook credential used by your Streamline for Salesforce workflow trigger.
4. Connect the webhook to the first person step that signed-in site users should see.
5. Map any current-user values you need from the incoming webhook to your form or later steps.
6. Publish the workflow.

Part 2: Create the Salesforce Workflow Trigger

Follow How to Add a Streamline Workflow Button and Track Session Status in Salesforce to create the workflow trigger. During setup:

1. In Salesforce, open the Streamline app.
2. Open Workflow triggers.
3. Create a workflow trigger for the Streamline workflow you want to embed.
4. Ensure Secure with HMAC signature is checked. The Experience Cloud embed requires an HMAC workflow trigger.
5. Select the Salesforce Object and test record.
6. Save the trigger.

Note: The selected object determines which Salesforce record data can be sent through the incoming webhook.

• User identity is always sent: The signed-in user's Salesforce user ID, first name, last name, email, and username are included. You can map these values to prefill fields even when the user does not have an associated Contact.

• Reduce a data-search step with Contact or Account: If the Experience Cloud user is associated with a Salesforce Contact, selecting Contact as the trigger object automatically includes that Contact's information. If the Contact is also associated with an Account, selecting Account automatically includes that Account's information instead. Streamline for Salesforce includes the record for the object you select, not both records. You can map its fields directly without adding a separate Salesforce data-search step. If Salesforce cannot resolve a matching record, the workflow still starts with the signed-in user's identity.

Part 3: Add the LWC to an Experience Cloud Site

1. Open your Experience Cloud site in Experience Builder.

2. Open the page where users should use the workflow.

3. From Components, drag Streamline Form Embed onto the page.

4. In the component properties, select the Workflow trigger.

5. Configure the Start view:

• Record Id: Leave blank unless the page supplies a Salesforce record to associate with the session.

• Start message: Enter the instructions displayed above the button, or leave blank for the default message.

• Start button label: Enter the button text, or leave blank for Start.

• Start button color: Select the button background color.

• Height (px): Set the iframe height. The minimum is 200 pixels and the default is 600 pixels.

6. Click Publish, then confirm the publish action.

Note: Changing the Workflow trigger resets the Start message and Start button label to their defaults.

Part 4: Give Site Members Access

For each user who needs to start an embedded workflow from the published site:

1. In Salesforce Setup, open the user's record.
2. Open Permission Set Assignments.
3. Assign Streamline Experience Cloud.
4. Confirm the user can sign in to the published site and access the page containing the component.

The permission set allows the signed-in user to start the selected embedded workflow. It does not grant access to the Streamline Salesforce app, workflow-trigger administration, or HMAC secrets.

Part 5: Test the Embedded Workflow

1. Sign in to the published Experience Cloud site.
2. Open the page containing Streamline Form Embed.
3. Confirm the Start message and button styling.
4. Start the workflow.
5. Confirm the workflow appears inside the page.
6. Check any fields mapped from the current signed-in user.
7. Complete the workflow and confirm the completion message appears.

Feature Considerations

• Streamline Form Embed is an LWC and supports LWR Experience Cloud sites.

• Users must be signed in to the Experience Cloud site to start the workflow.

• Incoming webhook must use HMAC authentication.

• The workflow must be published before the live site can run its latest configuration.

• To begin another session after completing a workflow, reload the Experience Cloud page.

Troubleshooting

The Workflow trigger list is empty

• Confirm the workflow trigger uses HMAC.

• Confirm its incoming webhook step and credential are still valid.

• Confirm the Experience Builder user has a Streamline permission set that can read workflow triggers.

• Reload Experience Builder.

The trigger list says to assign a Streamline permission set

Assign the Experience Builder user the appropriate Streamline Admin or Streamline User permission set, then reload the page.

Start returns "The Apex request is invalid"

Assign Streamline Experience Cloud to the signed-in site user. Do not use the broader Streamline User permission set for a Customer Community user.

The workflow does not appear after selecting Start

• Confirm the Streamline workflow is published.

• Confirm the incoming webhook returns a secure resume URL.

• Ask your Salesforce administrator to check the browser console for an iframe Content Security Policy error.

Current-user fields are blank

• Map the fields from the incoming webhook's current-user values.

• Publish the workflow again.

• Start a new session from the Experience Cloud page.

The Sign step reports an invalid configuration

Confirm the preceding Document step contains a Signature field and that the Sign participant is configured From previous step.

The session does not appear on the Salesforce record

• Confirm Write session statuses back to Streamline Session Status object is enabled.

• Confirm the page record or signed-in user's Contact or Account uses the same object as the workflow trigger.

• Start a new session after enabling status storage. Existing sessions are not backfilled.