TimelinesAI enables teams to manage and automate WhatsApp communications, integrating with various CRMs and tools to streamline workflows.
TimelinesAI enables teams to manage and automate WhatsApp communications, integrating with various CRMs and tools to streamline workflows. On Nagent, TimelinesAI is exposed as a fully-configurable communication integration that any agent can call — 13 actions, 1 trigger, and API key authentication. No code is required to wire TimelinesAI into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use TimelinesAI to automate the kinds of tasks communication teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
TimelinesAI also supports 1 event trigger ("New WhatsApp Message Received"), which lets your Nagent agents react to TimelinesAI activity in real time — for example, kicking off a downstream workflow the moment a relevant event fires.
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire TimelinesAI into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Triggers are the entry points of agents built on Nagent — pick one to fire your agent the moment a TimelinesAI event happens. Webhook triggers run instantly; poll triggers check on an interval you configure. Each shows its configuration parameters and the payload your agent receives.
TIMELINESAI_NEW_MESSAGE_RECEIVEDPolling trigger that monitors for new messages received in TimelinesAI WhatsApp chats.
Configuration
Filter messages from a specific chat ID. If not provided, all chats will be monitored
Periodic Interval to Check for Updates & Send a Trigger in Minutes
If true, only unread messages will be included
Maximum number of messages to fetch per polling cycle
Payload
ID of the chat the message belongs to
Type of event that triggered
Unique identifier of the message
Type of message (text, media, etc.)
Details of the message sender
Content of the message
ISO-8601 timestamp when message was sent
Every operation an agent can call against TimelinesAI, with input parameters and output schema. Drop these into any step of an agent built in Helix.
TIMELINESAI_DELETE_FILETool to delete an uploaded file by its UID. Use after confirming the file is no longer needed.
Input parameters
Unique identifier of the file to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
TIMELINESAI_DELETE_WEBHOOKTool to delete a webhook subscription by its ID. Use when you need to remove an existing webhook after confirming the webhook ID. Example: "Delete the webhook with ID '9f6a8c3d-56b7-4a1e-8f2e-abcdef123456'."
Input parameters
Unique identifier of the webhook subscription to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
TIMELINESAI_GET_CHAT_MESSAGESTool to get messages from a specific chat in TimelinesAI. Use when you need to retrieve message history or recent messages from a chat. Example: "Get the last 20 messages from chat 'chat_123abc'."
Input parameters
Maximum number of messages to return
Number of messages to skip before returning results
Unique identifier of the chat to retrieve messages from
Get messages after this message ID (for pagination)
Get messages before this message ID (for pagination)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
TIMELINESAI_GET_CHATSTool to get full or filtered list of all chats. Use when you need to browse or search chats with optional filters. Example: "List all unread chats assigned to me."
Input parameters
Maximum number of chats to return
List of chat types to include (e.g., \['group', 'direct'\])
Number of chats to skip before returning results
Search term to filter chats by name or content
If true, only chats that are muted
Filter chats by the specified label ID
If true, only chats that have at least one label
If true, only chats with unread messages are returned
Filter chats by the associated person ID
Field by which to sort results (e.g., 'createdAt')
Filter chats by the specified assignee ID
If true, only archived chats will be returned
If true, only chats that have been assigned
If true, only chats followed by the current user
ISO 8601 date string; return chats created after this timestamp
If true, only chats with open tasks
Filter chats by the specified integration ID
Sort order: 'asc' (ascending) or 'desc' (descending)
Filter chats involving the specified team member ID
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
TIMELINESAI_GET_FILE_DETAILSTool to retrieve metadata and temporary download URL for an uploaded file. Use after uploading a file or when needing its URL.
Input parameters
Unique identifier of the file to retrieve details for
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
TIMELINESAI_GET_WEBHOOKRetrieves detailed information about a specific webhook subscription by its ID. Use this action to: - Check webhook configuration (URL, event type, enabled status) - Monitor webhook health (error counter) - Verify webhook existence before updating or deleting Prerequisites: You must have a valid webhook ID. Use the Get Webhooks action to list all available webhooks first.
Input parameters
The unique webhook ID (numeric string). Use Get Webhooks action to list all available webhook IDs.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
TIMELINESAI_GET_WEBHOOKSRetrieves all webhook subscriptions configured for the workspace. Webhooks notify external systems about events (e.g., 'message:new', 'chat:new') in real-time. Use this to view existing webhook configurations, check their status, or retrieve webhook IDs for updates/deletion. Supports optional pagination via limit and offset parameters.
Input parameters
Maximum number of webhooks to return per page
Number of webhooks to skip before returning results
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
TIMELINESAI_GET_WHATSAPP_ACCOUNTSTool to list all WhatsApp accounts connected to the workspace. Use after configuring WhatsApp integration to verify accounts.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
TIMELINESAI_LIST_UPLOADED_FILESTool to list files uploaded in your TimelinesAI workspace. Use when you need to retrieve all uploaded files.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
TIMELINESAI_POST_MESSAGETool to send a WhatsApp text message to a phone number via TimelinesAI. Use this to send messages to any recipient phone number using one of your connected WhatsApp accounts as the sender. The message will be delivered immediately if the recipient number is reachable on WhatsApp. Example: Send 'Hello, how can I help you today?' from +15105566777 to +14151231234.
Input parameters
Message text to send. Note: text length is limited by the WhatsApp platform (currently 65,534 characters).
Recipient's phone number in international format with a leading '+' and country code.
Your sender WhatsApp number in international format with a leading '+' and country code. This must be a WhatsApp account that is already connected to your TimelinesAI workspace.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
TIMELINESAI_POST_WEBHOOKTool to create a new webhook subscription. Use when you have the event type and callback URL ready.
Input parameters
The HTTP endpoint URL that will receive webhook payloads.
Optional secret used to sign webhook payloads (HMAC).
Event type to subscribe to. Valid values: 'message:new', 'message:sent:new', 'message:received:new', 'whatsapp:account:connected', 'whatsapp:account:disconnected', 'whatsapp:account:suspended', 'whatsapp:account:resumed', 'chat:new', 'chat:incoming:new', 'chat:outgoing:new', 'chat:responsible:assigned', 'chat:responsible:unassigned'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
TIMELINESAI_PUT_WEBHOOKTool to update an existing webhook subscription. Use after confirming the webhook ID when you need to change the URL, subscribed event types, or enable/disable a webhook.
Input parameters
The URL endpoint that will receive webhook event notifications
Whether the webhook should be active. If omitted, current state is preserved
Single event type to subscribe to. Common types: 'message:new', 'chat:new', 'message:received:new', 'message:sent:new', 'chat:incoming:new', 'chat:outgoing:new', 'chat:responsible:assigned', 'chat:responsible:unassigned', 'whatsapp:account:connected', 'whatsapp:account:disconnected'
Unique identifier of the webhook subscription to update (numeric ID as string)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
TIMELINESAI_SEND_MESSAGESend a WhatsApp message to an existing chat in TimelinesAI. Use this action when you have a chat ID from the Get Chats action and want to send a message to that conversation. For sending messages to new phone numbers (not existing chats), use the 'Send WhatsApp Message to Number' action instead. Example: "Send message 'Hello world' to chat with ID 'chat_123abc'."
Input parameters
Unique identifier of the chat to send the message to. Obtain this from the Get Chats action.
The text message to send. Maximum length: 65,534 characters (WhatsApp platform limit).
Type of message to send. Common values: 'text' for text messages, 'media' for media messages. Defaults to 'text'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 40 agents privately built on Nagent that already use TimelinesAI.
Build on Nagent
Connect TimelinesAI to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find TimelinesAI, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, TimelinesAI is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once TimelinesAI is connected, you configure its 13 actions and 1 trigger directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop TimelinesAI steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a TimelinesAI event fires, the agent kicks off automatically.
Every TimelinesAI action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While TimelinesAI ships with 13 pre-built communication actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching TimelinesAI together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build TimelinesAI-based workflows tailored to your business.