Getform

@Getform pull all submissions from our contact form (form ID abc123) from the last 7 days and show me the most common inquiry topics

Retrieved 47 submissions from form abc123. Most common inquiry topics based on message content: Product pricing questions (18 submissions), Technical support requests (14 submissions), Partnership inquiries (9 submissions), General feedback (6 submissions). The API returned paginated results; this summary reflects the first 50 records. Several submissions include file attachments (resumes, screenshots) that can be accessed via signed URLs if needed.

This example shows the MCP's ability to fetch and analyze form submissions at scale. Requires a valid API key with read access to the specified form. The MCP retrieves raw submission data; the AI performs the categorization and summarization. Be aware that large forms may require multiple paginated requests, and file URLs expire after a vendor-defined period.

@Getform submit a test entry to form xyz789 with name 'QA Bot', email 'qa@example.com', and message 'Automated health check at 2PM UTC'

Successfully submitted test entry to form xyz789. Getform confirmed receipt with submission ID sub_9k2m4n. The form endpoint processed the three fields (name, email, message) without errors. No reCAPTCHA or honeypot validation was required for this form. The submission will appear in your Getform dashboard immediately and trigger any configured webhooks or email notifications.

This example demonstrates programmatic form submission, useful for testing workflows or automating data entry. The MCP posts directly to Getform's API, bypassing the browser-based form. If your form has reCAPTCHA enabled, you'll need to provide a valid token. Submitting via API counts against your Getform plan's monthly submission quota.

@Getform fetch submission sub_7h8j2k from form abc123 and draft a personalized thank-you email based on what they asked about

Retrieved submission sub_7h8j2k: Contact name is Sarah Chen, email sarah.chen@startup.io, submitted 2 hours ago asking about enterprise pricing and SSO integration timelines. Based on her inquiry, here's a draft reply: 'Hi Sarah, thanks for reaching out about our enterprise plan. Our SSO integration (SAML 2.0) is available on the Business tier and above, with typical setup completed in 1-2 weeks. I'd love to schedule a 20-minute call to walk through pricing options tailored to your team size. Does Thursday at 2PM work?' This response addresses her specific questions while moving toward a sales conversation.

This example pairs the MCP's single-submission retrieval with AI-driven personalization. Useful when you need to respond thoughtfully to high-value leads without manually copying data from the Getform dashboard. Requires both form_id and submission_id, which you'd typically get from a webhook payload or the bulk submissions list. The AI's draft quality depends on the richness of the original submission data.

When Getform makes sense for customer intake workflows

A 5-person support team uses Getform to collect bug reports and feature requests from their public site. The Get Form Submissions tool lets them pull the last 24 hours of entries directly into Switchy during morning standup, filter by keyword, and route urgent issues to Linear without opening the Getform dashboard. This works when your form volume is under 200 submissions per day and you're not doing complex conditional logic or multi-step flows. If you need branching or calculated fields, you'll hit Getform's limits fast and should look at Typeform or Fillout instead. For straightforward intake where the team just needs quick read access to recent submissions, the 3-tool scope is enough.

Using Getform for one-off event sign-ups

A 3-person marketing team runs quarterly webinars and uses Getform to collect registrations. The Submit Form tool lets them programmatically add attendees from a CSV or another system, and Get Form Submissions pulls the full list for badge printing or email follow-up. This setup shines when you're running 2-4 events per year and don't want to pay for a dedicated event platform. The API key auth means anyone on the team can configure the MCP in under 5 minutes. The trade-off: Getform doesn't handle payment or calendar invites, so you'll still need Stripe or Calendly in the loop. If your event cadence is monthly or higher, the manual stitching gets tedious and you should consolidate into Eventbrite or Luma.

When Getform fits early-stage lead collection

A 2-person sales team at a pre-seed startup embeds a Getform contact form on their landing page and uses the MCP to pull new leads into Switchy each morning. The Get Form Submissions tool surfaces name, email, and message in one call, and the team copies high-intent leads into their CRM manually. This works when you're under 50 leads per week and haven't built out automation yet. Once you cross 100 leads per week or need lead scoring, Getform's flat structure becomes a bottleneck—there's no native enrichment or routing logic. At that point, migrate to HubSpot or Pipedrive and use their MCP instead. For now, Getform keeps setup time under an hour and costs stay near zero.