Check an alerted signing session before you follow up
Get the IP reputation check and document context together when a signing session raises concern.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Get Document
Retrieves a document’s current state and details.
Why this helps
A security alert and its related signature request can live in separate tools, making it easy to miss context before acting.
- Bring the referenced document's current state into the alert review.
- Reduce tool switching when investigating a suspicious signing session.
- Keep the decision with a human before changing a signature request.
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 alert's IP with Abuselpdb and fetch the Docnify document identified in the request.
- 4Choose the webhook trigger and select where run reports should go.
- 5Test with a real example that includes an IP address and Docnify document ID.
Questions about this workflow
What starts this workflow?
An external service sends an HTTP request to the Notis webhook. Include the IP address to check and the Docnify document ID to retrieve.
Does this workflow change or pause the document?
No. It checks IP reputation and retrieves document details. It does not change signing access or document status.
What if the webhook does not include a document ID?
Notis cannot fetch a specific document without its ID. Include that ID in the incoming request.
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.