Menu
Mattering Automations connector

A Fillout MCP that covers the entire published Fillout API

Fillout publishes eight API operations, and this connector is eight nodes. List your forms, read a form's questions and field metadata, pull submissions with the answers and the question text already attached, import up to ten rows at a time, delete one, and subscribe or unsubscribe a webhook. Nothing is missing, because nothing was left out.

8 ready-made nodes One credential to connect Works with Claude, ChatGPT, and Matter

What the Fillout MCP connector does

The Fillout connector for Mattering Automations is 8 nodes: four reads and four actions, with two flagged destructive. That number is the whole API rather than a slice of it. Two independent sources agree exactly on the count: Fillout's machine-readable API specification declares six paths carrying eight operations, and Fillout's own documentation index lists eight API reference pages, one per operation, with no page for an operation the specification omits and no operation without a page. So this page can be precise where most connector pages hedge: there is no unbuilt remainder and no advanced surface waiting behind a bigger plan.

It is worth being just as precise about what the API does NOT do, because a form product invites assumptions. Fillout's REST API is a submissions API with a read-only view of form structure. Forms are built in Fillout's editor and cannot be created, changed or deleted over the wire, and there is no question or field editing. There are no analytics or reporting endpoints of any kind, no workspaces, folders, teams or permissions surface, and no way to list, read, update or replay webhooks after creating them. Submissions can be listed, fetched, imported and deleted, but not updated. Everything in that paragraph is an absence in the vendor's API, not a gap in this connector.

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any other MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. Fillout does not publish an MCP server of its own: its documentation index contains no MCP page and no MCP reference anywhere. So for anyone searching for a way to give an assistant access to Fillout data, this connector is the answer rather than the alternative to one. An agent can list forms with Fillout: List Forms, read the question ids and types with Fillout: Get Form Metadata, and pull the answers with Fillout: List Submissions, and the same nodes run as steps on an automation canvas when nobody is there to ask.

The submission payload is friendlier than most, and it changes what a workflow has to do. Each submission carries a flat questions array where every entry holds the question's id, its TEXT as a name, its type, and the answer as a value, so a downstream step can address a field by the question people actually see without a second metadata call. Four sibling arrays ride along and are fully specified: calculations, the URL parameters captured at fill time, Fillout Scheduling bookings with their event times and reschedule links, and Fillout Payments records with the amount, currency, discount code and status. Quiz forms carry a score and a maximum, and login-gated forms carry the respondent's email. One honest caveat about the answer value itself: its type follows the question type and the specification does not enumerate the object shapes for structured questions like Address, Matrix, Table, File Upload, Signature, Payment and Subform, so a workflow that reads one of those should inspect a real submission first rather than trusting a guessed path.

Two nodes carry a destructive flag, and one of them is worse than it looks. Fillout: Delete Submission removes one submission and every answer in it, and Fillout documents no restore endpoint and no recovery window for an API-deleted submission, so nothing in a workflow can undo it. Fillout: Delete Webhook is aggravated by two absences: there is no webhook lister, so once a subscription is gone there is no way to enumerate what was removed, and there is no delivery log or replay, so every submission made between the removal and a re-subscribe is never delivered and cannot be re-sent. Recreating a webhook for the same form and URL issues a new id. Importing submissions is deliberately NOT destructive: it adds rows, returns their new ids, and deleting those ids restores the prior state exactly.

One connection, three surfaces

  • Visual automations. Drag Fillout nodes onto the canvas and wire them to triggers, conditions, and other apps.
  • AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
  • The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.

Every Fillout node, ready to drop on the canvas

8 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.

Read and query nodes 4

Fillout: Get Form Metadata

Describe one form: its questions with their ids, titles and types, plus any calculations, URL parameters, Fillout Scheduling fields, Fillout Payments fields and quiz configuration. This is the lookup table for both reading and writing submissions, because an answer is addressed by question id. The type tells you what an answer value will look like; the documented types are: Address, AudioRecording, Calcom, Calendly, Captcha, Checkbox, Checkboxes, ColorPicker, CurrencyInput, DatePicker, DateRange, DateTimePicker, Dropdown, EmailInput, FileUpload, ImagePicker, LocationCoordinates, LongAnswer, Matrix, MultiSelect, MultipleChoice, NumberInput, OpinionScale, Password, Payment, PhoneNumber, Ranking, RecordPicker, ShortAnswer, Signature, Slider, StarRating, Subform, SubmissionPicker, Switch, Table, TimePicker, URLInput. Fillout adds new types regularly and advises discarding unknown ones, so branch on type with a default case.

Fillout: Get Submission

