TimelinesAI
MessagingAutomate WhatsApp for a whole team through a TimelinesAI workspace, sending messages, voice notes, and attachments and organising chats. Agents keep shared WhatsApp coverage from depending on one person's phone.
What This Integration Enables
The problem TimelinesAI solves is organisational rather than technical. A WhatsApp number that customers rely on tends to live on a specific person's phone, which means coverage, history and escalation all depend on that person being awake and employed. TimelinesAI turns that into a workspace: multiple connected WhatsApp accounts, teammates with roles, chats that can be assigned to a responsible person, labels for segmentation, notes the customer never sees, and quota you can read before you spend it. This connector is the one to reach for when the requirement is that a team, not an individual, is reachable on WhatsApp.
It is also one of the few WhatsApp platforms in this catalog with genuine triggers. On Incoming Message and On Workspace Event both manage their own webhook subscriptions, so FlowRunner registers and removes them for you rather than sending you into a settings screen. TimelinesAI documents the delivery envelope, event_type and data, but not every field inside data, so the payload is passed through verbatim and the flow reads what it needs. Outbound is equally direct: Send Message To Phone reaches a number with no prior chat or contact, which makes it the usual starting point for automation, and Send Message To JID exists for the case where a webhook handed the flow a WhatsApp JID rather than a phone number. Worth planning around: each send consumes one message credit, and text combined with an attachment consumes two, which is why Get Workspace Info belongs in any flow that sends in bulk.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Inbound triaged before the team opens the inbox
On Incoming Message fires at 07:12. The agent reads the sender's number from the payload, looks the contact up in Pipedrive, and finds an open deal owned by a named rep. It calls Get Chat to see the current state, then Update Chat to assign that rep as the responsible teammate, and Add Labels to tag the thread with the deal stage while preserving whatever labels it already carried. Add Note writes the deal value, the last activity and the open quote into the thread, marked as a team note so it never reaches the customer. When the rep opens TimelinesAI, the conversation is already theirs and already explained. The agent has done the routing and the research and left the reply to a person, which is the right split for a channel customers read as a direct line to someone they know.
Outbound with the delivery actually confirmed
An invoice is issued in QuickBooks Online. The agent calls Upload File From URL to put the PDF into the workspace, which returns a file UID, then Send Message To Phone with the text and that attachment, reaching the customer without any existing chat. Because this send costs two credits rather than one, the flow checks Get Workspace Info first when it is running a batch. Later it calls Get Message Status, which returns the sending history and each delivery state the message passed through, and writes back to the invoice record whether the customer actually read it. Chasing an unpaid invoice is a different conversation when you know the reminder was delivered and read than when you are guessing.
Threads that close themselves, and labels that survive
A support thread is resolved and the ticket closes in Zendesk. The agent calls Update Chat to mark the conversation closed and clear the responsible teammate, and adds a resolution label. It uses Add Labels rather than Replace Labels deliberately, because Replace Labels removes every label not in the supplied list, and the routing labels applied earlier in the thread's life are what the weekly report is built on. Where a full reset genuinely is wanted, at the end of a seasonal campaign for instance, Replace Labels is the right operation and the flow says so explicitly rather than reaching for it by default.
Human-in-Loop Highlight
Invite Teammate is where this connector gets a gate, and it is a gate about access rather than about messaging. A TimelinesAI workspace holds the WhatsApp history of every connected account. Inviting someone into it, with a role and a team, grants them visibility of customer conversations that were never scoped to them, and Revoke Invitation only cancels an invitation that is still pending. So when an identity or HR system says a new support hire has started, the agent does the preparation and stops before the grant. It reads List Teammates to show who is already in the workspace and with what roles, resolves the role and team the new hire's job title maps to, and posts the request: "Joana Peres, Support Specialist, starting Monday per BambooHR. She would be invited as an Agent on the Support team, which gives visibility of all 4 connected numbers including the billing line. Confirm, restrict the team, or hold?" The workspace owner answers and the flow proceeds on that answer. Provisioning is exactly the kind of routine, high-volume, low-drama task an agent should own end to end right up to the moment it hands someone the keys, and that last step is where human-in-the-loop belongs.
Agent Capabilities
28 actionsMessaging
9- Send Message To Phone Sends a WhatsApp message to a phone number with no existing chat or contact required, which makes it the usual starting point for outbound automation. Text is limited to 2000 characters and an attachment can be included by referencing a file already uploaded to the workspace. Each send consumes one message credit, or two when text and an attachment are combined.
- Send Message To Chat Sends a message into an existing chat or group by its TimelinesAI chat ID, optionally quoting an earlier message as a reply so threaded conversations stay readable for the customer.
- Send Message To JID Sends a message to a contact or group addressed by its WhatsApp JID, the internal identifier of the form [email protected]. Used when a flow already holds a JID from a webhook delivery rather than a phone number.
- Send Voice Message Sends a voice note into an existing chat or group, with the audio fetched from a public URL as an OGG, OGA or MP3 file. It is delivered as a WhatsApp recording rather than as a file attachment.
- List Messages Returns the message history of a chat with filters for direction, date range and position relative to another message. This is how an agent reads what a customer said before deciding how to respond.
- Get Message Retrieves a single message by its UID with its text, direction, attachment and the chat it belongs to.
- Get Message Status Returns the sending history of a message, showing each delivery state it passed through, so a flow can confirm a notification actually reached and was read.
- Get Reactions Returns the current map of emoji reactions on a message, showing which participant set each one.
- Update Reactions Sets or clears your emoji reaction on a message. A single emoji character reacts; an empty string removes a reaction set earlier.
Chats
7- List Chats Returns chats in the workspace with filters for label, WhatsApp account, group or direct, responsible teammate, name, phone number, read state, closed state and creation date, paged 50 at a time.
- Get Chat Retrieves a single chat by identifier with its name, participants, labels, responsible teammate and open or closed state.
- Update Chat Changes a chat's name, assigns or clears the responsible teammate, closes or reopens it, marks it read or unread, and switches the built-in AI agent auto-response on or off. Only the fields supplied are changed.
- Add Note Adds a note to a chat, shown to the team inside TimelinesAI and never delivered to the customer on WhatsApp. Notes can be marked private so only the author sees them.
- List Labels Returns the labels currently applied to a chat, which is how TimelinesAI segments conversations for filtering and reporting.
- Add Labels Adds labels to a chat while keeping the labels it already carries. Labels that do not yet exist in the workspace are created.
- Replace Labels Replaces every label on a chat with the set supplied, removing any label not in the list. Reach for Add Labels instead unless a full reset is genuinely intended.
Files
5- Upload File From URL Uploads a file to the workspace by giving TimelinesAI a publicly accessible URL to fetch, detecting the file name and MIME type automatically unless overridden. The returned file UID is what the send operations use as an attachment.
- Upload File Uploads a file to the workspace as a multipart request, fetching the bytes from the supplied URL first. Used when the source cannot be reached by TimelinesAI directly but is reachable from your flow. A caption can be stored alongside the file.
- List Files Returns the files uploaded to the workspace, optionally filtered by file name.
- Get File Retrieves the details of an uploaded file together with a temporary download URL that stays valid for 15 minutes.
- Delete File Removes an uploaded file from the workspace. Messages that already delivered the file are unaffected.
Workspace
7- Get Workspace Info Returns the workspace identity and plan together with current quota usage for messages, API calls and transactions. Agents check it before a broadcast so a flow does not exhaust the sending quota partway through.
- List WhatsApp Accounts Returns the WhatsApp accounts connected to the workspace with their phone numbers and connection state. Those phone numbers are how a flow chooses which account a message is sent from.
- List Teammates Returns the teammates in the workspace with their names, email addresses and roles. The email addresses are what Update Chat expects when assigning a responsible person.
- Invite Teammate Sends a workspace invitation to an email address and assigns the new user a role and team. This grants access to the workspace's conversations, which is why it belongs behind a human decision rather than inside an unattended provisioning loop.
- Revoke Invitation Cancels a pending workspace invitation so the recipient can no longer use it to join.
- List Webhooks Returns every webhook subscription in the workspace with its event type, destination URL and error counter, including subscriptions created outside this connection.
- Get Webhook Retrieves a single webhook subscription by identifier, showing the event it listens for, its destination URL and whether deliveries are paused.
Triggers
2 triggersEvent Triggers
2- On Incoming Message Fires when a WhatsApp account in the workspace receives a new message. TimelinesAI creates the webhook subscription for the message received event and each delivery runs your flow. The event body is passed through under Data exactly as TimelinesAI sends it, because the vendor documents the envelope but not every field inside it.
- On Workspace Event Fires when one of the selected TimelinesAI events occurs, covering sent messages, reactions, new and reassigned chats, WhatsApp account connection changes and call activity. One webhook subscription is created per selected event. The account connection events are the ones worth wiring to an alert, because a disconnected account is a silently unstaffed channel.
Frequently Asked Questions
What can FlowRunner do with TimelinesAI?
FlowRunner agents can run Send Message To Phone, Send Message To Chat, and Send Message To JID in TimelinesAI, plus 25 more actions.
Does connecting TimelinesAI to FlowRunner require OAuth?
No. TimelinesAI connects to FlowRunner with an API key, no OAuth flow required.
Can TimelinesAI trigger a FlowRunner workflow automatically?
Yes. TimelinesAI supports 2 triggers that can start a FlowRunner workflow automatically.
Start building with TimelinesAI
$100 in credits. No card required. Connect in minutes.