Skip to main content

Products

Compliance Officer Service Expert-led compliance, end to end Compliance Portal Share security documents securely Document Management Draft, approve, and sign your policies Employee Portal Your whole team’s compliance, in one portal Access Review Monitor user access across all your systems AI Agents Run compliance from the tools you use Cookie Banner Consent that follows every visitor's law Device Agent Continuous security posture for every device Open-source platform Deploy Probo on your own infrastructure

Resources

Probo stories How teams get compliant with Probo Blog Ideas and guidance from the Probo team Guides & tools Practical compliance guides and free tools Love from Customers What customers say about working with Probo Changelog Latest product updates Download Get the Device Agent

Company

About The people and vision powering Probo Careers Join the team building Probo Brand assets Official logos and visual resources Security Review our security and compliance posture
Overview Understand Probo and its core concepts Product Explore Probo's GRC capabilities Developers Explore GraphQL, CLI, MCP, n8n, and webhooks Deployment Probo Cloud, self-hosting, and configuration

Explore

GitHub Explore our open-source compliance tools
Changelog
Documents

Pending signatures and approvals in n8n

Two new n8n operations list who still has to sign or approve a document, which document it is, and how long the request has been waiting. Build reminder workflows without stitching documents and versions together.

Pending signatures and approvals in n8n screenshot

The Probo n8n node has two new document operations: Get Pending Signatures and Get Pending Approvals.

Each item is one open request. It includes the person, with their email, the document, and how long the request has been waiting (waitingSince, waitingDuration, waitingSeconds). Before, you had to list documents, then versions, then signatures, and line them up yourself.

The obvious use is a reminder. Every Monday, send a Slack message to everyone who has had a policy to sign for more than a week. We run that exact workflow at Probo.

Heads up: in the same release, list operations return one n8n item per record instead of a single item holding an array. Workflows that read fields like $json.documents need to read each item directly.