Get one submission by its id, with the same answer shape the list node returns. Note the wrapper differs: the row sits under data.submission rather than inside an array, so a workflow written against the list node needs its paths adjusted.

Fillout: List Forms

List every form the API key can see, as an array of name and formId pairs. Takes no parameters and is not paginated, so it doubles as the credential health check (200 means the key works and reaches the right host, 401 means it does not). This is where form ids come from: every other Fillout node needs one. Note the response is a bare JSON array, so paths read data[].formId with no wrapper key.

Fillout: List Submissions

Read a form's submissions with the answers inline. Each row carries a submissionId, a submissionTime and a flat questions array where every entry holds the question's id, its text as name, its type and the answer as value. Filter by date range, search for submissions containing a piece of text, include unfinished (in_progress) submissions, and page with limit and offset against data.totalResponses and data.pageCount. The list key is responses, not submissions.

Action nodes 4

Fillout: Create Submissions

Import up to 10 submissions into a form in one call. Answers are addressed by question id, so read the ids from Fillout: Get Form Metadata first. Imported rows appear in the form's Results tab and come back with their new submissionIds, which is what makes this reversible: delete them to undo. Fillout states that submissions created through the API do NOT trigger email notifications, workflows or integrations, so this is a backfill and migration tool rather than a way to fire a form's downstream automations.

Fillout: Create Webhook

Subscribe a URL to a form's submissions. Fillout then posts each new submission to that URL in the same shape as an entry in the responses list from Fillout: List Submissions. The response is just the new webhook's numeric id, and there is no endpoint that lists webhooks afterwards, so store that id if you ever intend to remove the subscription. Reverse by deleting the webhook you just created. This node configures Fillout to call an endpoint YOU run: Mattering does not receive Fillout deliveries.

Fillout: Delete Submission

DESTRUCTIVE. Delete one submission and every answer it contains. Fillout documents no restore endpoint and no recovery window for a submission deleted through the API, so nothing in a workflow can undo this. Returns 200 with no documented response body.

Fillout: Delete Webhook

DESTRUCTIVE. Remove a webhook subscription so Fillout stops delivering that form's submissions. Fillout publishes no endpoint that lists webhooks and no delivery log or replay, so once a subscription is gone there is no way to enumerate what was removed, and every submission made between the removal and any re-subscribe is never delivered and cannot be re-sent. Recreating a webhook for the same form and URL issues a NEW id. Note the method is POST rather than DELETE: the id travels in the JSON body.

Connecting Fillout takes one credential

Fillout authenticates every request with an API key in the Authorization header as a bearer token. The key is generated in the Fillout app under Settings and then Developer, and it can be revoked or regenerated in the same place. Fillout documents no scopes and no per-key permissions, so one key does everything this connector does, deletes included. Fillout's pricing page lists REST API access as included on every plan, free included, so a key does not require an upgrade. There is no version header, no account id and no signature to compute. One thing besides the key belongs on the connection, and it is the detail that trips people up: the base URL is a property of the ACCOUNT rather than a constant. The default deployment answers at Fillout's primary API host, the EU agent answers at its own host, and a self-hosted installation answers at whatever address that account's API dashboard shows. A Fillout key is issued by one deployment and does not work against another, so the host lives on the credential beside the key rather than as a field on all eight nodes. Two things follow from that. A workflow cannot be pointed at the wrong host while holding a working key and leave you reading the resulting failure as a broken connector. And the form picker on six of the eight nodes stays correct for EU and self-hosted accounts automatically, because the picker runs through the same credential and therefore reaches the same host.

1

Open Fillout, go to Settings and then Developer, and generate an API key. Copy the value.

2

While you are there, note the API base URL the dashboard shows. On a default account it is Fillout's standard host and there is nothing to change; on the EU agent or a self-hosted installation it will be different and you will need it.

3

In Mattering Automations, open Connectors, click Add Connector, choose Fillout, and create a credential with the key. Set the region or the base URL override only if your account is not on the default deployment.

4

Click Test Connection. Mattering calls Fillout's form list, which is the only endpoint in the API with no path and no query parameters, so it proves the key and the host together in one request without needing a form id first.

5

All 8 Fillout nodes appear in the canvas palette. Run Fillout: List Forms first: it is where every form id comes from, and every other node needs one.

Common uses for the Fillout MCP

Route a form submission into everything that has to happen next

