Stop pending surveys when a Jira update calls for it
Keep survey outreach aligned with customer context by cancelling pending requests when an issue update indicates they should stop.
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
Delete Pending Survey Requests
Tool to remove all pending (scheduled but not yet sent) survey requests for a person. Use when you need to cancel all future surveys for a specific email address.
Why this helps
A customer can keep receiving scheduled surveys after their situation changes unless someone remembers to cancel them.
- Remove pending requests when issue context calls for a pause.
- Avoid searching Delighted manually for the customer's scheduled surveys.
- Report when contact details needed for cancellation are unavailable.
Setup
Build it in a few focused steps.
- 1Connect Jira and Delighted once in the Notis portal.
- 2Create an automation in the portal or tell Notis from any channel what outcome you want.
- 3In one instruction, describe which issue updates should cancel the customer's pending surveys and how to identify them.
- 4Pick Jira Updated Issue as the trigger and choose where run reports go.
- 5Test with one real issue and a person with pending survey requests.
Questions about this workflow
Does this unsubscribe the person from all future surveys?
No. This action deletes pending survey requests for a person. Use Delighted's unsubscribe action for a permanent email survey opt-out.
What if the Jira issue does not identify the person's email?
The action requires a person to be identified. Notis should report that the email is missing rather than guess.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Delighted. A trigger fires from one place; an action lands in another.
Jira triggers
Delighted actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Person to Autopilot Email
Tool to add a person to Autopilot or update their properties for email-based surveys. Use when you need to enroll a person in scheduled email surveys or update their custom properties.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Person to Autopilot SMS
Tool to add a person to Autopilot or update their properties for SMS-based surveys. Use when you need to schedule automated survey delivery via SMS.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Create or Update Person
Tool to create or update a person and schedule a survey email. Use when you need to add a new person to Delighted, update existing person details, or schedule a survey with custom properties for segmentation.
New Project
Triggered when a new project is added in Jira
Delete Pending Survey Requests
Tool to remove all pending (scheduled but not yet sent) survey requests for a person. Use when you need to cancel all future surveys for a specific email address.
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.
Delete Person
Tool to remove a person and all associated data from Delighted. Use when you need to permanently delete a person's information. Deletion includes surveys, responses, properties, Autopilot membership, survey history, and unsubscribe/bounce status.
Get Autopilot Email Configuration
Tool to retrieve the current Autopilot configuration for email distribution. Returns configuration details including whether Autopilot is active, survey frequency, and timestamps.
Get Autopilot SMS Configuration
Tool to retrieve the current Autopilot configuration for SMS distribution. Use when you need to check whether Autopilot is enabled, review survey frequency settings, or examine configuration timestamps for SMS surveys.
List Autopilot SMS Memberships
Tool to retrieve all Autopilot memberships for SMS distribution platform. Use when you need to list people enrolled in Autopilot SMS or filter by specific person details.
Connect any two apps with Notis in the middle.
Jira and Delighted, 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 Delighted.