Never Lose External Feedback: Bug Report Reminder Workflow
External bug reports from customers often get buried. This webhook-based workflow captures incoming reports (via email, form, or API) and creates a Slack reminder so your team can act immediately.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create a reminder
Creates a slack reminder with specified text and time; time accepts unix timestamps, seconds from now, or natural language (e.g., 'in 15 minutes', 'every thursday at 2pm').
Why this helps
Bug reports arrive from various channels (email, support forms, social media). Without coordination, important bugs get lost in the noise.
- Centralize external feedback into Slack reminders without manual data entry
- Ensure critical bugs get immediate visibility and action
- Create an audit trail of external issues in Slack history
Setup
Build it in a few focused steps.
- 1Connect your Jira and Slack workspaces to Notis (one-time).
- 2Create an automation with the prompt: 'When you receive an HTTP POST to my automation webhook with a bug report, create a Slack reminder with the bug title, description, and reporter email.'
- 3Select 'Webhook Trigger' and copy the webhook URL provided.
- 4Send that URL to your support team, form provider, or customer feedback system.
- 5Test by sending a sample bug report to the webhook URL and verifying the Slack reminder appears.
Questions about this workflow
How do I integrate the webhook into my support tool?
Paste the Notis webhook URL into your tool's outgoing webhook settings. Most platforms (Zapier, support tools, form builders) support this natively.
Can the webhook also create a Jira issue?
Yes. Include in your prompt: 'Also create a Jira ticket with the same details for tracking.'
Is the webhook secure?
Notis webhooks use HTTPS and can accept custom authentication headers. Ask for security details in your automation setup.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Slack. A trigger fires from one place; an action lands in another.
Jira triggers
Slack actions
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Set snooze duration
Deprecated: turns on do not disturb mode for the current user, or changes its duration. use `set dnd duration` instead.
New Project
Triggered when a new project is added in Jira
Add a custom emoji to a Slack team
Deprecated: adds a custom emoji to a slack workspace given a unique name and an image url. use `add emoji` instead.
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.
Add an emoji alias
Adds an alias for an existing custom emoji in a slack enterprise grid organization.
Add a remote file
Adds a reference to an external file (e.g., google drive, dropbox) to slack for discovery and sharing, requiring a unique `external id` and an `external url` accessible by slack.
Add a star to an item
Stars a channel, file, file comment, or a specific message in slack.
Add call participants
Registers new participants added to a slack call.
Add emoji
Adds a custom emoji to a slack workspace given a unique name and an image url; subject to workspace emoji limits.
Add reaction to message
Adds a specified emoji reaction to an existing message in a slack channel, identified by its timestamp; does not remove or retrieve reactions.
Connect any two apps with Notis in the middle.
Not just Jira and Slack. Any combination from 985+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Slack.