eavz

Using Input Partials

Create and manage saved parameter presets for actions and triggers.

Input partials let you save parameter configurations as reusable presets. They pre-fill values, enforce immutable fields, and simplify action execution for your team and AI agents.

Creating a Partial

From the Dashboard

1

Open the Playground

Navigate to the Playground from the sidebar and select a workspace.

2

Configure an action

Select an integration and action, then fill in the input fields you want to save as a preset.

3

Save as partial

Click the Save button in the input panel. Enter a name for the partial and optionally mark fields as enforced.

From the API

bash
curl -X POST https://api.weavz.io/api/v1/partials \
  -H "Authorization: Bearer wvz_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "workspaceId": "proj_abc123",
    "integrationName": "slack",
    "actionName": "send_channel_message",
    "name": "Alerts Channel",
    "description": "Always post to #alerts with bot username",
    "values": {
      "channel": "C0ALERTS",
      "username": "alert-bot"
    },
    "enforcedKeys": ["channel"]
  }'

Loading a Partial in the Playground

1

Open the Playground

Navigate to the Playground and select your workspace.

2

Select the action

Pick the integration and action that has saved partials.

3

Load partial

Click the Load button in the input panel. Select a partial from the dropdown to populate the input fields.

4

Execute

Modify any non-enforced fields as needed, then click Execute.

Enforced vs Non-Enforced Values

Partial values come in two flavors:

TypeBehaviorUse Case
Non-enforcedPre-fills the field. Callers can override.Default model, default channel
EnforcedLocked. Callers cannot override, even at runtime.Security constraints, channel locks

Enforced keys are listed in the enforcedKeys array. Any key in this array has its value locked at execution time, regardless of what the caller passes.

Default Partials

Mark a partial as default and it auto-applies whenever no explicit partialIds are provided:

bash
# Set as default
curl -X POST https://api.weavz.io/api/v1/partials/{partialId}/set-default \
  -H "Authorization: Bearer wvz_your_key" \
  -H "Content-Type: application/json" \
  -d '{"isDefault": true}'

Default resolution stacks up to 2 levels: action-specific default + integration-wide default.

Using Partials with MCP Servers

Assign partials to MCP server tools to control what AI agents can do:

bash
curl -X POST https://api.weavz.io/api/v1/mcp/servers/{serverId}/tools \
  -H "Authorization: Bearer wvz_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "integrationName": "slack",
    "actionName": "send_channel_message",
    "connectionId": "conn_abc",
    "partialIds": ["partial_id"]
  }'

Enforced keys are automatically removed from the MCP tool schema, so AI agents cannot see or override them.

Managing Partials

Updating Values

bash
curl -X PATCH https://api.weavz.io/api/v1/partials/{partialId} \
  -H "Authorization: Bearer wvz_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "values": { "channel": "C0ALERTS", "username": "weavz-bot" },
    "enforcedKeys": ["channel", "username"]
  }'

Deleting a Partial

Deleting a partial automatically removes it from any MCP server tools that reference it.

bash
curl -X DELETE https://api.weavz.io/api/v1/partials/{partialId} \
  -H "Authorization: Bearer wvz_your_key"