Connect Workday to Cults

When something happens in Workday, Notis takes the next step in Cults. 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 Cults

View example

Turn a new job posting into a Cults role model pack

When a Workday job posting opens, find relevant Cults models for the role and organize a review-ready collection.

View example

Refresh Cults references when a job posting changes

When a Workday posting changes, compare its updated requirements with the existing Cults reference set and suggest updates.

View example

Use interview feedback to find better Cults portfolio examples

When interview feedback is submitted or updated, search Cults for models that address the capabilities the panel discussed.

View example

Prepare a Cults visual brief for every new interview

When Workday schedules an interview, assemble a Cults search brief and relevant models for the interview team.

View example

Match new prospect resumes with Cults skill references

When a resume is added to a Workday prospect, extract stated skills and find relevant Cults models for structured review.

View example

Update a Cults shortlist when a prospect profile changes

When a Workday prospect profile changes, reassess the relevant Cults models and refresh the review shortlist.

View example

Build a Cults coverage resource pack when leave changes

When a Workday leave record changes, find and organize Cults resources that help the team cover affected creative work.

View example

Create a Cults handoff collection for new leave

When a new Workday leave is created, gather Cults models that document active work and likely coverage needs.

View example

Use absence balance changes to refresh Cults planning resources

When a Workday absence balance changes, update a Cults collection of planning models for upcoming team capacity reviews.

Supported Triggers and Actions

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

Workday triggers

Cults actions

Recurring trigger

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

TriggerScheduled

Get Approved Origins

Tool to retrieve approved sharing origins from Cults. Use when you need to infer the allowed domains for the Share on Create action. Use after authenticating with Cults.

ActionInstant

Webhook trigger

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

TriggerInstant

Cults GraphQL POST

Tool to execute a GraphQL operation against the Cults API. Use when you need to fetch or mutate data via the Cults GraphQL endpoint.

ActionInstant

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

Share on Create (FR)

Tool to prefill a new creation on Cults (French locale). Use when you need to generate a one-click share link for a 3D file. Use after your site is approved by Cults.

ActionInstant

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.