Connect Agentql to Botstar
When something happens in Agentql, Notis takes the next step in Botstar. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Agentql to Botstar
Initialize BotStar chat for an AgentQL session
Use a webhook to start an AgentQL-powered session, retrieve the BotStar app ID, and initialize its live chat widget.
Review BotStar bots before AgentQL research runs
Schedule a BotStar bot inventory so you can identify the bot to use in upcoming AgentQL research and automation work.
Inspect BotStar attributes for AgentQL data
When an HTTP request starts the flow, list BotStar bot attributes to check which existing fields can hold research context.
Audit BotStar CMS entities for AgentQL content
Schedule a review of BotStar CMS entities so AgentQL-derived content has a clear place in your bot's existing structure.
Find BotStar content items for AgentQL review
Start from a webhook to list BotStar CMS items, optionally filtered by name or status, for a targeted research review.
Check BotStar bot details for AgentQL operations
On a schedule, retrieve detailed BotStar bot information to keep operational context ready for AgentQL work.
Inspect a BotStar entity before AgentQL content updates
Retrieve a BotStar entity's field configuration from a webhook flow before deciding how AgentQL findings should change its content.
Retrieve a BotStar item for AgentQL enrichment
Schedule retrieval of a specific BotStar CMS item so its current values are ready for comparison with new AgentQL research.
Update a live chat profile with AgentQL context
When a webhook starts the flow, update user details on an active BotStar live chat session using context you provide or retrieve with AgentQL.
Supported Triggers and Actions
Notis builds workflows that link Agentql to Botstar. A trigger fires from one place; an action lands in another.
Agentql triggers
Botstar actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
BotStar LiveChat onClose Callback
Registers a callback that runs when the chat window closes.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Bot
Creates a new bot.
Get BotStar Application IDs
Retrieves the application IDs used by the live chat widget.
Create Bot Attribute
Creates a bot attribute for shared, multilingual values.
Livechat boot
Reinitializes the live chat widget with updated data.
Create CMS Entity
Creates a content entity with optional custom fields.
Close BotStar Livechat Widget
Hides the live chat window.
Create Entity Fields
Adds fields to an existing content entity.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Agentql and Botstar
Connect any two apps with Notis in the middle.
Agentql and Botstar, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Botstar.