Formdesk
MARKETING · MARKETING
Forms, their input items, and form results in the account they connected.
Connect Formdesk with Fabriq Developer
Your user pastes their Formdesk credential on a page Agentic Fabriq hosts, so it never reaches your backend and never becomes one shared key across all of your users. Same call as OAuth, one more argument.
Provider names are surfaces, not vendors, and the authoritative list is the capabilities endpoint rather than any page including this one — an unknown name returns 400 with the valid list. Fabriq Developer is free to start and needs no provider paperwork. Start free or read the quickstart.
Connecting Formdesk in practice
Formdesk lists a "webservice API" and webhooks among its features but publishes no developer reference on the open web, so form and field identifiers, authentication and any throughput ceiling all have to come out of an account or out of support before an agent can be wired up.
Worth knowing
- There is no public endpoint list or authentication description to read in advance; the features page names the webservice API and then routes technical questions to info@formdesk.com.
- Webhooks are presented as the way to "directly submit entered data to one or more other systems", which suggests push-first integration and no documented polling contract to fall back on.
Checked against Formdesk features (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put Formdesk behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.