Send Location: Telegram action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Chat ID chat_id	string	Required	Chat ID
Latitude latitude	string	Required	Latitude. e.g. "40.7128"
Longitude longitude	string	Required	Longitude. e.g. "-74.0060"

Sample request

{
  "chat_id": "{{trigger.chat_id}}",
  "latitude": "40.7128",
  "longitude": "-74.0060"
}

Returns

{
  "ok": true,
  "result": {
    "location": {
      "latitude": 40.7128,
      "longitude": -74.006
    },
    "message_id": 125
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Send Location.

What does the Send Location action do in Telegram?

Sends a static lat/long point to a Telegram chat as a map preview. Use Send Venue if you also want a name and address attached.

What inputs does Send Location require?

Required: Chat ID, Latitude, Longitude. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Telegram returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Send Location support batch operations?

Yes. Run Send Location inside a Loop node to process arrays. Tiny Command handles Telegram's rate limits automatically so you don't have to throttle manually.

More actions