Read WhatsApp threads for context, then send the reply as an approved step.
TimelinesAI puts your team's WhatsApp traffic where the agent can read it. Look up connected accounts, pull a chat history, check which webhooks are feeding your other tools. When something needs to go out — a status note to a vendor, an update to an on-call contact — the agent drafts the message and holds it for your approval before it sends. Connected with an API key.
13 tools: 7 read, 6 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed TimelinesAI run looks like inside Luumen.
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
This connection exposes write actions such as delete file, delete webhook, send whatsapp message to number, create webhook subscription, and more. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to TimelinesAI — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Connect in minutes. Every action scoped, approved, and audited from day one.