AI by Zapier Workflow Steps

Use this companion with workflows-create or workflows-modify; it sets up the bounded AI step but does not replace the workflow lifecycle. If the request involves creating, testing, publishing, or enabling a complete workflow and neither lifecycle skill is loaded, load the appropriate one first.

SDK CLI discovery

Use the public SDK CLI's live catalog before writing the AI step:

• Find the current implementation: zapier-sdk list-apps --search "AI by Zapier" --json.
• Inspect actions: zapier-sdk list-actions <appKey> --json.
• Inspect editable fields: zapier-sdk list-action-input-fields <appKey> <actionType> <actionKey> --json.
• Prefer the complete contract: zapier-sdk get-action-input-fields-schema <appKey> <actionType> <actionKey> --json; retain the whole data schema, including nested contentSchema and root references. If that discovery is unavailable, use the version-scoped basic fallback below, not an invented nested contract.
• Resolve dependent choices: zapier-sdk list-action-input-field-choices with the settled parent inputs.
• Resolve an embedded app's connection: zapier-sdk list-connections <appKey> --owner me --json. Match the intended account by its returned name/label, paginate as needed, and ask when ambiguous. If none is usable, use the installed SDK's supported connect/reconnect flow and rediscover after the user finishes; never ask for raw credentials.

Keep three namespaces separate: