Integration
Connect TimelinesAI to SLF
When something happens in TimelinesAI, your agent does the next thing in SLF. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want TimelinesAI and SLF to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with TimelinesAI and SLF
Triggers and actions 6 triggers · 2 actions
Trigger
New Incoming ChatTriggers when a new incoming chat is created.
Trigger
New Outgoing ChatTriggers when a new outgoing chat is created.
Trigger
New Received MessageTriggers when a new incoming message is received.
Trigger
New Sent MessageTriggers when a new message is sent.
Trigger
New Uploaded FileTriggers when new uploaded_file is created.
Trigger
New Whatsapp AccountTriggers when new whatsapp_accounts is created.
Action
Send Uploaded File to Existing ChatSends uploaded file to existing chat.
Action
Get Stadt-Land-Fluss dataFetch the full German Stadt-Land-Fluss (city/country/river word-game) reference dataset via GET https://slftool.github.io/data.json. Static, unauthenticated, single-request JSON blob keyed by letter, each letter holding arrays for stadt (city), land (country), fluss (river), name, beruf (profession), tier (animal), and marke (brand). No query parameters — the vendor exposes no filtering or search; the whole dataset is returned every call and any per-letter/per-category lookup must be done client-side on the response.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews