Route Customers Instantly: Webhook-Powered Owner Lookup
Customer issues arrive through various channels. This webhook-based workflow finds the right support owner in Slack and routes the issue immediately, reducing response time.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Find users
Find users in a slack workspace by any criteria - email, name, display name, or other text. includes optimized email lookup for exact email matches.
Why this helps
Customer issues land in email or support tools, but you have to manually hunt in Slack for the right person to handle it. Time gets wasted on routing.
- Automatically route customer issues to the right owner without manual lookup
- Reduce time-to-assignment and improve customer response time
- Keep customer issues organized in Slack with proper ownership
Setup
Build it in a few focused steps.
- 1Connect Jira and Slack to Notis (one-time).
- 2Create an automation with the prompt: 'When a webhook delivers a customer issue with a component or team name, find the Slack user who owns that component and post the issue details in that user's DM.'
- 3Select 'Webhook Trigger' and copy the webhook URL.
- 4Configure your support tool or CRM to send customer issues to this webhook URL.
- 5Test by sending a sample customer issue and verifying it lands in the right owner's DM.
Questions about this workflow
How do you know who owns a component?
Notis reads your Jira project configuration and user assignments. You can also specify a mapping in your prompt (e.g., 'Feature-X is owned by John, Feature-Y is owned by Sarah').
What if the owner isn't available?
Ask Notis to check Slack presence and find a backup: 'If the primary owner is away, DM the backup owner instead.'
Can the webhook also create a Jira issue?
Yes. Include in your prompt: 'Also create a Jira ticket for tracking.'
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.