Collaboration

Cognito Forms

Read Cognito Forms submissions in Dex so you can drive onboarding, offboarding, and change requests from the form data your customers already send.

Dex connects to Cognito Forms through its REST API so admins can read form definitions and entries in plain language - pull up a form's schema and fields, list submitted entries, open a single entry, and fetch a generated document. Read-only for this first ship: Dex captures onboarding, offboarding, and change submissions and drives CoAdmin work from them, but does not write, import, or delete. Available as an MSP global app: one Organization API key is shared across the Cognito Forms organization, and each Dex tenant is confined to a single form via its form_id.

Start free →See Dex Live

What Dex does with Cognito Forms

Dex handles both admin workflows and employee self-service — all policy-guardrailed and audit-logged.

For admins (Dex Pro)

Read a form's schema and field list so you know what each submission captures
List entries submitted to this tenant's form
Open a single entry to review the submitted onboarding, offboarding, or change details
Fetch a generated document attached to an entry
List every form on the Cognito Forms organization from the MSP master connection to map each tenant to its form
Deploy as an MSP global app - one Organization API key, each tenant confined to its own form via form_id

Just ask Dex

Your team types a request in plain language. Dex investigates, plans, and executes — with the right guardrails.

Admin prompts

>Show me the schema for this tenant's onboarding form
>List the entries submitted to our new-user request form this week
>Open entry 214 and summarize the onboarding details
>Fetch the generated document for entry 214
>Which fields does this form capture?

Policy actions

Every action Dex can take on Cognito Forms is declared, scoped, and guardrailed. Admins control which apply, who approves them, and whether they're limited to self-service.

Action	What it does	Guardrails
`cognito_forms_list_forms`	List every Cognito Form (MSP master connection only; ships disabled on scoped children)	—
`cognito_forms_get_form`	Read one Cognito Form by id or name (path-forced on a scoped child; prefer schema)	—
`cognito_forms_get_form_fields`	Read the field list for this form (path-forced; prefer schema on some keys)	—
`cognito_forms_get_form_schema`	Read the schema for this form (path-forced)	—
`cognito_forms_list_entries`	List entries submitted to this form (path-forced)	—
`cognito_forms_get_entry`	Read a single entry under this form (path-forced)	—
`cognito_forms_get_document`	Fetch a generated document for an entry under this form (path-forced)	—

How to configure Cognito Forms

Onboarding takes minutes. Dex validates your credentials before saving them.

Setup steps

1
In Cognito Forms, go to Organization Settings > API and create an Organization API key for Dex. Prefer Form Scope Read and Entry Scope Read.
2
Copy the API key - it is shown once, so regenerate if lost.
3
In Dex, enable the Cognito Forms integration and paste the Organization API key. Leave form_id blank on the MSP master connection.
4
On the MSP master, run discovery and use GET /api/forms to find each tenant's form by name, then take its form Id or internal form name.
5
Save that form_id on the tenant's own connection. Dex validates with a live schema read and reports the form id the platform forced so any mismatch is visible.

Credentials required

api_key: Cognito Forms Organization API key (secret; sent as a Bearer header, never surfaced)
form_id: This tenant's form Id or internal form name (e.g. NewUserComputerRequestIntegraDelamarNevada) - leave blank on the MSP master connection

Requirements

•A Cognito Forms Pro, Team, or Enterprise plan with an Organization API key
•Read-only for this first ship - no write, import, or delete actions are policy-modelled
•Each Dex tenant maps to exactly one Cognito form via form_id; a scoped child has its form path segment forced and cannot read another tenant's form
•The account-wide form roster (GET /api/forms) is master-connection-only and refused on a scoped child