Actions17
Send Venue
AI-generatedSummary
Sends a Telegram venue message to a specified chat using bot credentials.
Inputs
- botToken — Bot token from input (e.g. from Orchestrator/Strapi)
- chatId (required) — Chat ID where the venue will be sent
- replyToMessageId — Message ID to reply to
- replyMarkup — Inline keyboard or other reply markup
- latitude (required) — Latitude coordinate of the venue
- longitude (required) — Longitude coordinate of the venue
- venueTitle (required) — Title of the venue
- venueAddress (required) — Address of the venue
- useRateLimit — Enable Redis rate limiting to avoid 429 errors
Output shape
The node emits three result streams: success items (Telegram message objects for each venue), blocked‑403 items (indicating the bot was blocked), and error items (generic error payloads). Each stream is an array of result objects containing the original JSON payload and metadata.
Success output contains Telegram’s API response; blocked output adds error_code 403 details; error output includes the error details. The shape may vary per item but is consistent across the stream.
Examples
Example 1: Dispatch a venue to a known chat using bot token from a previous node
Set operation to Send Venue; provide botToken; set chatId, latitude, longitude, venueTitle, venueAddress; optionally add reply markup and replyToMessageId; enable rate limit if needed.
Example 2: Send a venue to a different chat in the same workflow
Change chatId value; keep required geolocation and venue fields; optionally adjust reply markup.
Example 3: Handle a blocked‑bot scenario gracefully
Configure downstream node to listen on the second output to detect blocked‑403 responses and trigger an alternative flow.