What inputs does the City Explorer workflow use?

The workflow uses Location, Dates, Group Size, Description. Required fields and their expected formats are listed on this page.

What resources are included in the City Explorer blueprint?

The blueprint contains 2 AI agents, 0 functions, 1 MCP server. Its workflow pattern is Sequential.

Can I customize the City Explorer blueprint in GraphN?

Yes. Open the blueprint in GraphN to customize its inputs, models, resources, and workflow behavior before deployment.

All blueprints Travel AI workflow blueprint

AI City Explorer workflow blueprint

Plan a trip using OpenStreetMap venue listings and available Open-Meteo forecasts

See where this blueprint fits in the production workflow lifecycle

Sequential

Use this blueprint

Pattern

Sequential

Agents

2

Functions

0

MCP servers

1

What the City Explorer blueprint does

Suggested starting request
I build a trip itinerary from OpenStreetMap venue listings and available weather forecasts. Provide the location, dates, group size, occasion, and preferences.

Inputs for the City Explorer workflow

Provide the following information when starting this workflow. Required inputs are validated before the first workflow stage runs.

Location
Required
City or neighborhood (e.g. 'Lower East Side, Manhattan')
Type: String
Dates
Required
Trip dates in YYYY-MM-DD format or plain English (e.g. 'June 6-8, 2026')
Type: String
Group Size
Required
Number and type of people (e.g. '6 adults' or 'family of 4 with young kids')
Type: String
Description
Required
What's the occasion and any preferences? (e.g. 'graduation dinner, loves Italian food and rooftop bars')
Type: String

Input template

This request shape is generated from the blueprint's input schema. Angle-bracket values are placeholders; defaults and examples appear only when the source blueprint defines them.

{
  "location": "<required string>",
  "dates": "<required string>",
  "group_size": "<required string>",
  "description": "<required string>"
}

How the City Explorer AI workflow works

This travel blueprint uses a sequential workflow with 2 agents, 0 functions, and 1 MCP server. Open it in GraphN to customize the resources, inputs, and workflow behavior for your use case.

Scout
Agent using LocalScout
Plan
Agent using TripPlanner

Blueprint resources and prerequisites

These are the actual agents, functions, and MCP servers declared by the blueprint. If an MCP server connects to an external system, configure the required connection and credentials in your GraphN workspace before running the workflow.

AI agent

LocalScout

AI agent

TripPlanner

MCP server

CityTools

Tools: Find Places Nearby, Get Weather Forecast

Workflow output contract

The completed workflow makes the following output available to downstream steps, applications, or API clients:

Result

Frequently asked questions

What does the City Explorer blueprint do?: Plan a trip using OpenStreetMap venue listings and available Open-Meteo forecasts
What inputs does the City Explorer workflow use?: The workflow uses Location, Dates, Group Size, Description. Required fields and their expected formats are listed on this page.
What resources are included in the City Explorer blueprint?: The blueprint contains 2 AI agents, 0 functions, 1 MCP server. Its workflow pattern is Sequential.
Can I customize the City Explorer blueprint in GraphN?: Yes. Open the blueprint in GraphN to customize its inputs, models, resources, and workflow behavior before deployment.