Embedding workflow webforms in your app

Author headshot
By Ben Ogle

Learn how to embed Workflows in an iframe: collect user information, fill PDFs, and gather e-signatures, all from within your app.

Back to all articles
Post hero image

A central feature of Anvil is Workflows. Workflows allow you to collect data from your users via a simple webform, automatically fill PDFs with the user's data, then gather signatures from relevant people.

For example, say we wanted our client to sign an NDA. We can give our client an easy webform to fill:

Workflow webform nda example

When the client is finished filling the webform, it will fill the NDA with their information, then ask them to sign:

embedded Workflow e signature

You can embed this entire process in an iframe on your app or website. That way, you control the experience, and a user does not need to leave your site to fill and sign our hypothetical NDA.

In this post, I'll show you how to

  • Embed the webform filling and signature UIs in your app or website
  • Start Workflows
  • Have your app notified when actions take place. For example, when the user submits a page, or completes the Workflow
  • Download the documents when the user is finished

Note: please contact us at to enable form embedding for your Anvil organization.

Embedding the form in an iframe

Embedding the webform UI in an iframe is extremely easy. All you need to do is point the src attribute at your Workflow's webform URL.


And you will see the form inside your own app:

Workflow webform nda example

Starting a Workflow

There are two ways to start a Workflow submission for one of your users:

  1. Embedding a special URL to kick off a new submission
  2. Creating a Workflow submission via the API

Option 1: Embed a special URL

Embedding a form URL without an ID will create a new Workflow submission (a WeldData). This approach is the easiest way to get a Workflow submission started and seeded with your own data.

In our case, our iframe URL would look like this:

  src='{"name":"Sally Jones"}'

Note the d param, it will seed the new Workflow submission with data from your system. See the Workflow UI URLs docs for all the options available.

Option 2: Create a Workflow submission via the API

An alternative to creating a Workflow submission with a special URL is starting the Workflow with the GraphQL API, then embedding the resultant form URL. This approach is a little more complex, but gives you full control over the submission.

Often customers with complex Workflows use the API method to start Workflows because it allows for more flexibility. With the API method, you can specify a specific webhookURL for the Workflow submission, seed multiple forms in a Workflow, and more.

To create a Workflow submission, use the forgeSubmit mutation. Our node API client supports the forgeSubmit mutation out of the box:

// Uses the Anvil client, see
const result = await anvilClient.forgeSubmit({
  variables: {
    forgeEid: forge.eid, // your webform's eid
    complete: false,
    isTest: false,
    // Seed the submission with data here...
    payload: {
      name: Sally Jones,

// You will embed the resulting `weldData.continueURL` in the iframe
const responseData =
const embedURL = responseData.weldData.continueURL

Then in the HTML, you would use embedURL in the iframe's src attribute:


See the forgeSubmit docs for more information on using forgeSubmit. The basic mutation call used above to start a Workflow is as follows:

mutation ForgeSubmit(
  $forgeEid: String!,
  $weldDataEid: String,
  $submissionEid: String,
  $payload: JSON!,
  $complete: Boolean,
  $isTest: Boolean,
  $webhookURL: String,
) {
  forgeSubmit (
    forgeEid: $forgeEid,
    weldDataEid: $weldDataEid,
    submissionEid: $submissionEid,
    payload: $payload,
    complete: $complete,
    isTest: $isTest,
    webhookURL: $webhookURL,
  ) {
    weldData {

Getting notified

Your app can be notified when a user takes an action in two ways:

  1. JavaScript events from the iframe to the parent frame
  2. Webhook notifications

Events from the iframe

For some actions, the iframe will emit events that your parent frame can capture. These events will help you know when the user is finished filling a page, finished with the webform, and finished signing.

On the page that renders the iframe element, you can subscribe to the window's message event. The events emitted by the iframe should provide you with any ids you need to query our system for the user's submitted data.

window.addEventListener('message', ({ origin, data: messagePayload }) => {
  if (origin !== '') return
  // messagePayload will be an object in one of the formats
  // {
  //   action: 'forgeSubmitPage',
  //   organizationSlug: 'my-org'
  //   weldDataEid: 'bdwIX5TUiLBzldgdwzL2',
  //   forgeEid: 'wIX5TUiLBzldgdwzL2bd',
  //   submissionEid: 'X5TUiLBzldgdwzL2bdwI',
  //   pageId: 'somePageId',
  // }
  // OR
  // {
  //   action: 'forgeComplete',
  //   organizationSlug: 'my-org'
  //   weldDataEid: 'bdwIX5TUiLBzldgdwzL2',
  //   forgeEid: 'wIX5TUiLBzldgdwzL2bd',
  //   submissionEid: 'X5TUiLBzldgdwzL2bdwI',
  // }

Webhook notifications

On the server side, you can receive webhook notifications for several actions—Anvil will POST to an endpoint on your server. You can set up a global webhook URL in your organization's settings, or you can set a per-object webhook URL for each Workflow submission. In either case, your webhook URLs will receive the same event payloads.

The most important actions for Workflow embedding are:

  • forgeComplete - A user completes a webform
  • signerComplete - A signer finishes signing all of their documents
  • weldComplete - The Workflow submission is completely finished, all webforms have been completed, and all signers have finished signing

See the webhooks guide for more information on handling webhooks.

Downloading the documents

When all forms have been filled, and all signers have signed, it's time to download the documents. Download them in zip format with the following URL:

The best way to know when everything is finished is by way of the weldComplete webhook notification mentioned above. We recommend you download the zip in that webhook notification response handler.

Your specified webhook URL will be called with a JSON payload that contains the download URL. The webhook payload:

// Zip download URL is at `data.documents.url`
  action: 'weldComplete',
  token: '38Gp2vP47zdj2WbP1sWdkO2pA7ySmjBk'
  data: {
    eid: 'GHEJsCVWsR1vtCx3WtUI',
    documents: [{
      type: 'application/zip',
      url: '',
  // ... other data

Then you can request the file at[0].url:

const downloadURL =[0].url
const zipResponse = httpFetch(downloadURL, options)

If you are using our node API client, this is even easier with the downloadDocuments() function

const weldDataEid =
const zipResponse = await anvilClient.downloadDocuments(weldDataEid)

All done!

That's it! Now you have all the tools to embed a Workflow's form in your app or website, get notified when something happens, and download the finished documents.

Note that if you are already collecting your client's information with your own webforms, you can use Etch e-sign to fill PDFs with your data, create signature packets, and embed the e-signing UI in your app.

If you have questions, or want to enable Workflow embedding in your app, please do not hesitate to contact us at: