Berner Setterwall5 min read

    Fillout Is Live in Cogny: Read Form Leads and Registrations, Import Rows and Manage Webhooks from an Agent

    If your forms run on Fillout, the submissions they capture are your lead and registration data — every signup, booking, application and poll response sitting in each form's Results. Until today none of it was reachable from a Cogny agent. Now it is: Fillout is a live MCP integration in the catalog alongside HubSpot Forms, Typeform-style survey builders and the rest of the data connectors.

    No OAuth dance and no developer app: one organization API key created in Fillout in about a minute, pasted once into Settings → Cogny Managed MCPs, and your agent is in.


    TL;DR

    • Fillout is live now. Connect it with an organization API key from your warehouse Settings → Cogny Managed MCPs.
    • 8 tools across forms, submissions and webhooks. The read tools cover your form list, each form's question schema, and a form's submissions — paginated and filterable by date, status (finished / in-progress), sort and search.
    • Import rows into Results. create_submissions adds up to 10 stored submissions to a form in one call — useful for bringing offline or older leads into a form you already report on.
    • Deletes and webhooks are flagged and confirm-gated. delete_submission permanently removes a response (destructive), and create_webhook makes Fillout POST every future submission to an external URL — so it sends data out of Fillout and carries a clear "only for an endpoint you control" note. Both describe what they do and are marked so an agent doesn't run them by accident.
    • The Forms API can't create or edit forms — only read them. Submissions created through the API don't trigger Fillout's email notifications, workflows or integrations.
    • The Buying Intent Signals scheduled template now recognizes Fillout for the form-fill signal, alongside HubSpot Forms.
    • Works from any MCP client on app.cogny.com/mcp.
    • Included in Solo ($9/mo); bring your own agent and the standard MCP tools run under fair use.

    What you can do with it

    AreaWhat Claude can do
    FormsList the forms in your organization (list_forms), and read one form's schema — its questions and their ids, plus calculations, URL parameters, scheduling and payment fields (get_form_metadata)
    SubmissionsList a form's submissions with date, status, sort and search filters and pagination (list_submissions), or pull a single response (get_submission)
    ImportCreate up to 10 stored submissions in a form, importing lead or registration rows into its Results (create_submissions)
    DeletesPermanently delete a submission by id (delete_submission) — destructive, confirm before running
    WebhooksCreate a webhook so Fillout POSTs every future submission of a form to a URL you control (create_webhook), and remove one by id (remove_webhook)

    In plain terms: "Which forms captured new leads in the last 7 days, and how many were finished?" "Pull every submission this month with an email ending in @acme.com." "Import these 30 older registrations into the March event form's Results." The answers — and the imports — happen against Fillout's own API, not a spreadsheet.

    Reading a form's schema first

    Because Fillout submissions store answers keyed by question id, the connector's two reads work together: get_form_metadata tells an agent what question ids a form has, and list_submissions / get_submission pull the rows those ids hold. Resolving a question id here is also the right first step before create_submissions, so an import writes answers under the correct questions.

    Writes stay narrow on purpose

    The first release is deliberately limited:

    • Import is additive. create_submissions adds new stored submissions to a form's Results; it can't rewrite an existing response, and it isn't idempotent — calling it twice creates duplicates. That's stated plainly so an agent doesn't re-run an import by accident.
    • One destructive delete. delete_submission permanently removes a response and carries the destructive annotation, so the UI flags it before it runs.
    • Webhooks are yours to own. create_webhook makes Fillout POST every future submission to the URL you give. It isn't idempotent — calling it again creates another webhook — and because it sends data out of Fillout, its description says to pass only an endpoint you control and trust, and to confirm before creating one. remove_webhook stops one by its id.
    • No form editing, no audience posting. The Forms API can't create or edit forms. And none of the tools post to an audience: this connector reads captured leads and imports rows, it doesn't send anything to your contacts.

    Reading is read-only, and honest about it

    The read tools are genuinely read-only. Every tool carries MCP behavior annotations, so Cogny's UI and Claude.ai connectors know which ones read, which write, and which touch a destructive path. Fillout rate-limits at 5 requests per second per key, and creating or deleting submissions at 10 per minute — on a 429 the integration names the limit clearly instead of guessing.

    How to connect it

    1. In Fillout, open your organization name → Settings → Developer → API key → Enable API, then click Copy. It is one org-wide key.
    2. In your warehouse Settings → Cogny Managed MCPs, click Connect on the Fillout card and paste the API key. If your organization is EU-hosted, set the region field to https://eu-api.fillout.com/v1/api (the connector defaults to the US host).

    The key is stored encrypted and sent only to Fillout's API. Because it's an org-wide key, it carries the access your whole organization's forms have — if you want it read-only in Cogny, keep the Fillout admin who created it read-only. Disconnect any time with one click, and disable the key back in Fillout's Developer settings if you ever stop using Cogny.


    If your forms run on Fillout, this is the connector that puts your leads and registrations one prompt away — and lets you import the rows that never made it in. Connect it from your Cogny dashboard and ask your first question.