Connect Agile CRM to Botstar
When something happens in Agile CRM, 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 Agile CRM to Botstar
Review BotStar bots from an Agile CRM signal
Use an Agile CRM webhook to prompt a fresh BotStar bot inventory when your CRM process needs a current view.
Schedule a BotStar attribute review alongside CRM operations
Ask Notis to retrieve BotStar attributes on a schedule and report the fields your team may need to review.
Check BotStar CMS structures from an Agile CRM request
Use a Notis webhook to retrieve a BotStar bot's CMS entities and field configurations when CRM work prompts a content check.
Scan BotStar CMS items as part of a recurring content review
On a Notis schedule, retrieve BotStar CMS items so your recurring CRM operations review can surface content needing attention.
Fetch BotStar bot details for a CRM handoff
When an Agile CRM process sends a webhook, retrieve a specific BotStar bot's name and team details for a handoff report.
Run a recurring BotStar inventory check for CRM operations
Have Notis list your BotStar bots on a schedule and report the current inventory for a regular operations review.
Inspect a BotStar CMS entity for a CRM-driven request
Use a webhook to retrieve one BotStar CMS entity's field configuration when an Agile CRM process needs a closer look.
Review BotStar attribute values on a recurring CRM cadence
Schedule a recurring summary of BotStar attribute names, descriptions and values to help catch changes relevant to CRM operations.
Retrieve a BotStar CMS item for a CRM request
Start from a Notis webhook and fetch the full field values for a specific BotStar CMS item relevant to an Agile CRM process.
Supported Triggers and Actions
Notis builds workflows that link Agile CRM to Botstar. A trigger fires from one place; an action lands in another.
Agile CRM 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 Agile CRM and Botstar
Connect any two apps with Notis in the middle.
Agile CRM 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.