Send customer commitments without losing them in your task list
Capture the promise in Linear, then let Notis handle the physical follow-through once the recipient and letter are confirmed.
Trigger
Issue Created Trigger
Triggered when a new issue is created.
Action
Send Letter
Tool to send a letter via u.s. mail with specified recipient, sender, and pdf. use after confirming recipient and document details. example: send letter(to name='john doe', to address='123 main st, ...', file url='https://...')
Why this helps
Customer promises can disappear among competing issues and follow-ups, leaving founders to remember a separate mailing task.
- Keeps a physical follow-up tied to the issue where the commitment was recorded.
- Avoids re-reading the whole backlog to find pending mail tasks.
- Requires confirmation of recipient and document details before sending.
Setup
Build it in a few focused steps.
- 1Connect Linear and Docupost once through the Notis portal.
- 2Create an automation in the portal, or ask Notis conversationally to mail a customer commitment letter when its Linear issue is created.
- 3Write one plain-language instruction telling Notis how to identify the commitment and to send only after recipient and document details are confirmed.
- 4Select the Linear Issue Created trigger and choose where Notis should report runs.
- 5Test with one real issue and verify the recipient and letter before the mailing is sent.
Questions about this workflow
Will every new Linear issue cause a letter to be sent?
No. The instruction should tell Notis to act only on issues that represent a customer commitment, and sending requires confirmed recipient and document details.
Can Notis fill in missing address details?
The instruction can ask Notis to check available context, but the address and document must be confirmed before sending.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Docupost. A trigger fires from one place; an action lands in another.
Linear triggers
Docupost actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Send Letter
Tool to send a letter via u.s. mail with specified recipient, sender, and pdf. use after confirming recipient and document details. example: send letter(to name='john doe', to address='123 main st, ...', file url='https://...')
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Send Postcard
Tool to send a postcard via u.s. mail with specified recipient, sender, and front/back images. use after confirming recipient addresses and design urls. example: send postcard(to name='john doe', ..., front image='https://...', back image='https://...')
Comment Received Trigger
Triggered when a comment is received.
Issue Created Trigger
Triggered when a new issue is created.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Connect any two apps with Notis in the middle.
Linear and Docupost, 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 Docupost.