Connect Workday to Boloforms

When something happens in Workday, Notis takes the next step in Boloforms. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Workday to Boloforms

View example

Check BoloForms documents when an interview is scheduled

When Workday schedules an interview, review the BoloForms document list and report any interview packets, consent forms, or related documents that may need attention.

View example

Review BoloForms documents for every new job posting

When a job posting appears in Workday, list BoloForms documents and highlight recruiting templates or forms that may support the new role.

View example

Check document impact after a job posting changes

When a Workday job posting changes, review BoloForms documents and report forms or templates that may now be out of date.

View example

Add BoloForms document context to updated interview feedback

When interview feedback is submitted or updated, retrieve BoloForms documents and report any forms or records that provide useful context for the review.

View example

Cross-check BoloForms documents when a resume is added

When a new resume attachment appears on a Workday prospect, retrieve BoloForms documents and flag related recruiting paperwork for review.

View example

Review BoloForms documents after a prospect profile change

When a Workday prospect profile changes, list BoloForms documents and report records that may need review because of the updated candidate context.

View example

Review BoloForms documents when a leave record changes

When a Workday leave of absence changes, retrieve the BoloForms document list and report leave related records that may need attention.

View example

Check BoloForms documents for a newly created leave

When a new leave of absence is created in Workday, review BoloForms documents and report records that may support the leave process.

View example

Audit BoloForms documents after an absence balance change

When a worker's absence balance changes, retrieve BoloForms documents and report records that may explain or support the updated balance.

Supported Triggers and Actions

Notis builds workflows that link Workday to Boloforms. A trigger fires from one place; an action lands in another.

Workday triggers

Boloforms actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Get Documents List

Tool to retrieve a list of documents associated with the account. use when you need to list all documents.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

TriggerPolling

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.

TriggerPolling

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.

TriggerPolling

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.

TriggerPolling

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.

TriggerPolling

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.

TriggerPolling

Trigger Types

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.

New Notion pageStripe chargeCalendar event

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.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

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.

Row insertedValue > limitQuery match

Why AI automation

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.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

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:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

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.