Connect Workday to Bigmailer

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

View example

Create a Bigmailer campaign for every new Workday job posting

Turn each new Workday job posting into a ready-to-review Bigmailer transactional campaign for recruiting outreach.

View example

Create a candidate update campaign when a Workday posting changes

Convert meaningful job posting changes into a Bigmailer update campaign for candidates and recruiting partners.

View example

Create an interview preparation campaign when an interview is scheduled

Create a Bigmailer transactional campaign with interview details and preparation guidance when Workday schedules an interview.

View example

Create a follow-up campaign from submitted interview feedback

Use new or updated Workday interview feedback to create a Bigmailer campaign for next-step communication.

View example

Create a prospect nurture campaign after a Workday profile change

Turn a meaningful prospect profile update into a Bigmailer campaign for recruiting nurture or outreach.

View example

Create a recruiter follow-up campaign when a resume is added

Create a Bigmailer campaign for recruiter follow-up when Workday detects a new prospect resume attachment.

View example

Create a team communication campaign when a leave record changes

Create a Bigmailer transactional campaign for approved internal communication when a Workday leave of absence changes.

View example

Create an onboarding communication campaign for a new leave record

Create a Bigmailer campaign for approved leave process communication when a new Workday leave record is created.

View example

Create an employee reminder campaign after an absence balance change

Create a Bigmailer campaign that explains an absence balance change using the Workday event and your approved policy language.

Supported Triggers and Actions

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

Workday triggers

Bigmailer actions

Recurring trigger

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

TriggerScheduled

Create Transactional Campaign

This tool creates a new transactional campaign within a specified brand in bigmailer. it allows users to programmatically create new transactional campaigns by using the provided parameters (brandid, name, subject, fromname, fromemail, htmlcontent, etc.). the api endpoint returns details such as campaignid, name, status, and created at when a campaign is successfully created.

ActionInstant

Webhook trigger

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

TriggerInstant

Get User Information

This tool retrieves information about the authenticated user in bigmailer using the get /me endpoint. it requires only authentication and no additional parameters, making it ideal for verifying api connectivity and retrieving essential user details.

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

List All Brands

This tool retrieves a list of all brands associated with the authenticated bigmailer account. it allows users to view and manage their brands. the operation is executed via a simple get request to the /brands endpoint and requires proper authentication using the x-api-key header. the response is a json array containing information such as brand id, brand name, and other related details.

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.