Send Sticker: 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
Sticker (file_id or URL) sticker	string	Required	Sticker (file_id or URL)

Sample request

{
  "chat_id": "{{trigger.chat_id}}",
  "sticker": "{{trigger.sticker}}"
}

Returns

{
  "ok": true,
  "result": {
    "message_id": 129
  }
}

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

FAQ

Questions about Send Sticker.

What does the Send Sticker action do in Telegram?

Sends a Telegram sticker by file_id (or URL for WebP). Sticker file IDs can be captured from any inbound sticker message you receive.

What inputs does Send Sticker require?

Required: Chat ID, Sticker (file_id or URL). 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 Sticker support batch operations?

Yes. Run Send Sticker 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