Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

TimelinesAI

TimelinesAI integration for Flows360 workflows.

CategoryMarketing
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 24, 2026

Overview

Connect TimelinesAI with Flows360

TimelinesAI integration for Flows360 workflows.

Use the TimelinesAI connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 11 actions and 7 triggers.

Available actions

  • Send Message to Existing Chat
  • Send Uploaded File to Existing Chat
  • Send File to Existing Chat
  • Send Message to New Chat
  • Close Chat
  • Find Chat
  • Find Message
  • Find Uploaded File
  • Plus 3 additional declared actions.

Available triggers

  • Chat Closed
  • New Outgoing Chat
  • New Incoming Chat
  • New Sent Message
  • New Received Message
  • New Uploaded File
  • Plus 1 additional declared trigger.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: TimelinesAI
  • Package: @activepieces/piece-timelines-ai@0.2.0
  • Exact artifact digest: sha256:be48228611b1833ffacf6899619c2ada2ef7eaa89b23b35d44bdc4ee708d1c02
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Send Message to Existing Chat (sendMessageToExistingChat), Sends a text message in a chat identified by chat_id Classification: read.
  • Send Uploaded File to Existing Chat (sendUploadedFileToExistingChat), Send a file (media/attachment) to a chat, with metadata like file name, via existing chat. Classification: read.
  • Send File to Existing Chat (sendFileToExistingChat), Similar to above: send a file attachment to a chat using URL or file input and name. Classification: read.
  • Send Message to New Chat (sendMessageToNewChat), Create a new chat (new conversation) by specifying the WhatsApp account, phone number, and message. Classification: read.
  • Close Chat (closeChat), Programmatically mark a chat as closed by its chat_id. Classification: read.
  • Find Chat (findChat), Look up a chat by parameters such as chat_id, phone, name, etc. Classification: read.
  • Find Message (findMessage), Lookup a message by its WhatsApp message ID. Classification: read.
  • Find Uploaded File (findUploadedFile), Locate an uploaded file by filename or identifier. Classification: read.
  • Find Message Status (findMessageStatus), Lookup a message’s delivery status by message ID. Classification: read.
  • Find WhatsApp Account (findWhatsappAccount), Search for a WhatsApp account (by phone or ID). Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • Chat Closed, polling.
  • New Outgoing Chat, webhook.
  • New Incoming Chat, webhook.
  • New Sent Message, webhook.
  • New Received Message, webhook.
  • New Uploaded File, polling.
  • New WhatsApp Account, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects18
Supported actions11
Triggers7

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Send Message to Existing Chat Yes No Sends a text message in a chat identified by chat_id
Send Uploaded File to Existing Chat Yes No Send a file (media/attachment) to a chat, with metadata like file name, via existing chat.
Send File to Existing Chat Yes No Similar to above: send a file attachment to a chat using URL or file input and name.
Send Message to New Chat Yes No Create a new chat (new conversation) by specifying the WhatsApp account, phone number, and message.
Close Chat Yes No Programmatically mark a chat as closed by its chat_id.
Find Chat Yes No Look up a chat by parameters such as chat_id, phone, name, etc.
Find Message Yes No Lookup a message by its WhatsApp message ID.
Find Uploaded File Yes No Locate an uploaded file by filename or identifier.
Find Message Status Yes No Lookup a messageu2019s delivery status by message ID.
Find WhatsApp Account Yes No Search for a WhatsApp account (by phone or ID).
Custom API Call Yes No Make a custom API call to a specific endpoint
Chat Closed Yes No polling trigger declared by the pinned package.
New Outgoing Chat Yes No webhook trigger declared by the pinned package.
New Incoming Chat Yes No webhook trigger declared by the pinned package.
New Sent Message Yes No webhook trigger declared by the pinned package.
New Received Message Yes No webhook trigger declared by the pinned package.
New Uploaded File Yes No polling trigger declared by the pinned package.
New WhatsApp Account Yes No webhook trigger declared by the pinned package.

Supported actions

Send Message to Existing Chat · Read

Sends a text message in a chat identified by chat_id

send_message_to_existing_chat · Risk: low · Retry: safe

