Connect Slack to Calendly
When something happens in Slack, Notis takes the next step in Calendly. 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 Slack to Calendly
Create a Calendly link for a prospect request in Slack
Turn a clear prospect request in a Slack channel into a reusable Calendly scheduling link, ready to share in the conversation.
Prepare a one-time Calendly link for an introduction
When a Slack DM asks you to make an introduction meeting, create a single-use Calendly link for that booking.
Create a tailored Calendly share for a team meeting request
When teammates discuss a meeting in Slack, create a Calendly share link with the event settings appropriate to that request.
Create a scheduling link when a meeting request is approved
Use a Slack reaction that signals approval to prompt Notis to create a Calendly scheduling link for the agreed meeting.
Check Calendly availability for a Slack meeting request
When a Slack channel message proposes a meeting, check available times for the relevant Calendly event type and date range.
Check open Calendly times for a meeting proposed by DM
Respond to a clear meeting proposal in Slack DM by checking Calendly's available slots for the requested window.
Review Calendly events when Slack starts planning a meeting
When a channel begins planning a meeting, retrieve relevant Calendly events for the named invitee or defined scope to help avoid duplicate coordination.
Find invitee details for a Calendly event mentioned in Slack
When a DM asks for attendee details on a specific Calendly event, list that event's invitees for a quick review.
Retrieve Calendly event details from a Slack reference
When a channel message asks about a specific scheduled meeting, retrieve the Calendly event details using its uuid.
Supported Triggers and Actions
Notis builds workflows that link Slack to Calendly. A trigger fires from one place; an action lands in another.
Slack triggers
Calendly actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Cancel event
Permanently cancels an existing, active scheduled event by its `uuid`, optionally providing a `reason`, which may trigger notifications to invitees.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create an invitee no-show
Marks an invitee, identified by their existing and valid uri, as a 'no show' for a scheduled event.
New Channel Created Trigger
Triggered when a new channel is created in Slack.
Create One-Off Event Type
Creates a temporary calendly one-off event type for unique meetings outside regular availability, requiring valid host/co-host uris, a future date/range for `date setting`, and a positive `duration`.
Channel Message Received
Triggered when a message is posted in a Slack channel (public, private, or multi-party IM). Does NOT match direct messages.
Create scheduling link
Create a single-use scheduling link. creates a scheduling link that can be used to book an event. the link allows invitees to schedule up to the specified maximum number of events. once the limit is reached, the link becomes inactive.
Direct Message Received
Triggered when a new direct message (DM) is sent to a user in Slack. Catches all DMs across all DM channels.
Create share
Creates a customizable, one-time share link for a calendly event type, allowing specific overrides to its settings (e.g., duration, availability, location) without altering the original event type.
Message Reaction Added
Triggered when a reaction is added to a message in Slack. Supports optional filtering by channel and emoji name.
Create single use scheduling link
Creates a one-time, single-use scheduling link for an active calendly event type, expiring after one booking.
Message Reaction Removed
Triggered when a reaction is removed from a message in Slack. Supports optional filtering by channel and emoji name.
Create webhook subscription
Creates a calendly webhook subscription to notify a specified `url` (which must be a publicly accessible https endpoint) for selected `events` within a given `organization` and `scope`.
Reaction Added Trigger
DEPRECATED: use `SLACK_MESSAGE_REACTION_ADDED` instead. Triggered when a reaction is added to a message in Slack.
Delete invitee data
Permanently removes all invitee data associated with the provided emails from past organization events, for data privacy compliance (requires enterprise subscription; deletion may take up to one week).
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 Slack and Calendly
Connect any two apps with Notis in the middle.
Slack and Calendly, 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 Calendly.