> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/framer.md).

# Framer

Framer is a no-code website builder. Connect a Framer site to receive form submissions in StackAI workflows.

### Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

| Connector | Authentication |
| --------- | -------------- |
| Framer    | API Key        |

#### Framer

Connect to a Framer site to receive form submissions and manage CMS content. Stores your Framer Server API key and project URL.

**Set up in Framer**

1. Open your site in Framer and make sure it has a published form whose submissions you want to capture.

**Set up in StackAI**

1. Open **Settings → Connections**, add a connection, and select **Framer**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field | Required | What to enter                                                                                                                                                                                                                                                                    |
| ------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| API Key       | Yes      | Your Framer Server API key. Generate one in your project's Site Settings → General. Stored to scope this connection to a single Framer project; not used for the Forms webhook trigger today. [Provider instructions](https://www.framer.com/developers/server-api-quick-start). |
| Project URL   | Yes      | Your Framer project URL. Either the editor URL (<https://framer.com/projects/Sites--…>) or the published site URL (<https://yoursite.framer.website>).                                                                                                                           |

**Provider documentation:** [Setup reference](https://www.framer.com/help/).

#### Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

### Triggers

A trigger starts a workflow when its configured event occurs. Configure the event and filters before enabling the trigger.

#### On Form Submission

Trigger a workflow execution every time a Framer form is submitted. Optionally verifies each request using a shared secret configured in Framer.

1. In Framer, open your form's settings → **Submit To** → **Webhook**. 2. Paste your StackAI webhook URL: {{webhook\_url}} 3. (Recommended) Set the same **Webhook Secret** here and in Framer (minimum 32 characters). When set, StackAI rejects requests whose `Framer-Signature` header does not match. Leave blank to accept unsigned submissions. 4. Publish the form. Each submission Framer makes will trigger this workflow.

**Configuration**

| Field          | Type   | Required | Description                                                                                                                                                                          |
| -------------- | ------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Webhook Secret | secret | No       | Optional shared secret used to verify that incoming requests really come from Framer. Set the same value in Framer's form webhook setup; leave blank to accept unsigned submissions. |

**Event inputs**

| Field         | Type     | Required | Description                                      |
| ------------- | -------- | -------- | ------------------------------------------------ |
| Submission ID | string   | Yes      | Unique submission ID assigned by Framer.         |
| Form Fields   | object   | Yes      | Submitted form fields keyed by their input name. |
| Raw Payload   | textarea | Yes      | Raw JSON body Framer posted to the webhook.      |

**Outputs**

| Field         | Type     | Description                                      |
| ------------- | -------- | ------------------------------------------------ |
| Submission ID | string   | Unique submission ID assigned by Framer.         |
| Form Fields   | dict     | Submitted form fields keyed by their input name. |
| Raw Payload   | textarea | Raw JSON body Framer posted to the webhook.      |

### Important behavior

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.


---

# 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.stackai.com/integrations/catalog/framer.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.