Fillout: List Submissions reads a form's submissions with the answers inline, and because each answer carries the question's TEXT alongside its id, the next step can address a field by the name people actually see rather than by a mapping somebody maintains. From there it is ordinary canvas work: a condition on one answer decides whether a human is involved, a Mattering database row records it, a task opens for whoever owns follow-up, and another connector writes it into a CRM or a spreadsheet. The submissions read is the node to build on rather than fetching each row individually, both because it returns everything in one call and because Fillout's rate limit is tight.

Read the form before you read the answers

Fillout: Get Form Metadata describes one form: its questions with their ids, titles and types, plus any calculations, URL parameters, Fillout Scheduling fields, Fillout Payments fields and quiz configuration. It is the lookup table for both reading and writing, because an imported answer is addressed by question id. The type field is what tells a workflow what an answer will look like, and one piece of Fillout guidance belongs in every workflow that branches on it: Fillout adds new question types regularly and advises applications to discard fields with unknown types, so branch with a default case rather than an exhaustive list that will age.

Backfill and migrate submissions into a form

Fillout: Create Submissions imports up to ten submissions per call, addressed by question id, and returns their new ids, which is what makes the operation reversible: deleting those ids restores the prior state exactly. This is the node for a migration off another form tool or a backfill of historical records. One property of it must be stated plainly rather than discovered, because it is the difference between a working automation and a silent one: Fillout states that submissions created through the API do NOT trigger email notifications, workflows or integrations. An imported row is inert. If you want a form's own downstream automation to fire, importing is not the way to do it, and the workflow should do that work itself with the other nodes on the canvas.

Give an assistant read access to real form data

Fillout: List Forms, Fillout: Get Form Metadata, Fillout: List Submissions and Fillout: Get Submission are the whole read surface, and they are a comfortable set to hand an agent. Because each answer carries its question text, an assistant can summarise last week's responses, count how many people chose an option, or pull out the free-text feedback without anyone first explaining the form's structure to it. Keep the two destructive nodes out of an agent's reach or behind an approval step, since Fillout has no scopes and therefore no read-only key to hand out instead.

Subscribe your own endpoint to a form

Fillout: Create Webhook points Fillout at a URL you already run, and Fillout then posts each new submission to it in the same shape as a row from the submissions list, so the list node's output doubles as the payload reference. Fillout: Delete Webhook removes the subscription. Two boundaries matter here. These nodes configure Fillout to call your endpoint; Mattering does not receive Fillout deliveries, so this is subscription management rather than a trigger here. And Fillout documents no signing secret and no signature header for these subscriptions, so a receiver cannot verify authenticity beyond keeping the URL unguessable. Note also that Fillout's in-app Webhook integration, configured per form in the editor, is a different mechanism that this API can neither see nor manage.

Example: A submissions sync that reads the newest rows rather than the oldest ones

Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.

1

Trigger: a schedule fires every fifteen minutes.

2

Fillout: List Submissions runs against the form with the after date set to the last successful run, the sort set to descending, and the limit raised toward the vendor cap of 150. Setting the sort explicitly is the important part: Fillout defaults to ascending, so a workflow that asks for the latest submissions without saying so reads the OLDEST ones and looks like it worked.

3

A condition ends the run when nothing new came in, which keeps the request count comfortably inside Fillout's 5 requests per second limit.

4

For each row, the questions array carries the question text with every answer, so the mapping into the next steps is written once against names people recognise. A default branch handles any question type the workflow does not know, per Fillout's advice about new types.

5

A Mattering database row is written keyed on the submission id, and a task opens for whoever owns follow-up. Payment amounts are converted from cents before anything displays them, and a calculation's value is cast before arithmetic, because Fillout returns it as text even when the calculation is a number.

6

A condition routes anything containing a scheduling booking down a different branch, since those rows carry the event time and a reschedule link that a reminder workflow can use directly.

7

Nothing in this run deletes anything. Fillout: Delete Submission stays out of the scheduled flow and behind an approval task, because Fillout documents no restore endpoint for a submission removed through the API.

Fillout MCP questions, answered

What Fillout operations are supported?

All eight that Fillout publishes, as 8 nodes: 4 reads and 4 actions. List forms; get one form's questions and field metadata; list a form's submissions with filters, a date range, a text search and paging; get one submission; import up to ten submissions; delete one submission; create a webhook subscription; delete a webhook subscription. There is no unbuilt remainder. What the API does not offer, and therefore what this connector cannot do, is worth stating in the same breath: no form creation, editing or deletion, no question or field editing, no submission updates, no analytics or reporting endpoints, no workspaces or folders or team management, and no way to list, read, update or replay a webhook once it exists.

Does this work with Claude, ChatGPT, or other AI assistants?

Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively. The same nodes are also steps on the automation canvas, which is what a form workflow usually needs more: submissions arrive at their own pace, and the flow that handles them should run on a schedule rather than waiting for somebody to open a chat window.

