Send Direct Message: X (Twitter) 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
Recipient User ID user_id	string	Required	The user ID of the recipient (not username — use 'Get User' to resolve username to ID)
Message Text text	textarea	Required	The message text (max 10,000 characters)

Sample request

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

Returns

{
  "data": {
    "dm_event_id": "789",
    "dm_conversation_id": "123-456"
  }
}

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

FAQ

Questions about Send Direct Message.

What does the Send Direct Message action do in X (Twitter)?

Sends a direct message to an X/Twitter user. Recipient must either follow the sender or have DMs open to everyone.

What inputs does Send Direct Message require?

Required: Recipient User ID, Message Text. 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 X (Twitter) 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 Direct Message support batch operations?

Yes. Run Send Direct Message inside a Loop node to process arrays. Tiny Command handles X (Twitter)'s rate limits automatically so you don't have to throttle manually.

More actions