TimelinesAI currently provides 7 triggers that can start a workflow and 11 actions a workflow can run. Use those building blocks to connect campaign activity to the records and follow-up it should influence.
Chat Closed
Fires when a chat is closed.
New Outgoing Chat
Fires when a new outgoing chat is initiated.
New Incoming Chat
Fires when a new incoming chat (i.e. from a user) is created.
New Sent Message
Fires when a message is sent (outgoing).
New Received Message
Fires when a message is received (incoming).
New Uploaded File
Fires when a new file is uploaded in a chat.
New WhatsApp Account
Fires when a new WhatsApp account is added/registered.
Send Message to Existing Chat
Sends a text message in a chat identified by chat_id
Send Uploaded File to Existing Chat
Send a file (media/attachment) to a chat, with metadata like file name, via existing chat.
Send File to Existing Chat
Similar to above: send a file attachment to a chat using URL or file input and name.
Send Message to New Chat
Create a new chat (new conversation) by specifying the WhatsApp account, phone number, and message.
Close Chat
Programmatically mark a chat as closed by its chat_id.
Find Chat
Look up a chat by parameters such as chat_id, phone, name, etc.
Find Message
Lookup a message by its WhatsApp message ID.
Find Uploaded File
Locate an uploaded file by filename or identifier.
Find Message Status
Lookup a message’s delivery status by message ID.
Find WhatsApp Account
Search for a WhatsApp account (by phone or ID).
Custom API Call
Make a custom API call to a specific endpoint
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported TimelinesAI event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
Chat Closed
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported TimelinesAI action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Send Message to Existing Chat
Combine TimelinesAI with another integration and Coherence records to connect campaign activity to the records and follow-up it should influence.
Starts with
Chat Closed
Finishes with
Send Message to Existing Chat, then preserve the outcome in Coherence
The exact authentication fields depend on TimelinesAI. The workflow structure stays straightforward:
Authorize the TimelinesAI account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with TimelinesAI or provide a complementary trigger or action.
TimelinesAI currently provides 7 triggers that can start a workflow and 11 actions a workflow can run. Use those building blocks to connect campaign activity to the records and follow-up it should influence.
TimelinesAI currently lists 7 triggers and 11 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported TimelinesAI triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