Does Fillout have its own MCP server?

No. Fillout's published documentation index contains no MCP page and no MCP reference anywhere, so there is no vendor server to compare this connector against and nothing to choose between. That makes this the straightforward answer for connecting an AI assistant to Fillout: connect the key once in a Mattering workspace and the eight operations are available over MCP to Claude, ChatGPT or Matter, and as canvas steps at the same time. If Fillout ships one later, the distinction to look for is the same one that applies to every vendor server: whether it runs unattended on a schedule, whether it chains with your other tools in one workflow, and whether the credential lives in a shared workspace store or in each person's local client config.

Can I create or edit a form through this connector?

No, and no connector could: Fillout's API has no endpoint for it. Forms are built in Fillout's editor, and the API's view of form structure is strictly read-only through Fillout: Get Form Metadata. That is a real boundary rather than a roadmap item, so a workflow that needs a form to exist should treat form creation as a human step. Everything downstream of the form is fully covered: reading its structure, reading its submissions, importing submissions, deleting one, and subscribing a webhook.

Why did my latest-submissions workflow return old records?

Because Fillout's sort parameter defaults to ASCENDING, which means oldest first. This is the single easiest mistake to make with this API, and it fails quietly: the workflow returns rows, processes them and reports success, and the rows are simply the wrong ones. Set the sort explicitly to descending on Fillout: List Submissions whenever you mean the newest. Two neighbouring defaults are worth setting deliberately at the same time: unfinished submissions are hidden unless you ask for the in-progress status, and submissions filled while previewing the form in the editor are excluded unless you ask for them, which is right for reporting and surprising while testing.

If I import submissions, will the form's notifications and integrations fire?

No. Fillout states that submissions created through the API do not trigger email notifications, workflows or integrations. That makes Fillout: Create Submissions a backfill and migration tool rather than a way to fire a form's downstream automation, and a workflow that imports a row expecting the form's own integrations to run will silently do nothing at all. If a notification or a downstream write is wanted, build it into the same Mattering workflow with the nodes beside the import. The import is capped at ten submissions per call by the API's own schema, so a larger batch has to be chunked, and each chunk costs a request against the rate limit.

Can an AI agent delete a submission I cannot get back?

It can, which is why Fillout: Delete Submission is flagged destructive. Fillout documents no restore endpoint and no recovery window for a submission deleted through the API, so nothing in a workflow can undo it. Fillout also documents no scopes, so there is no read-only key to hand an automation instead: the same key that lists submissions can delete them. The guardrails have to be structural. Keep agents on the four read nodes, put the delete behind a condition or an approval task, and note that the submission id field on the delete node is deliberately free text rather than a browsable picker, so an id has to be chosen by an upstream step rather than picked off a list of real respondent data. Fillout: Delete Webhook is the other flagged node, and it is worse than it sounds because Fillout ships no webhook lister and no delivery log: once a subscription is removed there is no way to enumerate what was there, and every submission between the removal and a re-subscribe is never delivered and cannot be re-sent.

Can Fillout submissions trigger a Mattering automation directly?

Not through this connector, and it is better to say so than to imply otherwise. Fillout: Create Webhook and Fillout: Delete Webhook subscribe and unsubscribe a URL you already run; Mattering does not receive Fillout deliveries today, so these are subscription management rather than an inbound trigger. What works instead is a schedule with Fillout: List Submissions using a date window, which is well suited to it since submission time is a real column on every row. Two more facts about these subscriptions are worth carrying: Fillout documents no signing secret and no signature header, so a receiver can only rely on the URL staying unguessable, and Fillout's in-app Webhook integration configured per form in the editor is a different mechanism this API cannot see or manage.

What limits should I design a Fillout workflow around?

Three, and the first one is tighter than most. Fillout documents a limit of 5 requests per second per account and API key, applying to every endpoint, so a loop that fetches submissions one at a time will trip it on a form of any size: prefer one Fillout: List Submissions call with a raised page size over a fan-out of Fillout: Get Submission calls. The page size is capped at 150 and defaults to 50, with offset-based paging and a total count and page count in the response telling you when to stop. And the import is capped at ten submissions per call by the request schema, so a migration chunks its batches. This connector does not retry internally: a rate-limit response comes back as an ordinary non-success result, so backoff belongs in the workflow.

8 nodes waiting on the canvas

Put Fillout to work inside your workspace

Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.

All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Fillout is a product of its respective owner; Mattering is an independent platform.

Start Free Explore our Products