Connect Calendly to Slack

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

When this happens · Trigger

Fires when a contact is added to the organization’s contact list.

Do this · Action

Add an alias for an existing custom emoji.

Build an automation Browse examples

Examples

Ways Notis can move work from Calendly to Slack

Share new Calendly bookings in Slack

Post a concise Slack update when a Calendly booking arrives, so the team sees who is meeting and when.

Post Calendly cancellations to Slack

Share a Slack update when a Calendly meeting is cancelled so teammates can adjust plans promptly.

Share Calendly reschedules with the team

Post a Slack update when a meeting time changes, helping teammates spot the latest schedule information.

Get a daily Calendly meeting brief in Slack

Ask Notis to check upcoming Calendly meetings on a schedule and share a short daily overview in Slack.

Create Slack reminders for upcoming Calendly meetings

On a schedule, find near-term Calendly meetings and create Slack reminders using the available meeting times.

Set a Slack follow-up reminder after a Calendly booking

When a booking webhook arrives, create a Slack reminder for a follow-up if a usable due time is included.

Review next week's Calendly meeting load in Slack

Post a weekly overview of next week's Calendly meetings so you can spot a crowded schedule before it begins.

Post a meeting prep prompt for new Calendly bookings

When a booking arrives, post a Slack prep prompt with the meeting details available and any missing context to gather.

Supported Triggers and Actions

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

Calendly triggers

Slack actions

Recurring trigger

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

TriggerScheduled

Add an emoji alias

Add an alias for an existing custom emoji.

ActionInstant

Webhook trigger

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

TriggerInstant

Add a remote file

Add a reference to an external file for discovery and sharing.

ActionInstant

Contact Created

Fires when a contact is added to the organization’s contact list.

TriggerInstant

Add Enterprise user to workspace

Adds an Enterprise user to a workspace, with optional guest restrictions.

ActionInstant

Contact Deleted

Fires when a contact is removed; the event identifies the contact but includes no details.

TriggerInstant

Add a star to an item

Adds a star to a Slack item; it cannot be viewed or interacted with by end users.

ActionInstant

Contact Updated

Fires when a contact changes; omitted fields are cleared by the update.

TriggerInstant

Add call participants

ActionInstant

Event Type Created

Fires when a standard bookable meeting type is created, but not for one-off types.

TriggerInstant

Add emoji

Add a custom emoji to a workspace.

ActionInstant

Event Type Updated

Fires when any meeting type field changes; the event does not specify which field changed.

TriggerInstant

Add reaction to message

Adds an emoji reaction to a Slack message.

ActionInstant

Invitee Marked No-Show

Fires when a host marks an invitee absent after a meeting, including past meetings.

TriggerInstant

Search for channels in Enterprise organization

Searches for public or private channels in an Enterprise organization.

ActionInstant

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 schedule (recurring or one-time), and a change in one of your Notis databases.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,500+ 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

Scheduled triggers

Run a workflow on the clock, on a recurring schedule or once at a set date and time. Daily standups, hourly syncs, a one-off launch reminder: the workhorse of Notis.

Daily · 8:00Weekdays onlyOnce · Dec 13

Beta

Database triggers

Fire when a row in one of your Notis databases is added or edited, with optional filters on its properties. New lead added, status changed, value crosses a limit.

Row addedProperty editedValue > limit

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.