Find stale paperwork tied to campaign outputs
Make aging paperwork visible before it slows the next campaign step.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get Documents List
Lists documents in a workspace.
Why this helps
Old documents can remain unnoticed when no one has a regular review tied to production activity.
- Surface aging items for a human decision
- Connect review to actual production outputs
- Keep attention on records that may be blocking work
Setup
Build it in a few focused steps.
- 1Connect Adrapid and Boloforms in Notis.
- 2Create an instruction to review the Boloforms document list against a supplied Adrapid output export containing output identifiers and relevant dates.
- 3Choose a Notis cron trigger and provide the source export before each scheduled run.
- 4Choose where reports go and test with one real campaign period.
Questions about this workflow
Can Notis know whether a document is truly stale?
Only if the supplied Adrapid payload includes dates or status context and you define the review rule in the instruction.
Will it archive or update documents?
No. The available Boloforms action only lists documents.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Adrapid to Boloforms. A trigger fires from one place; an action lands in another.
Adrapid triggers
Boloforms actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Documents List
Lists documents in a workspace.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Connect any two apps with Notis in the middle.
Adrapid and Boloforms, 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 Boloforms.