Send Contact: 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. Example: -100123456789
Phone Number phone_number	string	Required	Phone Number. e.g. "+15551234567"
First Name first_name	string	Required	First Name. e.g. "John"
Last Name last_name	string	Optional	Last Name. e.g. "Doe"

Sample request

{
  "chat_id": "e.g. -100123456789",
  "phone_number": "+15551234567",
  "first_name": "John",
  "last_name": "Doe"
}

Returns

{
  "ok": true,
  "result": {
    "contact": {
      "first_name": "John",
      "phone_number": "+15551234567"
    },
    "message_id": 123
  }
}

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

FAQ

Questions about Send Contact.

What does the Send Contact action do in Telegram?

Sends a contact card (name + phone number) to a Telegram chat. Useful for handoff flows where a bot needs to surface a human contact.

What inputs does Send Contact require?

Required: Chat ID, Phone Number, First Name. 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 Contact support batch operations?

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