Thank customers by mail when Jira work is resolved
Close the loop with a physical thank-you letter tied to the Jira issue that records the completed work.
Trigger
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
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
A resolved ticket can close the task while the customer follow-up is still sitting on someone's to-do list.
- Tie customer mail to the issue update that marks work complete.
- Send only when the recipient and document details are supplied and approved.
- Keep a physical follow-up from becoming a separate manual task.
Setup
Build it in a few focused steps.
- 1Connect Jira and Docupost once in the Notis portal.
- 2Create an automation and give it a clear name.
- 3Tell Notis to send the approved thank-you PDF only when an issue update indicates resolution and includes a verified name and mailing address.
- 4Pick Jira Updated Issue as the trigger.
- 5Choose where run reports go, then test with one real example.
Questions about this workflow
Does this trigger on a Jira comment?
No. Jira Updated Issue does not fire on comment activity. It fires when an issue field changes, such as its status.
What if the issue has no mailing address?
The instruction should require verified recipient details and an approved PDF URL. Provide any missing information before relying on the workflow.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Docupost. A trigger fires from one place; an action lands in another.
Jira 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://...')
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
New Project
Triggered when a new project is added in Jira
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Connect any two apps with Notis in the middle.
Jira 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.