Input config

Build action, trigger, and connection forms with toolkit field factories.

Input config is the declarative form schema for actions, triggers, and connections. Users fill these fields in the workflow builder and agent tool UIs. Field id values become keys on configValue in your run handlers.

Build fields with factories from @lunnoa/toolkit, then pass the array as inputConfig.

Common field factories

Example

import {  createTextInputField,  createSelectInputField,  createNumberInputField,} from '@lunnoa/toolkit';export const inputConfig = [  createTextInputField({    id: 'subject',    label: 'Subject',    description: 'Email subject line',    placeholder: 'Invoice ready',    required: {      missingMessage: 'Subject is required',      missingStatus: 'warning',    },  }),  createSelectInputField({    id: 'priority',    label: 'Priority',    selectOptions: [      { label: 'Low', value: 'low' },      { label: 'High', value: 'high' },    ],  }),  createNumberInputField({    id: 'retries',    label: 'Retries',    defaultValue: 3,  }),];

Shared field options

Most factories accept a common base shape:

• id (required): key on configValue
• label / description / placeholder
• required: { missingMessage, missingStatus } when the field must be set
• defaultValue when a sensible default exists
• Visibility and conditional helpers where the field type supports them

Keep id values stable. Renaming an id breaks existing workflow configurations that already store that key.

Pair with aiSchema

For actions, every configurable inputConfig id should appear on aiSchema. See Actions.

Next

• Actions: attach inputConfig to createAction
• Triggers: configure how workflows start
• Connections: connection-specific fields