IPGeolocation ACTION
Get Timezone
Retrieve timezone information using a timezone name, IP address, coordinates, city, IATA code, ICAO code, or UN/LOCODE. See the documentation
- Action
- Read only
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's IPGeolocation account once, then configure and run Get Timezone from your backend or agent.
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: "ipgeolocation-get-timezone",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
ipgeolocation: { authProvisionId: "apn_xxxxxxx" },
tz: "Timezone Name",
ip: "IP Address",
},
})
console.log(result)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": "ipgeolocation-get-timezone",
"configured_props": {
"ipgeolocation": { "authProvisionId": "apn_xxxxxxx" },
"tz": "Timezone Name",
"ip": "IP Address"
}
}'// 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": "ipgeolocation",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "ipgeolocation-get-timezone",
arguments: {
tz: "Timezone Name",
ip: "IP Address",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
tz Timezone Name | string | IANA timezone name to look up (e.g. America/New_York). Optional |
ip IP Address | string | IPv4 or IPv6 address to look up timezone for. Leave blank to lookup timezone for the caller's IP address if no other parameters are provided Optional |
lat Latitude | string | Latitude coordinate (e.g. 40.7128). Optional |
long Longitude | string | Longitude coordinate (e.g. -74.0060). Optional |
location Location | string | City or physical address string (e.g. New York, USA) Optional |
iata IATA Code | string | Airport IATA code (e.g. JFK) Optional |
icao ICAO Code | string | Airport ICAO code (e.g. KJFK) Optional |
locode UN/LOCODE | string | UN/LOCODE for a port or city (e.g. USNYC) Optional |
lang Language | string | Language for the response. Defaults to English. Only available on paid plans Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- ipgeolocation-get-timezone
- Version
- 0.0.2
- App
- IPGeolocation
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