Send LINE Push Message: LINE 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
User ID to	string	Required	LINE user ID of the recipient
Message text	string	Required	Message

Sample request

{
  "to": "{{trigger.to}}",
  "text": "{{trigger.text}}"
}

Returns

{
  "id": "msg_lin_123",
  "status": "sent",
  "success": true
}

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

FAQ

Questions about Send LINE Push Message.

What does the Send LINE Push Message action do in LINE?

Alias for Push Message. Sends to a user who has prior interaction with the LINE Official Account. The standard transactional-LINE-message action.

What inputs does Send LINE Push Message require?

Required: User ID, Message. 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 LINE 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 LINE Push Message support batch operations?

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

More actions