TimelinesAI
TimelinesAI enables teams to manage and automate WhatsApp communications, integrating with various CRMs and tools to streamline workflows.
Verdict
Common use cases
- Pull unread customer chats into standup
- Search message history for order numbers
- Retrieve file metadata from WhatsApp uploads
- Create webhooks for new-message alerts
- Audit active webhook subscriptions
Integration
- Vendor
- TimelinesAI
- Category
- communication
- Auth
- API_KEY
- Tools
- 12
- Composio slug
timelinesai
Tools
- Create Webhook Subscription
Tool to create a new webhook subscription. use when you have the event type and callback url ready.
- Delete Filedestructive
Tool to delete an uploaded file by its uid. use after confirming the file is no longer needed.
- Delete Webhookdestructive
Tool 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'."
- Get Chat Messages
Tool 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'."
- Get Chats
Tool 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."
- Get File Details
Tool to retrieve metadata and temporary download url for an uploaded file. use after uploading a file or when needing its url.
- Get Webhook
Tool to retrieve details of a specific webhook subscription. use after confirming the webhook id.
- Get Webhooks
Tool to list all webhook subscriptions for the workspace. use when you need to retrieve configured webhooks, optionally with pagination.
- Get WhatsApp Accounts
Tool to list all whatsapp accounts connected to the workspace. use after configuring whatsapp integration to verify accounts.
- List Uploaded Files
Tool to list files uploaded in your timelinesai workspace. use when you need to retrieve all uploaded files.
- Send Message
Tool to send a message through timelinesai whatsapp integration. use after identifying the target chat id. example: "send message 'hello world' to chat with id 'chat 123abc'."
- Update Webhook
Tool 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.
Setup
Setup guide
- 11. In Switchy, open Settings > Integrations > MCP Servers and click Add Server. 2. Select TimelinesAI from the catalog. 3. Log in to your TimelinesAI workspace, navigate to Settings > API, and generate a new API key with read permissions for chats and messages plus write permissions for webhooks. 4. Paste the key into Switchy's API Key field and click Connect. 5. Switchy will verify the key and list the 12 available tools. 6. Open any Space, type '@TimelinesAI get chats' and send the message to confirm the connection works. 7. If you see a list of your WhatsApp chats, the integration is live and ready for team use.
What teammates see: by default, memories from TimelinesAI are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Unread Customer Threads
@TimelinesAI list all unread chats assigned to me so I can prioritize responses this morning.Open in a Space →
Recent Chat History
@TimelinesAI get the last 20 messages from chat 'chat_abc123' so I understand the customer's issue.Open in a Space →
File Download Link
@TimelinesAI retrieve file details for uid 'file_xyz789' and give me the download link.Open in a Space →
New Webhook Subscription
@TimelinesAI create a webhook subscription for event type 'message.received' with callback url 'https://example.com/hook'.Open in a Space →
List Active Webhooks
@TimelinesAI list all webhook subscriptions in our workspace so I can see what's currently active.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@TimelinesAI list all unread chats assigned to me from the last 48 hours
Found 7 unread chats assigned to you in the last 48 hours: 1. Chat with Sarah Chen (Customer Success) - 3 unread messages, last activity 2 hours ago 2. Support ticket #4521 - 5 unread messages, last activity 4 hours ago 3. Sales inquiry from Acme Corp - 2 unread messages, last activity 6 hours ago 4. Team discussion: Q1 planning - 8 unread messages, last activity 12 hours ago 5. Bug report #892 - 1 unread message, last activity 18 hours ago 6. Chat with vendor: CloudHost - 4 unread messages, last activity 24 hours ago 7. Onboarding: New client XYZ - 2 unread messages, last activity 36 hours ago All chats are currently assigned to your queue and awaiting response.
This example demonstrates the MCP's filtering capabilities for chat retrieval. Requires API key with read access to chats. The actual response structure depends on your workspace's chat volume and assignment rules — high-traffic teams may need narrower time windows or additional filters to avoid overwhelming results.
@TimelinesAI get the last 15 messages from the support ticket chat #4521 and summarize the customer's main issue
Retrieved 15 messages from support ticket #4521. The conversation shows: Customer (Jessica Martinez, jessica@techstartup.io) reported that their API integration has been returning 429 rate-limit errors since yesterday afternoon. They've tried reducing request frequency but errors persist. Your colleague Mark responded 6 hours ago asking for API key details, but the customer hasn't replied yet. Main issue: Persistent 429 errors despite throttling attempts. Customer provided error logs in message 8 (uploaded file: error_logs_jan15.txt). They mention this is blocking their production deployment scheduled for tomorrow. Recommended next step: Check if their API key tier supports their current request volume, or escalate to engineering if rate limits appear misconfigured.
This example pairs the MCP's message retrieval with AI reasoning to extract actionable insights from chat history. Useful for context-switching into ongoing conversations. Note that file attachments in messages return metadata only — you'll need the separate Get File Details tool to access actual file contents if needed for deeper analysis.
@TimelinesAI create a webhook subscription for new message events pointing to https://our-crm.com/webhooks/timelinesai
Webhook subscription created successfully: Webhook ID: 9f6a8c3d-56b7-4a1e-8f2e-abcdef123456 Event type: message.created Callback URL: https://our-crm.com/webhooks/timelinesai Status: Active Created: 2025-01-15 14:32:18 UTC Your endpoint will now receive POST requests whenever a new message is created in any chat. Each webhook payload includes message content, sender details, chat ID, and timestamp. Ensure your endpoint returns 200 OK within 5 seconds to avoid retry attempts.
This write operation demonstrates real-time integration setup. Your callback URL must be publicly accessible and return proper HTTP responses — failed deliveries trigger exponential backoff retries. Requires API key with webhook management permissions. Consider testing with a single event type before subscribing to high-volume events across your entire workspace.
Use-case deep-dives
When TimelinesAI wins for support teams routing WhatsApp inquiries
A 6-person support team handling 200+ daily WhatsApp customer inquiries uses TimelinesAI to route conversations and track handoffs between agents. The Get Chats tool with filters (unread, assigned-to-me) surfaces the right queue at shift start, and Get Chat Messages pulls full context before an agent replies. Create Webhook Subscription pushes new inbound messages to a Slack channel so no inquiry sits idle. This works cleanly when your team already uses WhatsApp Business API and needs structured chat assignment—TimelinesAI's 12 tools cover the full lifecycle from list-filter to message-pull to webhook-notify. If your volume is under 50 chats per day or you don't need assignment logic, a simpler notification tool is enough. For teams triaging multi-agent WhatsApp queues, this MCP eliminates the tab-switching tax.
When this MCP handles post-demo WhatsApp sequences for small sales teams
A 3-person B2B sales team runs product demos, then follows up via WhatsApp to share contracts and answer technical questions. They use TimelinesAI's Get Chats to filter conversations by tag (demo-completed, contract-sent) and Get Chat Messages to review the last exchange before crafting a personalized follow-up. The Delete File tool cleans up outdated contract PDFs after a deal closes, keeping the workspace tidy. Webhooks push replies into their CRM so no prospect message goes unnoticed. This setup shines when your sales motion is WhatsApp-native and you need structured follow-up tracking across 20-100 active conversations. If your team is email-first or handles fewer than 10 concurrent deals, the overhead isn't worth it. For WhatsApp-heavy sales teams, this MCP turns chat history into a follow-up engine.
When TimelinesAI fits community teams managing WhatsApp group activity
A solo community manager runs 8 WhatsApp groups for a membership program, each with 30-80 members. She uses Get Chats with filters to spot groups with unread spikes (sign of a hot thread or moderation need) and Get Chat Messages to pull the last 50 messages before jumping in. Create Webhook Subscription sends her a Slack ping when a group crosses 10 unread messages in an hour, so she can intervene before a thread derails. The Get File Details tool helps her audit shared resources (PDFs, images) members upload. This works when your community lives on WhatsApp and you manage multiple groups solo or with one assistant. If your groups are under 20 members each or you check them manually twice a day, webhooks add complexity you don't need. For multi-group WhatsApp communities, this MCP gives you the dashboard WhatsApp doesn't.
Frequently asked
What does the TimelinesAI MCP do in Switchy?
It connects Switchy to your TimelinesAI workspace so AI agents can read chat messages, manage files, and configure webhooks without leaving the conversation. You can ask an agent to pull message history from specific chats, list unread conversations, or set up event subscriptions — all through natural language instead of clicking through the TimelinesAI interface.
Do I need admin access to connect TimelinesAI?
You need a TimelinesAI API key with permissions matching what you want the MCP to do. If you only want to read chats, a read-only key works. To create webhooks or delete files, you'll need write permissions. Check with your TimelinesAI workspace admin if you're unsure which scopes your key has.
Can the MCP send messages in TimelinesAI chats?
No. The 12 available tools focus on reading chat history, managing uploaded files, and configuring webhooks. There's no tool to send outbound messages. If you need to reply to customers through TimelinesAI, you'll still do that in the TimelinesAI app itself or via their direct API.
Why use this instead of just opening TimelinesAI?
It saves context-switching when you're already working in Switchy. An agent can pull message threads, check which chats are unread, or grab file URLs without you tabbing out. It's faster for bulk operations like auditing webhook configs across your workspace or searching chat history by filter criteria.
Who on the team should connect the TimelinesAI MCP?
Whoever manages your TimelinesAI workspace or handles customer support automation. They'll need access to generate an API key. Once connected in Switchy, any team member in that workspace can ask agents to query chats or manage webhooks, but the API key's permissions control what's actually allowed.