Track Box Sign Request Status in Linear
When a Box Sign request moves to 'signed' or someone rejects it, Notis posts the update to the related Linear issue so your team is kept in the loop.
Trigger
Box Sign Request Status Changed
Fires when a Box Sign request’s status or key details change.
Action
Create a comment
Add a comment to an issue; this shared workspace change cannot be undone.
Why this helps
Sign requests are completed or rejected in Box but your team doesn't find out until they follow up, wasting time.
- Team is notified immediately when signatures are complete
- Rejections are flagged instantly so you can re-send
- Clear status trail of signature workflows in Linear
- Reduced follow-up needed to check signature status
Setup
Build it in a few focused steps.
- 1Connect Box and Linear to Notis.
- 2Create an automation named 'Box Sign status updates Linear.'
- 3Set the prompt to 'When a Box Sign request status changes (signed, rejected, pending), post an update to the related Linear issue with the new status.'
- 4Use 'Box Sign Request Status Changed' as your trigger.
- 5Pick your notification channel.
- 6Test by completing or rejecting a Box Sign request and confirming the update posts.
Questions about this workflow
Can I automatically close the Linear issue when a document is signed?
Yes. Tell Notis 'Mark the Linear issue Done when the document is signed' and it will auto-close.
What if someone rejects the document?
Notis posts the rejection. You can tell it to flag rejections as 'blocked' so they stand out.
Does it show who signed or rejected?
Yes. The status update includes the signer's name and date.
When this happens · Trigger
Fires when a Box Sign request’s status or key details change.
Do this · Action
Add a comment to an issue; this shared workspace change cannot be undone.
Supported Triggers and Actions
Notis builds workflows that link Box to Linear. A trigger fires from one place; an action lands in another.
Box triggers
Linear actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Archive issue
Archives a Linear issue while preserving its data for future reference.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create a comment
Add a comment to an issue; this shared workspace change cannot be undone.
Collaboration Details Changed
Fires when a Box collaboration’s details change.
Archive Project
Confirm the project name before archiving, especially in bulk; it leaves active views but can be unarchived later.
Comment Changed
Fires when a Box comment’s content or details change.
Create linear issue
Creates an issue in a specified Linear team with the supplied details.
New File Comment Added
Fires when a new comment is added to a Box file.
Archive Project Update
Hides a project update from active views while keeping its data; it is irreversible only until it is unarchived.
Conditions and details
The update is archived, not permanently deleted: it is hidden from the default and active views and its data is preserved. It can be unarchived later; the action is irreversible only in the sense that the update stays hidden until it is explicitly unarchived.
File Metadata Changed
Fires when a Box file’s metadata or properties change.
Get create issue default params
Retrieve a team's default issue estimate and workflow state for new issue forms.
File Shared Link Changed
Fires when a Box file’s shared link settings change.
Create attachment
Creates an attachment and associates it with an existing issue.
New File Version Uploaded
Fires when a new version is uploaded to a Box file.
Create a label
Creates a label for a Linear team or returns an existing label with the exact same name.
Connect any two apps with Notis in the middle.
Box and Linear, or any other combination from 1,600+ 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 Linear.