Answer Callback Query: 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
Callback Query ID callback_query_id	string	Required	Callback Query ID
Notification Text text	string	Optional	Notification Text
Show Alert show_alert	options	Optional	Show Alert. Options: No, Yes

Sample request

{
  "callback_query_id": "{{trigger.callback_query_id}}",
  "text": "{{trigger.text}}",
  "show_alert": "{{trigger.show_alert}}"
}

Returns

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

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

FAQ

Questions about Answer Callback Query.

What does the Answer Callback Query action do in Telegram?

Acknowledges a callback query from a Telegram inline keyboard button, optionally showing a toast or alert to the user. Required to remove the "loading" spinner on the tapped button.

What inputs does Answer Callback Query require?

Required: Callback Query ID. 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 Answer Callback Query support batch operations?

Yes. Run Answer Callback Query 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