Cognito Forms

**Judgement:** A strong, well-documented integration for Cognito Forms via the Maton gateway, suitable for most production workflows that need to create, read, update, delete, or document-export form entries—provided you are comfortable depending on Maton’s infrastructure and have proper API keys configured. **Key strengths** - Covers core Cognito Forms needs: list forms, entry CRUD, document generation, and file retrieval. - Managed OAuth simplifies authentication; only a MATON_API_KEY secret is needed. - Documentation is clear and practical, with Python/JS examples, field-format guidance, and troubleshooting notes. **Risks & limitations** - Hard dependency on Maton services (`gateway.maton.ai`, `ctrl.maton.ai`); outages or platform changes there will affect this skill. - Requires a Maton account and API key, plus properly configured Cognito OAuth connections, which adds setup overhead. - The underlying Cognito API does not support bulk listing of all entries; unsuitable for large-scale export/sync without webhooks or OData. - Destructive operations (DELETE entries) are available when scopes allow, so misconfiguration or careless use could remove data. **Recommended scenarios** - Agents or backend services that need to submit new Cognito form entries, update them, or fetch specific submissions by ID/number. - Workflows that generate PDFs from Cognito Forms entries and then route those documents elsewhere (email, storage, other APIs). - Systems that need to fetch user-uploaded files from Cognito forms for further processing. - Multi-tenant integrations where you manage multiple Cognito accounts via Maton’s connection management. Less ideal for: - High-volume analytics or archival exports of all form entries (use Cognito webhooks/OData instead). - Environments where an additional external dependency (Maton) is not acceptable from a compliance or reliability standpoint.