Turn Slack lead requests into Callingly calls
When a teammate shares a lead and asks for a call in Slack, create a Callingly outbound call using the details in the conversation.
Connect Slack to Callingly
When something happens in Slack, Notis takes the next step in Callingly. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Triggers when a new channel is created.
Do this · Action
Activates or deactivates a client account to control access.
Examples
Ways Notis can move work from Slack to Callingly
Create calls when a lead gets the green light
Use a designated Slack reaction on a lead message as the signal to create a Callingly outbound call, keeping approval and follow-up together.
Capture lead calls requested in Slack DMs
When a direct message asks for a lead call and includes contact details, create a Callingly outbound call record without relying on memory.
Look up a Callingly lead from a Slack question
When a Slack message asks for an existing lead's details and includes its Callingly lead ID, retrieve the record for an informed response.
Retrieve a Callingly call from its Slack reference
When a Slack message requests details about a specific call and includes its call ID, retrieve the Callingly call record.
Check Callingly call history from Slack
Respond to a Slack request for a call-history review by listing Callingly calls using the date range or other filters included in the message.
List Callingly leads for a Slack follow-up review
When a teammate requests a lead review in Slack with clear search criteria, retrieve matching Callingly leads for follow-up planning.
Check agent availability from Slack
Retrieve a specific Callingly agent's schedule when a Slack message asks whether that agent is available and includes the agent identifier.
Apply explicit agent schedule changes from Slack
When a Slack message clearly requests a Callingly agent availability update and gives specific times, update that agent's schedule.
Supported Triggers and Actions
Notis builds workflows that link Slack to Callingly. A trigger fires from one place; an action lands in another.
Slack triggers
Callingly actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
TriggerScheduled
Activate/Deactivate Client Account
Activates or deactivates a client account to control access.
ActionInstant
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
TriggerInstant
Create Agent
Creates a new agent.
ActionInstant
New Channel Created Trigger
Triggers when a new channel is created.
TriggerInstant
Create Outbound Call
Creates a call record and immediately places an outbound call, which may incur a cost.
ActionInstant
Channel Message Received
Triggers when a message is posted in a channel, excluding direct messages.
TriggerInstant
Create Client
Creates a new client account under your agency.
ActionInstant
Direct Message Received
Triggers when a new direct message, including a thread reply, is sent to a user.
TriggerInstant
Create Team
Creates a new team.
ActionInstant
Message Reaction Added
Triggers when a reaction is added to a message.
TriggerInstant
Create Webhook
Creates a webhook for real-time call or lead notifications.
ActionInstant
Message Reaction Removed
Triggers when a reaction is removed from a message.
TriggerInstant
Delete Agent
Permanently deletes an agent from an account.
ActionInstant
New Bot Message Received Trigger
Triggers when a bot posts a new message in a channel.
TriggerInstant
Delete Client
Deletes an existing client from your account.
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.
- 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
All12Manager5Telegram1Messages0WhatsApp2Email4Slack8
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.
Related pairs
More ways to connect Slack and Callingly
Connect any two apps with Notis in the middle.
Slack and Callingly, or any other combination from 1,500+ 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 Callingly.