Follow up on a pending signature from Slack
Move from a clear follow-up request to a verified resend without losing the context of why it is needed.
Trigger
Channel Message Received
Triggered when a message is posted in a Slack channel (public, private, or multi-party IM). Does NOT match direct messages.
Action
Resend Document
Tool to resend a document for signing. Use after verifying the document ID to re-trigger signing notifications.
Why this helps
A request to follow up on a pending signature can become one more item to remember after the discussion moves on.
- Turns an explicit follow-up request into a focused next step.
- Keeps the request tied to its Slack context.
- Requires the document to be checked before resending.
Setup
Build it in a few focused steps.
- 1Connect Slack and Docnify to Notis once through the portal.
- 2Create the automation in the portal or ask Notis conversationally.
- 3Describe in one instruction how to recognize a follow-up request and verify the correct Docnify document before resending.
- 4Select Slack Channel Message Received as the trigger and choose a report channel.
- 5Test with a real pending-signature request and confirm the intended document is resent.
Questions about this workflow
Will this resend on every mention of a document?
No. The prompt should specify a clear follow-up request and require document verification.
Can it follow a signer without resending?
This workflow uses Docnify's resend action; it should only be used when resending is the intended next step.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Slack to Docnify. A trigger fires from one place; an action lands in another.
Slack 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.
Connect any two apps with Notis in the middle.
Slack 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.