Overview

Provide managed OAuth access to the Tally API via the Maton gateway so you can programmatically manage Tally forms, submissions, workspaces, organizations, and webhooks.

Key Advantages

1.Managed OAuth via Maton: you don’t handle Tally OAuth tokens directly; the gateway injects them for you.

2.Covers major Tally entities: forms, questions, submissions, workspaces, org users/invites, and webhooks.

3.Simple HTTP interface with a single base URL pattern (https://gateway.maton.ai/tally/{native-api-path}).

4.Clear authentication model using a Maton API key and optional connection selection header for multi-account setups.

5.Good reference-style documentation with concrete Python and JavaScript examples, including pagination and webhook usage patterns.

Use Cases

Creating, updating, publishing, and deleting Tally forms programmatically (e.g., auto-generating forms for new campaigns).
Fetching and filtering form submissions to power analytics, reporting, or syncing responses into CRMs or data warehouses.
Managing workspaces and organization users/invites for Tally account administration flows.
Setting up and managing webhooks to receive real-time submission notifications instead of polling.
Building internal tools or bots that let users list forms, inspect questions, and work with submission data from Tally.

Evaluation History (1)

8.3/103/19/2026win32-x64

▼

OS: win32-x64LLM: z-ai/glm-5-turbo

**Quick judgment** Well-designed, high-functionality integration for Tally via Maton. It provides broad coverage of the Tally API (forms, submissions, workspaces, webhooks) with managed OAuth and clear HTTP semantics, making it a solid choice whenever you need to work with a user’s Tally account programmatically. **Key risks / limitations** - Depends on external Maton and Tally services; outages or API changes (the API is explicitly in public beta) can break flows. - Requires a valid Maton API key and an established Tally connection; misconfiguration or missing env vars will cause 4xx errors. - Rate limit of 100 requests/min means it’s not ideal for very high-throughput bulk operations. - Operations can delete forms, submissions, and workspaces; callers must be careful with destructive endpoints. **Recommended scenarios** - Users explicitly ask to create, modify, or delete Tally forms, or to retrieve questions/submissions from existing Tally forms. - Automation of Tally administration: listing workspaces, managing organization users/invites, or cleaning up forms/workspaces. - Setting up or maintaining webhooks for real-time form response handling instead of polling. - Any Tally-specific workflow where the user already uses Tally; for other third-party apps, prefer the separate `api-gateway` skill.

Tally

Overview

Key Advantages

Use Cases

Evaluation Scores

Download Trend

Evaluation History (1)

Comments (0)

Post a Comment