Tally

@Tally show me all responses from the Q1 feedback form, including any partial submissions from the last 30 days

Retrieved 47 responses from form 'Q1 Team Feedback' (ID: fm_abc123). 42 are complete submissions, 5 are partial. Most recent response received 2 hours ago. Fields captured: satisfaction rating (1-5 scale), open feedback text, department dropdown, and optional email. The partial responses stopped at the feedback text field. Response data includes submission timestamps, respondent metadata where available, and all field values in structured format.

This example shows read-access to form responses with filtering. Requires API key with read scope for the target form. Tally returns paginated results; for forms with hundreds of responses, you may need to specify pagination parameters or accept a subset. Partial submissions are included by default unless filtered out.

@Tally create a new event registration form with fields for name, email, dietary restrictions, and a yes/no RSVP confirmation

Created form 'Event Registration' (ID: fm_xyz789) with 4 blocks: short text input for name, email input with validation, multiple choice for dietary restrictions (vegetarian/vegan/gluten-free/none), and yes/no toggle for RSVP confirmation. Form is live at tally.so/r/xyz789. Default settings applied: responses stored in Tally, no submission limit, thank-you message enabled. You can now retrieve the form ID to configure webhooks or adjust settings like requiring login or setting a close date.

Demonstrates form creation with mixed field types. The MCP constructs block definitions from your natural language description, but complex conditional logic or custom validation rules may require follow-up refinement. Form is immediately published unless you specify draft mode. You'll need the form ID for subsequent operations like adding webhooks or modifying settings.

@Tally set up a webhook for the customer feedback form to ping our Slack channel whenever someone submits a response rated below 3 stars

Created webhook (ID: wh_def456) for form 'Customer Feedback' (fm_abc123). Configured to POST to https://hooks.slack.com/services/YOUR/WEBHOOK/URL on every new response submission. Note: Tally webhooks fire on all submissions; filtering by rating value (below 3 stars) must be handled in your Slack webhook handler or via an intermediary service like Zapier. Webhook payload includes full response data, form metadata, and submission timestamp. Test the endpoint to confirm receipt.

Shows webhook creation for real-time notifications. Important limitation: Tally webhooks cannot filter by field values at creation time—conditional logic must be implemented in your receiving endpoint. Requires a publicly accessible HTTPS URL. Webhook failures are not automatically retried, so monitor your endpoint's uptime. You can delete the webhook by ID if routing changes.

When Tally MCP beats manual form management for support teams

A 6-person support team runs weekly NPS surveys and quarterly feature requests through Tally. They used to copy-paste responses into Slack and Notion manually. With the Tally MCP, they set up a webhook that pipes new responses directly into a shared AI workspace where the team triages sentiment and tags feature requests in real time during their Monday sync. The MCP's Get Form Responses tool handles pagination automatically, so even a 400-response survey loads without manual clicking. This works because their forms are stable (same structure each cycle) and they need read access more than write. If you're constantly rebuilding forms or need advanced conditional logic, you'll still do that in Tally's UI. But for teams who treat forms as data pipes into a shared workspace, this MCP cuts 2-3 hours of copy-paste per week.

How a 3-person ops team uses Tally MCP for one-off event forms

A startup ops team runs 8-10 community events per quarter. Each event needs a custom registration form with different fields (dietary restrictions for dinners, GitHub handles for hackathons). They use the Tally MCP's Create Form tool to spin up new forms from a template prompt in their AI workspace, then immediately create a webhook to route registrations into their event-planning thread. The MCP shines here because the team isn't form-design experts—they describe what they need in plain language, the AI generates the block definitions, and the form goes live in under 5 minutes. The trade-off: if your events have complex multi-step flows or payment gates, you'll hit Tally's block limitations and need to hand-code those in the UI. For straightforward registration forms that feed into a shared workspace, this MCP turns form creation into a 2-message conversation instead of a 20-minute UI session.

When Tally MCP replaces spreadsheet exports for sales handoff

A 4-person sales team uses Tally for inbound demo requests. Marketing built the form once; sales needs to pull responses twice daily to assign leads. Before the MCP, someone exported a CSV, uploaded it to Sheets, then pinged the team. Now they use Get Form Responses in their AI workspace to fetch new leads since the last check, and the AI auto-assigns based on territory and deal size. The MCP's field-retrieval tools let the AI parse custom fields (company size, use case) without hardcoding column names. This works because their form structure is fixed and they need fast read access, not form edits. If your lead volume exceeds 500/day, the pagination gets slow and you're better off with Tally's native Zapier integration. But for teams under 100 leads/week who want leads in their workspace without leaving the conversation, this MCP turns lead handoff into a background task.