> For the complete documentation index, see [llms.txt](https://docs.rewst.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rewst.help/documentation/automations/forms/embedding-a-form-into-an-iframe.md).

# Embed a form into an iFrame

### Embed forms

There is often a need to embed a form in an iframe to give users the ability to complete a form and trigger automation. The form can be embedded into other web pages that use iFrame links.

{% hint style="success" %}
To get the dynamic form URL, make sure your form is already set up as a trigger for a workflow.
{% endhint %}

### Get an embeddable link

Follow these steps to get the embeddable link.

1. Navigate to **Automations > Workflows**.
2. Click on the Workflow that includes the form trigger to open it in the Workflow Builder.
3. Click on the trigger to open its settings in the right side menu.
4. Click **Copy URL**.<br>

   <figure><img src="https://1835401289-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAQQ1EHVcEsGKBPVHmiav%2Fuploads%2FgAYRUGwFKV0sOYfe21Dg%2FScreenshot%202026-08-27%20at%203.33.55%E2%80%AFPM.png?alt=media&amp;token=f2d8270f-8e4f-4ccf-9724-095fd02b76f9" alt="" width="240"><figcaption></figcaption></figure>
5. Click **<>**. This copies the embeddable Iframe code. Paste the code into your compatible webpage editor.

<figure><img src="https://1835401289-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAQQ1EHVcEsGKBPVHmiav%2Fuploads%2FFC8da8wmWtd6S3fNJmM2%2FScreenshot%202026-08-27%20at%203.32.28%E2%80%AFPM.png?alt=media&amp;token=2abc7635-b3d5-4301-9fbe-64100cc02833" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rewst.help/documentation/automations/forms/embedding-a-form-into-an-iframe.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
