Mapping Locations
REST operations support four parameter locations:| Location | Usage | Example |
|---|---|---|
| Path | URL path variables | /users/{id} |
| Query | URL query string | ?limit=10&offset=0 |
| Body | Request body | {"name": "Alice"} |
| Header | HTTP headers | Authorization: Bearer ... |
Path Parameters
Parameters embedded in URL path.{"user_id": "123", "post_id": "456"}:
Query Parameters
Parameters in URL query string.{"search_term": "python", "page_limit": 10}:
Body Parameters
Request body mapping controls how input becomes JSON/form data.Strategy: Full Input
Use entire input as body:{"name": "Alice", "email": "alice@example.com"}
Request body:
Strategy: From Field
Extract specific field:{"data": {"name": "Alice"}}
Request body: {"name": "Alice"}
Strategy: Mapped
Map individual fields:{"name": "Alice", "email": "alice@example.com"}
Request body:
Header Parameters
Add custom headers to requests:Nested Field Mapping
Map nested input fields using dot notation or arrays:"123"
Or using dot notation:
Parameter Validation
Add validation to parameters:- pattern - Regex for strings
- minimum - Min value for numbers
- maximum - Max value for numbers
- enum_values - Allowed values list
Complex Example: GitHub Create Issue
Operation:POST /repos/{owner}/{repo}/issues
Full mapping:
Type Conversion
Parameters are automatically converted:"limit": "10" (string), auto-converted to integer 10.
Supported types:
- string
- integer
- number (float)
- boolean
- array
- object
Default Values
Set defaults for optional parameters:limit, defaults to 10.
Testing Mappings
After configuring mappings:- Connectors > Select connector
- Click Test
- Select operation
- Provide sample input
- View generated request
- Verify mapping correct
- Values in correct locations
- Data types correct
- Nested fields extracted correctly
- Validation applied
Common Mapping Patterns
Simple Path + Query
Body with Headers
Nested Path
Debugging Mapping Issues
Values in wrong location
- Check
from_fieldmapping - Verify parameter
namematches API docs - Review request in Test tab
Missing values
- Ensure
required: trueonly on required fields - Check agent provides necessary input
- Verify field names in agent input
Type errors
- Specify correct
param_type - Ensure input data type matches
- Check API documentation