> For the complete documentation index, see [llms.txt](https://gitbook.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.com/docs/developers/integrations/guides/send-data-to-a-webframe.md).

# Send data to a webframe

This guide builds a block that sends text input to a webframe. The webframe displays the latest text value.

### Before you start

You need a local integration project and a page that your webframe can load. Follow the [integration quickstart](/docs/developers/integrations/quickstart.md) before continuing.

### Add the component

In your integration entry file, create and register the component:

```typescript
import { createComponent, createIntegration } from '@gitbook/runtime';

const webframeData = createComponent({
  componentId: 'webframe-data',
  render: async (element) => (
    <block>
      <textinput
        state="content"
        label="Message"
        placeholder="Enter a message"
      />
      <webframe
        source={{ url: '/iframe.html' }}
        data={{
          content: element.dynamicState('content')
        }}
      />
    </block>
  )
});

export default createIntegration({
  components: [webframeData]
});
```

Replace `/iframe.html` with the URL served by your app. `dynamicState` sends updated input values to the webframe.

### Receive the data

In the page loaded by the webframe, listen for messages from GitBook:

```javascript
window.addEventListener('message', (event) => {
  const content = event.data.state.content;

  document.querySelector('#message').textContent = content ?? '';
});
```

Add an element with the `message` ID to the page. The handler updates that element when GitBook sends new state.

### Add the block to your manifest

In `gitbook-manifest.yaml`, add the block to the `blocks` list:

```yaml
title: My integration
blocks:
  - id: webframe-data
    title: Webframe data
```

The manifest block ID must match `componentId`.

### Test the block

1. Start your integration with the development command.
2. Insert **Webframe data** from the inline palette.
3. Enter text in the block.

The webframe receives the updated value in `event.data.state.content`.

### Next steps

Use the [webframe reference](/docs/developers/integrations/development/contentkit/reference.md#webframe) to access page context, visitor claims, and navigation actions.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://gitbook.com/docs/developers/integrations/guides/send-data-to-a-webframe.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.