Get Boloforms document context for new Box Sign requests
A new Box Sign request can prompt a quick look through your Boloforms document list, helping keep signature work visible.
Trigger
New Sign Request Created
Triggers when a new Box sign request is created. This trigger monitors Box sign requests and fires when new sign requests are detected.
Action
Get Documents List
Tool to retrieve a list of documents associated with the account. use when you need to list all documents.
Why this helps
New signature requests can get lost when you have to remember to check another document system for related context.
- Automatically retrieve the available Boloforms document list when a Box Sign request appears.
- Give the team a concise review prompt in its chosen report channel.
- Call out when document-list information is insufficient to establish a relationship.
Setup
Build it in a few focused steps.
- 1Connect Box and Boloforms once in the Notis portal.
- 2Create an automation in the portal or tell Notis to create one, with a name and prompt to retrieve the Boloforms document list and summarize any useful context for a new Box Sign request.
- 3Pick the New Sign Request Created trigger.
- 4Choose where run reports should go, then test with one real new Box Sign request.
Questions about this workflow
Will this create a Boloforms signature request?
No. The available Boloforms action only retrieves a list of documents.
What if there is no clear related document?
The prompt can ask Notis to say that no match can be confirmed from the returned document list.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Box to Boloforms. A trigger fires from one place; an action lands in another.
Box triggers
Boloforms actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Documents List
Tool to retrieve a list of documents associated with the account. use when you need to list all documents.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Collaboration Details Changed
Triggers when a collaboration's details change (e.g., role, status, expiration). This trigger monitors a specific collaboration and detects when any meaningful field changes, such as role, status, expiration date, access type, or acknowledgment status.
Comment Changed
Triggers when a comment's content or details change in Box. This trigger monitors a specific Box comment and detects when any meaningful field changes, such as message text edits, tagged message changes, or modification timestamp updates.
New File Comment Added
Triggers when a new comment is added to a file in Box. This trigger monitors a specific Box file and fires when new comments are detected.
File Metadata Changed
Triggers when a file's metadata or properties change in Box. This trigger monitors a specific Box file and fires when changes are detected in key fields like name, description, size, modification time, parent folder, or status.
File Shared Link Changed
Triggers when a file's shared link settings change in Box. This trigger monitors a specific Box file's shared link and fires when changes are detected in the shared link configuration, such as access level, permissions, password protection, expiration date, or vanity URL.
New File Version Uploaded
Triggers when a new file version is uploaded to a file in Box. This trigger monitors a specific Box file and fires when new versions are detected.
Connect any two apps with Notis in the middle.
Box 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.