Basin MCP integration for AI agents.
Connect AI agents to Basin through 18 structured actions, including get form, create form, and delete form. Review authentication, inputs, workflows, and saf…
- ACTION CONTRACTS
- 18
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Basin integration exposes
The Basin Agent App exposes 18 provider-backed actions for productivity and marketing work. Its current contract lets an authorized agent fetch a single basin form by id, create a new basin form, and delete a basin form by id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Basin account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Basin capabilities.
Showing 12 of 18 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_formREADFetch a single Basin form by ID.
INPUTS: form_id
create_formWRITECreate a new Basin form.
INPUTS: name / timezone / project_id / redirect_url / use_ajax
delete_formHIGH IMPACTDelete a Basin form by ID.
INPUTS: form_id
create_form_webhookWRITECreate a new Basin form webhook.
INPUTS: form_id / name / url / format / enabled
create_projectWRITECreate a new Basin project.
INPUTS: name
delete_form_webhookHIGH IMPACTDelete a Basin form webhook by ID.
INPUTS: webhook_id
delete_projectHIGH IMPACTDelete a Basin project by ID.
INPUTS: project_id
delete_submissionHIGH IMPACTDelete a Basin submission by ID.
INPUTS: submission_id
get_form_webhookREADFetch a single Basin form webhook by ID.
INPUTS: webhook_id
get_projectREADFetch a single Basin project by ID.
INPUTS: project_id
get_submissionREADFetch a single Basin submission by ID.
INPUTS: submission_id
list_form_webhooksREADList Basin form webhooks with optional filters.
INPUTS: page / query
INPUT CONTRACTS
Know what the action needs before it runs.
get_form
form_idOPTIONAL- Basin form ID.
create_form
nameREQUIRED- Form name.
timezoneREQUIRED- IANA timezone used for form timestamps.
project_idREQUIRED- Basin project ID.
redirect_urlOPTIONAL- URL to redirect users to after submission.
use_ajaxOPTIONAL- Whether the form should submit via AJAX.
delete_form
form_idOPTIONAL- Basin form ID.
create_form_webhook
form_idREQUIRED- Basin form ID to attach the webhook to.
nameREQUIRED- Friendly webhook name.
urlREQUIRED- Destination URL where Basin posts submission payloads.
formatOPTIONAL- Webhook payload format accepted by Basin.
enabledOPTIONAL- Whether the webhook is enabled.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Form
Fetch a single Basin form by ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_formControl Create Form
Create a new Basin form. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_formVerify with Create Form
Create a new Basin form. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
create_formSAFETY BOUNDARY
Operate Basin with explicit limits
- Authorize Basin with API key and grant only the provider access required by the selected actions.
- 10 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_form`, `delete_form_webhook`, and `delete_project` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Basin rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Basin task completed successfully.
CONNECTION MODEL
API key
Basin account API key sent with the Authorization Token header. Find or regenerate it from the Basin API section in your dashboard: https://docs.usebasin.com/account-management/api-access/
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 8
- WRITE SIGNALS
- 6
- HIGH IMPACT
- 4
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Basin.