Connect Workday to Botstar
When something happens in Workday, 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 Workday to Botstar
Open BotStar for new interview preparation
When Workday schedules an interview, open BotStar so the hiring team can start a focused preparation chat.
Update BotStar with submitted interview feedback
When interview feedback changes in Workday, update the active BotStar session with the latest review context.
Open BotStar for a job posting change review
When a Workday job posting changes, open BotStar for a quick review of impact, next steps, and owner follow-up.
Open BotStar for a new job posting launch
When Workday publishes a new job posting, open BotStar with a launch checklist for recruiting and support teams.
Update BotStar when a job questionnaire changes
When a Workday candidate questionnaire changes, update BotStar with a concise review of the new questions.
Update BotStar after a prospect profile change
When a Workday prospect profile changes, refresh the BotStar session with the latest recruiting context.
Open BotStar for a new resume review
When a Workday prospect receives a new resume attachment, open BotStar with a structured review prompt.
Update BotStar when a leave record changes
When a Workday leave record changes, update BotStar with the current status and follow-up context.
Open BotStar for new leave coordination
When Workday creates a leave of absence, open BotStar with a coordination checklist for the responsible team.
Supported Triggers and Actions
Notis builds workflows that link Workday to Botstar. A trigger fires from one place; an action lands in another.
Workday triggers
Botstar actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
BotStar LiveChat onClose Callback
Tool to register a callback when the chat window is closed. use after the widget is initialized. example prompt: "register an onclose handler that logs 'goodbye!' to the console."
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get BotStar Application IDs
Tool to retrieve the botstar application id (`appid`). use when initializing or reinitializing the live chat widget.
Absence Balance Changed
Triggers when a worker's absence balance changes. This trigger monitors a specific worker's absence plan balance and detects any changes to the balance details including quantity available, effective date, position, or other related fields. Uses snapshot-based diffing to detect meaningful changes.
Livechat boot
Tool to reinitialize the live chat widget with provided data. use after initial load to reset or update widget configuration.
Balance Details Changed
Triggers when details of a specific balance change (quantity, accruals, adjustments, etc.). This trigger monitors a specific worker's absence plan balance and detects any changes to the balance details including quantity available, effective date, position, or other related fields. Uses snapshot-based diffing to detect meaningful field changes.
Close BotStar Livechat Widget
Tool to hide the live chat window. use when the chat widget is configured in livechat or popup mode.
Interview Feedback Submitted or Updated
Triggers when interview feedback is submitted or updated for a specific interview. This trigger monitors a specific interview and fires when new feedback entries are detected or existing feedback is modified.
Livechat on open
Tool to register a callback when the chat window is opened. use after widget initialization.
Job Posting Changed
Triggers when a specific job posting's details change (title, status, posting dates, location, etc.). This trigger monitors a single job posting and fires when any of its fields are modified.
Livechat open
Tool to show the live chat window. use after the widget has been bootstrapped with botstarapi('boot') to programmatically open the chat window (mode must be 'livechat' or 'popup').
Job Posting Questionnaire Changed
Triggers when a job posting's candidate questionnaire is added or changed. This trigger monitors a specific job posting's questionnaires and detects any changes including additions, removals, or modifications to questionnaires and questions. Uses snapshot-based diffing to detect meaningful changes.
Livechat update
Tool to update user details on the current live chat session. use when you need to modify user profile attributes during an active conversation.
New Absence Balance
Triggers when a new absence balance record becomes available for a worker. This trigger monitors a specific worker's absence balances and detects when new balance records appear (e.g., a new plan/bucket becomes available). Uses snapshot-based diffing to compare balance record IDs between polls.
Get BotStar Webview Parameter
Tool to retrieve a parameter value passed from the botstar chatbot to the webview. use inside onchatbotready after your page loads in modal mode with bs:input meta tags.
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 Workday and Botstar
Connect any two apps with Notis in the middle.
Workday 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.