Overview

It would be helpful if Agent Studio could automatically import or sync input arguments from an HTTP Action into the related Compound Action and Conversation Process.

Today, inputs defined in an HTTP Action often need to be manually recreated or mapped again in the Compound Action, and then mapped again in the Conversation Process. While manageable for smaller actions, this becomes increasingly time-consuming and error-prone as actions grow in complexity.

Example

A ServiceNow Change Request action might require fields such as:

• short_description
• description
• start_date
• end_date
• risk_impact_analysis

These inputs are already defined within the HTTP Action, yet they must still be manually carried through multiple layers before the action can be used conversationally.

This results in the same schema effectively being maintained three times:

HTTP Action

↓

Compound Action

↓

Conversation Process

Suggested Improvement

Introduce an option such as:

• Import input arguments from HTTP Action
• Auto-map inputs
• Sync action schema

When enabled, Agent Studio would automatically propagate input definitions through the action chain while preserving:

• Field names
• Data types
• Descriptions
• Required/optional settings
• Default values
• Validation rules

Builders could still override mappings manually if needed.

Benefits

Reduce repetitive configuration

Builders should not need to recreate the same inputs multiple times across different layers of the platform.

Reduce mapping errors

The more times a field is manually mapped, the greater the chance of:

• Missing fields
• Incorrect parameter mappings
• Out-of-sync schemas
• Placeholder values being accidentally passed through

Faster development and testing

Less time spent maintaining mappings means more time spent:

• Building business logic
• Refining user experiences
• Testing new ideas
• Delivering value to end users

Easier maintenance

When an HTTP Action schema changes, updates could automatically flow through the action chain instead of requiring manual updates in multiple places.

Why This Matters

This may be partially addressed by future capabilities such as Tool Architect, but there is still significant manual configuration required today when building actions.

The biggest impact is not the time spent clicking through mapping screens. It's the interruption to the development flow.

When experimenting with ideas, repeatedly recreating or remapping inputs across HTTP Actions, Compound Actions and Conversation Processes creates friction and slows iteration.

For builders who enjoy exploring new use cases, prototyping solutions, or developing outside normal work hours, this repetitive setup work often becomes the limiting factor. Time that could be spent improving the experience, testing new patterns, or creating innovative solutions is instead spent maintaining mappings.

Reducing this overhead would make Agent Studio more enjoyable to build in, encourage experimentation, and allow builders to focus on solving business problems rather than managing plumbing.

Guiding Principle

Map once, consume everywhere.

Define an input once and have it available throughout the action chain, rather than maintaining the same schema across multiple layers.