Integrations · Messaging channels
X (Twitter) DM agents on VegaDūta
VegaDūta connects an AI agent to X (Twitter) direct messages through OAuth. You authorize the account, and the platform retrieves inbound DMs by polling — X's DM surface does not give us instant webhooks, so messages arrive on a polling cadence rather than the moment they are sent. Outbound replies go through the API, and X DMs work as a workflow trigger channel like every other messaging integration.
How the connection works
The integration authenticates with OAuth against your X account. Inbound DMs are fetched on a polling schedule and routed to your agent; the agent's replies are sent back through the API. Setup is a console-side authorization, not an app you host.
- OAuth-based account connection.
- Poll-based inbound DM retrieval — see the honest note below.
- Outbound DM replies through the API.
- X as a workflow trigger channel.
Honest note: polling, not instant webhooks
Inbound on this channel is poll-based, which means a short delay between a DM being sent and your agent seeing it. If your use case needs second-level latency, WhatsApp, Telegram, Slack, or Discord — all push-based — are better fits. We would rather tell you that here than have you discover it in production.
X DMs as workflow triggers
An inbound DM can start a Temporal-backed workflow — lead capture from an X audience, support intake, or any structured flow. Guardrails and human approval gates apply to the agent's tool calls, same as on every channel.
Frequently asked questions
Can an AI agent answer X (Twitter) DMs?
Yes. VegaDūta connects to your X account via OAuth, retrieves inbound DMs, and routes them to your agent, which replies through the API. The agent behaves like it does on any other channel — same knowledge, tools, and guardrails.
Are X DM replies instant?
Not quite — inbound retrieval is poll-based rather than webhook-pushed, so there is a short delay before the agent sees a new DM. Replies send immediately once the agent processes the message. For instant inbound, use a push-based channel like WhatsApp or Telegram.
How does VegaDūta authenticate with my X account?
Through OAuth: you authorize the connection from the console and the platform stores the resulting credentials per tenant. No password sharing is involved.
Can an X DM trigger a workflow?
Yes. X is one of VegaDūta's workflow trigger channels, so an inbound DM can start a Temporal-backed workflow — subject to the polling cadence on inbound delivery.
See it working in two minutes
The sandbox provisions a real tenant — describe an agent in one sentence and test it, no account, no card. Or browse ~90 industry workflow recipes to see what teams build.
