Integration · Automate and collaborate
Typeform and Meteor AI agents
Connect Typeform to a Meteor AI agent: build forms, measure their responses and manage contacts and automations, with 67 tools.
How does Typeform connect to Meteor?
With Typeform connected, your Met reads and writes in your company's Typeform account. It lists your forms, creates a new one, edits it with validated changes and publishes it when you ask. It measures responses with counts, averages, NPS, rankings and time series, and manages your contacts, their lists and the automations that react to each submission. Typeform's official server gives it 67 tools; whatever your plan does not include, Typeform rejects at the moment it is used.
What it automates
What a Meteor Met does with Typeform
Measure satisfaction without opening Typeform
From the internal chat, your team asks the Met for the NPS or the average of the month's survey, and it computes it with Typeform's response queries.
Build a form from a description
Your team describes the form it needs and the Met creates it, adds the questions with validated changes and publishes it only when asked.
Move respondents into your contacts
The Met connects the form's fields to contact properties and schedules importing the responses into Typeform's contacts database.
Alert your team on each submission
The Met creates an automation that, when a response arrives, sends an email or calls a webhook, and publishes it so it starts working.
67 tools
Everything your Met can ask Typeform for
Each one is a real action in the connector. You can switch off the ones you would rather it never used.
| Tool | What it does |
|---|---|
accounts_list_accounts | Lists the connected person's Typeform accounts; almost every other tool needs that account. |
workspaces_list_workspaces | Lists the visible workspaces, with their name, ID and how many forms they hold. |
forms_public_get_capabilities | Returns the question types, operations and logic operators that form editing supports. |
forms_public_get_form | Brings a form's current state, in full, only its questions or only its structure. |
forms_public_list_forms | Lists the connected person's forms, with search and pagination. |
forms_public_create_form | Creates an empty form in a workspace and returns its ID. |
forms_public_validate_patch | Validates a batch of changes against a form draft without saving anything. |
forms_public_patch_form | Applies validated changes to the draft; they are saved but not published. |
forms_public_publish_form | Publishes a form's draft and makes it live. |
forms_public_duplicate_form | Copies a form into another workspace, unpublished and without its third party connections. |
forms_public_update_form_metadata | Changes a form's title. |
forms_public_delete_form | Deletes a form by its ID. Starts switched off. |
themes_public_list_themes | Lists the available themes, your own, brand kit ones and, if asked, Typeform gallery themes. |
themes_get_theme | Brings a theme by its ID, whether your own, from a brand kit or from the gallery. |
themes_create_theme | Creates a form theme from scratch or by copying an existing one. |
themes_update_theme | Changes an existing theme; Typeform marks it destructive because it affects every live form using it. |
insights_public_discover | Returns which fields and measures of a form's responses can be queried; it goes before other queries. |
insights_public_aggregate | Computes counts, averages, sums and NPS for a field or for all responses. |
insights_public_timeseries | Groups measures over time, from hour to year, with up to two breakdown dimensions. |
insights_public_toplist | Returns top results and rankings, grouped by one or two dimensions. |
insights_public_list | Brings the responses to a single field of a form, paginated. |
automations_public_add_delay_step | Adds a delay step to an existing automation. |
automations_public_add_email_step | Adds an email step to an existing automation. |
automations_public_add_integration_step | Adds a step to an automation that sends the data to an integration. |
automations_public_add_webhook_step | Adds a webhook step to an existing automation. |
automations_public_create_automation | Creates a new automation in the Typeform account. |
automations_public_get_authorized_email_domains | Brings the authorized email domains for the current account. |
automations_public_get_automation | Brings an automation by its ID, in its working state. |
automations_public_get_email_notification | Brings the working state of an email notification template. |
automations_public_get_trigger | Brings an automation trigger by its ID, in its working state. |
automations_public_list_automations | Lists every automation in the connected account. |
automations_public_list_referenceable_fields | Lists the fields that can be referenced in an automation's emails and triggers. |
automations_public_patch_trigger | Changes an automation trigger by applying JSON Patch operations. |
automations_public_pause_automation | Pauses an automation by disabling its trigger, and optionally stops runs in progress. |
automations_public_publish_automation | Publishes an automation so it starts working. |
automations_public_remove_steps | Removes one or more steps from an existing automation. Starts switched off. |
automations_public_reorder_step | Moves an existing step to another position in an automation. |
automations_public_update_delay_step | Changes the duration of an existing delay step. |
automations_public_update_email_step | Changes an existing email step and its content. |
automations_public_update_webhook_step | Changes the configuration of an existing webhook step. |
contacts_public_get_contact | Brings a contact by its ID, with all its properties. |
contacts_public_get_contacts_database_properties | Brings specific contact properties from their IDs. |
contacts_public_get_contacts_list | Brings the details of a contact list by its ID. |
contacts_public_get_form_property_compatibility | Shows which contact properties are compatible with a form's fields and variables. |
contacts_public_get_form_property_mappings | Brings the setup that connects a form's fields to contact properties. |
contacts_public_get_form_property_mappings_by_id | Brings one form to contacts connection setup by its ID. |
contacts_public_list_contacts | Lists the contacts in the database, with filters and pagination. |
contacts_public_list_contacts_database_properties | Lists every property defined in the contacts database. |
contacts_public_list_contacts_lists | Lists every saved contact list. |
contacts_public_list_form_property_mappings | Lists every setup that connects forms to contact properties. |
contacts_public_bulk_create_contacts_lists | Creates one or more contact lists in a single call. |
contacts_public_bulk_create_custom_contacts_database_properties | Creates several custom contact properties in a single operation. |
contacts_public_bulk_upsert_contacts | Creates or updates several contacts in a single operation, matching them on a unique identifier. |
contacts_public_create_contact | Creates a new contact in the contacts database. |
contacts_public_create_contacts_list | Creates a new contact list in the database. |
contacts_public_create_form_property_mappings | Connects a form's fields to contact properties. |
contacts_public_delete_contact | Deletes a contact from the database. Starts switched off. |
contacts_public_delete_contacts_database_properties | Deletes several custom contact properties; it cannot be undone. Starts switched off. |
contacts_public_delete_contacts_database_property | Deletes one custom contact property; it cannot be undone. Starts switched off. |
contacts_public_delete_contacts_list | Deletes a contact list from the database. Starts switched off. |
contacts_public_delete_form_property_mappings | Deletes a form to contacts connection setup. Starts switched off. |
contacts_public_enable_standard_contacts_database_properties | Turns on one or more standard contact properties that were disabled. |
contacts_public_import_form_responses_by_mapping | Schedules importing a form's responses into contacts, using an existing connection. |
contacts_public_update_contact | Updates the properties of an existing contact. |
contacts_public_update_contacts_list | Changes the name or the filters and sorting of a contact list. |
contacts_public_update_form_property_mappings | Replaces every field connection in a form to contacts setup. |
submit_feedback | Sends Typeform a blocker report or comments about its MCP server. |
The limits
What the Typeform integration does NOT do
We would rather say it here than have you find out during rollout.
-
It does not bring full responses row by row, nor delete or export them: Typeform leaves that to its Responses API. Through this connector it reads one field at a time or aggregated results.
-
It does not create, change or delete workspaces, move forms between them or return embed codes for a form: Typeform does not offer them through its MCP server.
-
It does not serve accounts with data residency in Europe, which is an Enterprise plan feature and uses other server addresses.
-
It does not ask for confirmation in the chat before writing. Deleting forms, contacts or steps starts switched off, and the workspace admin chooses which actions stay on.
-
Your company pays for Typeform usage under its plan. If a feature is not in your plan, Typeform rejects the call at that moment; Met does not charge Energy for these calls.
Before you start
What you need to connect Typeform
- 1
A Typeform account
The account your company already uses works. Every account sees the same tools, but what each one can do depends on its plan.
- 2
Connect it in Met
In Met, open Connections, then Typeform, then Connect. A Typeform window opens so you sign in and authorize Met. Typeform asks you to accept all its permissions to connect.
Frequently asked questions
Questions about Typeform and Meteor
Changes stay in a draft until it is published. Typeform says to publish only when the person explicitly asks, and the admin decides whether that action stays on.
Not through this connector. Typeform only offers responses one field at a time and aggregated results through MCP; the full response stays in its Responses API.
Because Typeform checks your plan when each feature is used. If your plan does not include, for example, video answers, it rejects publishing a form that uses them.
Not in Typeform: today it asks you to accept all its permissions to connect. In Met, the admin does choose which actions stay on, and the delete ones start switched off.
Step by step
Automations that use Typeform
Complete tasks, with the steps and the tools that run at each one.
Automate and collaborate
Other integrations in the same family
Want to see a Met running Typeform?
We will show you with your own account connected, not with a canned demo.