Inputs

  • chat_id · string · Required, Select the chat to send the message to
  • text · string · Required, The text content of the message to be sent.
  • file · object · Optional, Optional file to send with the message.
  • label · string · Optional, Optional label to categorize or tag the message.
  • attachment_template_id · number · Optional, Optional ID of the attachment template to use for the message.
Send Uploaded File to Existing Chat · Read

Send a file (media/attachment) to a chat, with metadata like file name, via existing chat.

send_uploaded_file_to_existing_chat · Risk: low · Retry: safe

Inputs

  • chat_id · string · Required, Select the chat to send the message to
  • file_id · string · Required, Select the uploaded file
Send File to Existing Chat · Read

Similar to above: send a file attachment to a chat using URL or file input and name.

send_file_to_existing_chat · Risk: low · Retry: safe

Inputs

  • chat_id · string · Required, Select the chat to send the message to
  • file · object · Required, The file to be sent in the chat.
Send Message to New Chat · Read

Create a new chat (new conversation) by specifying the WhatsApp account, phone number, and message.

send_message_to_new_chat · Risk: low · Retry: safe

Inputs

  • contactType · string · Required, Select the type of contact identifier
  • contact · object · Required, Select the contact identifier based on the chosen contact type
  • whatsapp_account_id · string · Optional, Select the WhatsApp account
  • text · string · Optional, The text message to be sent in the chat.
  • file · object · Optional, The file to be sent in the chat.
  • label · string · Optional, An optional label to categorize the chat.
  • chat_name · string · Optional, An optional name for the chat (useful for group chats).
  • attachment_template_id · number · Optional, Optional ID of a predefined attachment template to use when sending files.
Close Chat · Read

Programmatically mark a chat as closed by its chat_id.

close_chat · Risk: low · Retry: safe

Inputs

  • chat_id · string · Required, Select the chat to send the message to
Find Chat · Read

Look up a chat by parameters such as chat_id, phone, name, etc.

find_chat · Risk: low · Retry: safe

Inputs

  • label · array · Optional, Filter by labels assigned to the chat
  • whatsapp_account_id · string · Optional, Select the WhatsApp account
  • group · boolean · Optional, Filter by whether the chat is a group chat
  • responsible · array · Optional, Filter by the user responsible for the chat (email)
  • name · string · Optional, Filter by the name of the chat
  • read · boolean · Optional, Filter by whether the chat is marked as read
  • closed · boolean · Optional, Filter by whether the chat is closed
  • chatgpt_autoresponse_enabled · boolean · Optional, Filter by whether ChatGPT autoresponse is enabled for the chat
  • created_after · string · Optional, Filter chats created after this date
  • created_before · string · Optional, Filter chats created before this date
  • page · number · Optional, Page number for paginated results
Find Message · Read

Lookup a message by its WhatsApp message ID.

find_message · Risk: low · Retry: safe

Inputs

  • message_uid · string · Required, The unique identifier of the message to find.
Find Uploaded File · Read

Locate an uploaded file by filename or identifier.

find_uploaded_file · Risk: low · Retry: safe

Inputs

  • filename · string · Optional, The name of the uploaded file to search for.
Find Message Status · Read

Lookup a messageu2019s delivery status by message ID.

find_message_status · Risk: low · Retry: safe

Inputs

  • message_uid · string · Required, The unique identifier of the message to look up.
Find WhatsApp Account · Read

Search for a WhatsApp account (by phone or ID).

find_whatsapp_account · Risk: low · Retry: safe

Inputs

  • id · string · Optional, The unique identifier of the WhatsApp account to search for.
  • phone · string · Optional, The phone number associated with the WhatsApp account to search for.
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

Chat Closed · Poll

Fires when a chat is closed.

New Outgoing Chat · Webhook

Fires when a new outgoing chat is initiated.

New Incoming Chat · Webhook

Fires when a new incoming chat (i.e. from a user) is created.

New Sent Message · Webhook

Fires when a message is sent (outgoing).

New Received Message · Webhook

Fires when a message is received (incoming).

New Uploaded File · Poll

Fires when a new file is uploaded in a chat.

New WhatsApp Account · Webhook

Fires when a new WhatsApp account is added/registered.

Setup

Setup

  1. Add the TimelinesAI connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-timelines-ai@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 11 actions and 7 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required TimelinesAI connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-timelines-ai@0.2.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com