Keep signed approval proof within reach
Make completed signing evidence easier to gather for your AI evaluation and governance reviews.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get Signed Document
Tool to download the signed document (signature proof) for a signature request. The action will: 1) Resolve the first documentId from the signature request details. 2) Try v4: GET /documents/{documentId}/signatures/PDF_WITH_SIGNATURES 3) Fallback v3: GET /v3/documents/{documentId}/signature-proof 4) Final fallback: GET /documents/{documentId}/file (original file)
Why this helps
Signed evidence often takes extra searching when review time arrives, disrupting focus and slowing down follow-up.
- Retrieves the signed proof for an identified completed request.
- Makes approval evidence easier to gather during periodic reviews.
- Keeps signing artifacts associated with the evaluation context.
Setup
Build it in a few focused steps.
- 1Connect Honeyhive and Ignisign to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to collect proof for completed approvals.
- 3Write one plain-language instruction identifying the completed Ignisign requests and asking Notis to retrieve their signed documents for the related Honeyhive review.
- 4Choose a recurring cron trigger and a run-report channel, then test with one real completed request.
Questions about this workflow
Does this retrieve the signed copy or the original file?
Ignisign first attempts to retrieve the PDF with signatures and uses fallback document retrieval paths if needed.
Can it find which requests are completed?
Provide the relevant request context or pair this review with the Ignisign request-list action in a separate workflow.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Honeyhive to Ignisign. A trigger fires from one place; an action lands in another.
Honeyhive triggers
Ignisign actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Ignisign API Authentication
Tool to authenticate an application over Ignisign API and retrieve a JWT. Use when obtaining a bearer token before making other API calls.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Cancel Signature Request
Tool to cancel a signature request. Use after identifying the signature request to abort.
Initialize Document
Tool to initialize a document for a signature request. Use when linking a new document to an existing signature request after creating that request.
Create Signer
Tool to create a new signer. Use when onboarding a signer to an application environment after selecting a signer profile.
Create Webhook Endpoint
Tool to create a new webhook endpoint for an application. Use after obtaining application ID and environment to register for event notifications.
Delete Document
Tool to delete a specific document by its ID. Use when you need to permanently remove a document after processing is complete.
Delete Ignisign Signature Request
Tool to delete a signature request. Use when you need to permanently remove a signature request by its ID.
Delete Signer
Tool to delete a signer. Use when you need to remove a signer from a specific application environment after confirming signer ID.
Connect any two apps with Notis in the middle.
Honeyhive and Ignisign, 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 Ignisign.