> For the complete documentation index, see [llms.txt](https://docs.lleverage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lleverage.ai/administer-and-govern/control/connections/typeform.md). # Typeform Typeform integration in Lleverage connects your workflows and agents to your forms, so submissions can flow straight into automated processes the moment they arrive. ### How to Connect 1. **Go to Control → Connections** in your project 2. **Pick Typeform** from the list of apps 3. **Choose which actions** the connection should allow and who should have access (shared or personal) 4. **Choose "Connect Now"** and sign in with your Typeform account, or send an authentication link so a colleague can connect on your behalf > 💡 Typeform signs in with your Typeform account (OAuth), so there's no API key to manage. ### What Typeform Can Do * **Forms and workspaces** - list your workspaces and forms, and retrieve a form's details * **Responses** - fetch form responses for processing, and delete responses when they're no longer needed * **Webhooks** - create, inspect and remove the webhooks that deliver responses to other systems ### Triggers Typeform provides one trigger: **a form response is submitted**. Typeform notifies Lleverage the moment someone completes your form, so the workflow starts straight away with the submission's answers available as variables. > 💡 **Use case**: Route new sign-ups into your CRM, send a tailored follow-up email based on someone's answers, or start an approval process from an internal request form. ### Important Considerations * The connection works with forms the signed-in Typeform account can access * Deleting responses is permanent, so use it carefully in automated flows --- # 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.lleverage.ai/administer-and-govern/control/connections/typeform.md?ask=&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.