CONNECT APP
Build with OpenWeather API
Travel
- API key
MCP
Give your agent OpenWeather API tools
Every OpenWeather API action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's OpenWeather API account for each tool call — you store no tokens.
// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "openweather_api",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Get Current Weather by Location:
const result = await mcp.callTool({
name: "openweather_api-get-current-weather-by-location",
arguments: {
city: "City",
stateCode: "State code",
},
})# access_token: mint a short-lived token with the Connect SDK — see the MCP guide
headers = {
"Authorization": f"Bearer {access_token}",
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", # any stable ID for this user in your system
"x-pd-app-slug": "openweather_api",
}
async with streamablehttp_client("https://remote.mcp.pipedream.net/v3", headers=headers) as (read, write, _):
async with ClientSession(read, write) as session:
await session.initialize()
tools = await session.list_tools()
# e.g. run Get Current Weather by Location:
result = await session.call_tool("openweather_api-get-current-weather-by-location", {
"city": "City",
"stateCode": "State code",
})API PROXY
Call the OpenWeather API API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the OpenWeather API API with the connected user's credentials attached. You store no tokens and write no refresh logic.
const resp = await pd.proxy.get({
externalUserId: "{external_user_id}", // any stable ID for this user in your system
accountId: "apn_xxxxxxx",
url: "https://api.openweathermap.org/data/2.5/weather",
})
// Any allowed OpenWeather API endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.# The path segment is the target URL, URL-safe base64 encoded:
# https://api.openweathermap.org/data/2.5/weather
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9hcGkub3BlbndlYXRoZXJtYXAub3JnL2RhdGEvMi41L3dlYXRoZXI?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run OpenWeather API actions from your backend
Connect a user's OpenWeather API account once, then run Get Current Weather by Location on their behalf from your own code — TypeScript, Python, or plain HTTP.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "openweather_api-get-current-weather-by-location",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
openweather_api: { authProvisionId: "apn_xxxxxxx" },
city: "City",
stateCode: "State code",
},
})from pipedream import Pipedream
pd = Pipedream(
client_id="{oauth_client_id}",
client_secret="{oauth_client_secret}",
project_id="{project_id}",
project_environment="production",
)
result = pd.actions.run(
id="openweather_api-get-current-weather-by-location",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"openweather_api": {"authProvisionId": "apn_xxxxxxx"},
"city": "City",
"stateCode": "State code",
},
)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "openweather_api-get-current-weather-by-location",
"configured_props": {
"openweather_api": { "authProvisionId": "apn_xxxxxxx" },
"city": "City",
"stateCode": "State code"
}
}'TOOLS
OpenWeather API actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Get Current Weather by Location
actionRetrieves the current weather condition by location longitude and latitude. See the docs here. For more accurate reading, you are advised to fill in the country and/or state codeRead-onlyv0.0.2 -
Get Current Weather by ZIP code
actionRetrieves the current weather for a given (ZIP, country)Read-onlyv0.2.2 -
Get Current Weather Forecast by Location
actionRetrieves 1-16 days weather forecast for a specified location. See the docs here. For more accurate reading, you are advised to fill in the country and/or state codeRead-onlyv0.0.3 -
Get Weather Forecast by ZIP code
actionRetrieves the 5-day weather forecast for a given (ZIP, country)Read-onlyv0.3.2
EVENTS
OpenWeather API triggers
Event sources your backend can deploy for users and receive through a webhook.
No OpenWeather API triggers are available yet.
MULTI-APP
Use OpenWeather API with other popular apps
Most products don't stop at one integration. Pair OpenWeather API with the other apps your users rely on, and ship use cases that span both.
- App slug
- openweather_api
- Authentication
- API key
- Categories
- Travel
- Actions
- 4
- Triggers
- 0
- API proxy
- Available