Connect Slackbot to Docnify
When something happens in Slackbot, Notis takes the next step in Docnify. 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 Slackbot to Docnify
Turn channel requests into a signing status check
When a Slack channel asks about a document, list matching Docnify documents and summarize their current signing status.
Fetch document details from a Slack DM
When you DM the Slackbot with a Docnify document ID, retrieve the document metadata and current state.
Send an approved document for signature
When a Slack channel confirms a document is ready, send the specified Docnify document for signing after checking its ID and recipients.
Resend a stalled signature request
When you DM a document ID and resend request, verify the Docnify document and resend its signing notification.
Update signer details after a Slack reaction
When an approved reaction is added to a Slack message containing a correction, update the confirmed Docnify recipient details.
Add a late signer to a document
When a Slack channel identifies an additional signer, add that recipient to the confirmed Docnify document.
Add required fields before sending
When a Slack review message identifies missing signature fields, create the requested fields on the confirmed Docnify document.
Update signature field metadata
When a Slack DM requests a label or requirement correction, update the specified Docnify document fields after verification.
Surface templates when a project channel starts
When a new Slack channel is created, list available Docnify templates so the team can choose a starting document quickly.
Supported Triggers and Actions
Notis builds workflows that link Slackbot to Docnify. A trigger fires from one place; an action lands in another.
Slackbot triggers
Docnify actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Document Recipient
Tool to add a recipient to a document. Use after confirming the document's ID. Optionally specify signing order and authentication options.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Document Fields
Tool to create one or more fields on a document. Use after fetching a document to add fields before sending.
New Channel Created Trigger
Triggered when a new channel is created in Slack.
Delete Document
Tool to delete a specific document by its ID. Use when you have confirmed the document should be permanently removed.
Channel Message Received
Triggered when a message is posted in a Slack channel (public, private, or multi-party IM). Does NOT match direct messages.
Delete Document Field
Tool to delete a field from a document. Use when you need to remove a specific field from an existing document.
Direct Message Received
Triggered when a new direct message (DM) is sent to a user in Slack. Catches all DMs across all DM channels.
Delete document recipient
Tool to remove a recipient from a document. Use after verifying document and recipient IDs to revoke access.
Message Reaction Added
Triggered when a reaction is added to a message in Slack. Supports optional filtering by channel and emoji name.
Get Document
Tool to fetch a specific document by its ID. Use when you need to view a document's current state and metadata.
Message Reaction Removed
Triggered when a reaction is removed from a message in Slack. Supports optional filtering by channel and emoji name.
Get Template
Tool to fetch a specific template by its ID. Use to view a template's details and metadata.
Reaction Added Trigger
DEPRECATED: use `SLACK_MESSAGE_REACTION_ADDED` instead. Triggered when a reaction is added to a message in Slack.
List Documents
Tool to list documents in the Docnify account.
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 Slackbot and Docnify
Connect any two apps with Notis in the middle.
Slackbot and Docnify, 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 Docnify.