Basin
Basin is a no-code form backend that enables users to set up powerful, reliable forms quickly without writing server-side code.
Verdict
Common use cases
- Spin up landing page forms during campaign sprints
- Route contact form submissions to Slack channels
- Archive old feedback forms after product launches
- Pipe lead captures into CRM webhooks automatically
- Organize seasonal campaigns into separate Basin projects
Integration
- Vendor
- Basin
- Category
- other
- Auth
- API_KEY
- Tools
- 18
- Composio slug
basin
Tools
- Create Form
Tool to create a new form in basin. use when you need to automate form setup with name, timezone, and project association; optionally configure redirect, notifications, or spam protection.
- Create Form Webhook
Tool to create a new webhook for a specific form. use when you need to programmatically add a webhook once you have the form id and callback url confirmed.
- Create Notification
Tool to create a new notification webhook. use when you need to forward form submissions to an external service.
- Create Project
Tool to create a new basin project. use when you need a new organizational container for forms. example: "create a project named marketing leads."
- Delete Formdestructive
Tool to delete a form. use when permanently removing a form after it's no longer needed. ensure the form id is correct; this operation is irreversible.
- Delete Integrationdestructive
Tool to delete a form webhook integration. use when removing an obsolete integration by id.
- Delete Projectdestructive
Tool to delete a project. use when you need to remove a project after confirming its id. returns the deleted project's details.
- Delete Webhookdestructive
Tool to delete a specific webhook. use when you need to remove a webhook from a form after confirming its id.
- Get Domains
Tool to retrieve a list of all domains associated with the account. use after authentication when you need to display or verify your configured domains in basin.
- Get Form Details
Tool to retrieve detailed information about a specific form. use when you have a form id and need its metadata.
- Get Forms
Tool to retrieve a list of all forms. use after authentication to fetch all your forms.
- Get Project Details
Tool to retrieve detailed information about a specific project. use when you have a project id and need its metadata (name, created at, updated at).
- Get Projects
Tool to retrieve a list of all projects. use after authentication to fetch your project inventory.
- Get Submissions
Tool to retrieve all submissions for a specific form. use when you need to list entries after obtaining the form id.
- Get Webhooks
Tool to retrieve all webhooks associated with a specific form. use after obtaining the form id.
- Update Integration
Tool to update a form webhook integration. use to modify settings of an existing integration.
- Update Project
Tool to update details of an existing project. use when you need to change a project's name after confirming the project id. example: "update project 123 to 'rebrand launch'".
- Update Webhook
Tool to update settings of an existing webhook for a form. use after obtaining the webhook's id.
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings → Integrations → Add MCP Server. 2. Select Basin from the catalog and choose API Key authentication. 3. Log into your Basin dashboard at usebasin.com, go to Account Settings → API Keys, and generate a new key with full read/write permissions. 4. Paste the key into Switchy's API Key field and click Connect. 5. Switchy will verify the credential and list Basin's 18 tools in the integration panel. 6. Open any Space, type a message like '@Basin create a project named Q1 Leads', and send it. 7. Basin will return the new project ID; confirm you see it in your Basin dashboard to verify the connection is live. 8. To test a full workflow, ask Basin to create a form inside that project, then create a webhook pointing to a test URL like webhook.site.
What teammates see: by default, memories from Basin are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
New Campaign Form
@Basin create a project called Spring Sale 2024, then create a form inside it named Early Access Signup with notifications enabled and a redirect to /thank-youOpen in a Space →
Wire Up Webhook
@Basin create a webhook for form ID fm_abc123 that posts to https://hooks.slack.com/services/T00/B00/xyz when a new submission arrivesOpen in a Space →
List All Projects
@Basin list all projects in my account and include the form count for each oneOpen in a Space →
Clean Up Old Forms
@Basin delete the form with ID fm_old456 and confirm it's gone from the projectOpen in a Space →
Notification Setup
@Basin create a notification webhook that sends all form submissions to https://example.com/intake so our ops team sees every leadOpen in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Basin list all forms in the 'Marketing Leads' project and show me which ones have active webhooks configured
Based on the Basin account, the 'Marketing Leads' project contains 4 forms: 'Contact Us' (3 active webhooks), 'Newsletter Signup' (1 webhook), 'Demo Request' (no webhooks), and 'Partner Inquiry' (2 webhooks). The Contact Us form routes submissions to Slack, HubSpot, and a custom endpoint. Newsletter Signup sends to Mailchimp. Demo Request has no integrations yet. Partner Inquiry forwards to Salesforce and an internal API. This illustrative example shows how Basin organizes forms under projects with webhook routing.
This read-heavy example demonstrates Basin's project-form hierarchy and webhook visibility. Requires API key with read permissions. Actual form names and webhook counts depend on your Basin account state. Useful for auditing integration health before modifying configurations.
@Basin create a new form called 'Product Feedback' in the Marketing project with spam protection enabled and redirect to /thank-you after submission
Form 'Product Feedback' created successfully in the Marketing project. Form ID: frm_abc123xyz. Spam protection is enabled using Basin's built-in filtering. Post-submission redirect configured to /thank-you. The form is now live and ready to accept submissions. You can add webhook integrations or email notifications separately. This example illustrates Basin's form creation with common configuration options applied in a single operation.
This write example shows Basin's form provisioning with inline configuration. The operation is immediate and creates a production-ready endpoint. Timezone defaults to account settings if not specified. Consider adding webhook integrations afterward to route submissions to your CRM or notification system.
@Basin review all submissions to the 'Contact Us' form from the last 7 days and draft a summary of common inquiry themes for our team meeting
Analyzed 47 submissions to 'Contact Us' from the past week. Three dominant themes emerged: (1) Pricing questions for enterprise plans (18 submissions, mostly asking about volume discounts), (2) Integration requests for Zapier and Make (12 submissions, users want no-code automation), (3) GDPR compliance questions (9 submissions, primarily EU-based contacts asking about data residency). Remaining 8 submissions were general support inquiries. Recommendation: prioritize enterprise pricing documentation and publish a compliance FAQ. This synthesis example shows Basin data paired with AI analysis.
This synthesis example combines Basin's submission retrieval with AI reasoning to surface patterns. Basin stores form submissions with timestamps and field data, making trend analysis possible. Rate limits apply to bulk submission fetches. The AI cannot access actual submission content without proper API scopes—ensure your key has read access to submission data.
Use-case deep-dives
When Basin makes sense for small marketing teams
A 3-person marketing team running 8 landing pages needs to route form submissions to Slack, HubSpot, and a Google Sheet without touching code. Basin wins here because the MCP lets you script the entire form infrastructure—create forms, wire up webhooks, toggle spam filters—from a shared Switchy workspace instead of clicking through a dashboard 8 times. The team can template their form setup in a prompt, run it once per campaign, and never log into Basin's UI. The boundary: if you're only managing 1-2 static forms, the MCP is overkill; just use Basin's web interface. But once you're spinning up forms weekly or A/B testing notification configs, the MCP pays off in 10 minutes.
Basin MCP for multi-client form provisioning
A 6-person agency onboards 4 new clients per month, each needing 3-5 contact forms with custom notification routing. The Basin MCP is the right call because it turns form setup into a repeatable script: create project, create forms, attach webhooks, done. The team runs a single Switchy prompt per client instead of manually clicking through Basin 20 times. The MCP's 18 tools cover the full lifecycle—you can also delete old projects when a client churns, keeping the account clean. The trade-off: Basin's API key is account-wide, so you'll need a process to avoid accidental cross-client edits. If your agency is under 2 clients per quarter, the manual UI is faster.
When to automate Basin forms for product teams
A 5-person product team runs quarterly feedback campaigns, each with 2-3 embedded forms that route to different Notion databases depending on the feature area. The Basin MCP is borderline here. It wins if you're changing notification endpoints or spam settings every cycle—those edits are faster in Switchy than in Basin's dashboard. The MCP also helps if you're archiving old forms in bulk after each campaign. But if your forms are evergreen and you're just tweaking copy in your site's CMS, the MCP adds no value. The buying threshold: if you touch Basin's config more than twice per quarter, script it with the MCP.
Frequently asked
What does the Basin MCP do in Switchy?
It lets AI agents create and manage Basin forms, projects, webhooks, and notifications without switching to the Basin dashboard. Useful when you're building landing pages or automating lead capture workflows and want the AI to spin up forms, wire webhooks to Slack or your CRM, or tear down test forms when you're done.
Do I need admin access to connect Basin MCP?
You need a Basin API key, which typically requires account-owner or admin permissions to generate. Basin uses API_KEY auth, so whoever connects it in Switchy must have access to the Basin settings page where keys are issued. Standard team members usually can't create keys.
Can Basin MCP read or export existing form submissions?
No. The 18 tools focus on form setup, webhooks, and notifications—creating, updating, and deleting resources. If you need to pull submission data or analytics, you'll have to export from the Basin dashboard or use Basin's REST API directly outside Switchy.
Why use Basin MCP instead of just logging into Basin?
Speed and context. If you're already chatting with an AI about a new campaign, it can scaffold the form, attach a webhook to your Slack channel, and drop the embed code in one thread—no tab-switching. For one-off form edits, the Basin UI is faster.
Who on the team should connect Basin to Switchy?
Whoever owns your Basin account or has API-key privileges. Once connected, any Switchy workspace member can ask the AI to create forms or webhooks, so limit access if you don't want junior team members accidentally deleting production forms.