Resend an approved signing request with security context
Make an approved resend easier to handle by checking the reported IP and acting on the confirmed Docnify document.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Resend Document
Resends a document for signing.
Why this helps
Resending is easy to forget after approval, while security context can slow down a straightforward follow-up.
- Keep the IP check and resend instruction in one workflow.
- Require an explicit approval signal before triggering another signing notification.
- Reduce manual follow-up on confirmed resend requests.
Setup
Build it in a few focused steps.
- 1Connect Abuselpdb and Docnify once in the Notis portal.
- 2Create an automation from Automations, New Automation, or tell Notis what outcome you want from a channel.
- 3In one instruction, ask Notis to check the supplied IP and resend the identified document only when the request explicitly marks the resend as approved.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test using a real approved resend request with an IP address and Docnify document ID.
Questions about this workflow
What starts the resend?
An external service sends an HTTP request to the Notis webhook. The request should include the document ID, IP address, and an explicit approval signal.
Does a favorable IP check automatically approve a resend?
No. The webhook must explicitly say the resend is approved. IP reputation is supporting context, not approval.
What if the IP check raises concern?
Have the instruction stop without resending and report the result for human review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Abuselpdb to Docnify. A trigger fires from one place; an action lands in another.
Abuselpdb triggers
Docnify actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Document Recipient
Adds a recipient to a document.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Document Fields
Adds fields to a document.
Delete Document
Permanently deletes a document.
Delete Document Field
Removes a field from a document.
Delete document recipient
Removes a recipient from a document and revokes their access.
Get Document
Retrieves a document’s current state and details.
Get Template
Retrieves details about a template.
List Documents
Lists documents in the account.
Connect any two apps with Notis in the middle.
Abuselpdb 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.