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 and trigger setup for your team and AI agents. Partials are scoped to a configured workspace integration alias, so two aliases for the same integration can have separate defaults.

Creating a Partial

From the Dashboard

1

Open the Playground

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

2

Choose an operation

Select a configured integration alias, then choose the action or trigger you want to test.

3

Save as partial

Fill the input fields you want to save, then use Save as Partial. Enter a name and optionally lock saved fields.

You can also create partials from the Partials page. That flow supports integration-wide shared fields, one-action presets, and one-trigger presets.

1

Open Partials

Navigate to Partials and select a workspace.

2

Pick a configured integration

Choose the workspace integration alias the partial should belong to.

3

Choose scope and fields

Select shared integration fields, one action, or one trigger. The field picker searches display names and API keys.

From the API

Use field keys from the current action or trigger schema. For dynamic or unfamiliar integrations, resolve metadata first with Integrations, then save only keys that appear in that schema.

bash
curl -X POST https://api.weavz.io/api/v1/partials \
  -H "Authorization: Bearer wvz_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "workspaceId": "550e8400-e29b-41d4-a716-446655440000",
    "integrationName": "slack",
    "integrationAlias": "slack_bot",
    "actionName": "send_channel_message",
    "name": "Alerts Channel",
    "description": "Always post to #alerts without link unfurling",
    "values": {
      "channel": "C0ALERTS",
      "unfurl_links": false
    },
    "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. To run without defaults, send an explicit empty partialIds array.

Using Partials with MCP Servers

MCP servers sync workspace integrations, so matching default partials for a workspace integration alias apply automatically. This is the normal way to pre-fill or enforce tool inputs for agents.

For advanced server-specific manual tools, assign explicit partialIds when that one server needs a preset that should not be the workspace default:

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",
    "integrationAlias": "slack_bot",
    "connectionId": "conn_abc",
    "partialIds": ["partial_id"]
  }'

Enforced keys are automatically removed from the synced or manual 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", "unfurl_links": false },
    "enforcedKeys": ["channel", "unfurl_links"]
  }'

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"