Feedback Finds Its Home in Email
Client feedback arrives via a feedback form, API, or external tool. Instead of getting lost in Slack or a separate spreadsheet, Notis routes it directly into the matching Gmail thread as a reply.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Reply to email thread
Sends a reply within a specific gmail thread using the original thread's subject, requiring a valid `thread id` and correctly formatted email addresses. supports attachments via the `attachment` parameter with valid `s3key`, `mimetype`, and `name`.
Why this helps
External feedback arrives through multiple channels (forms, surveys, APIs) and gets scattered. You lose track of which feedback relates to which client or project conversation.
- Centralize all feedback in email, your source of truth
- Connect external data to the original conversation
- Reduce fragmentation across tools
- Build a complete record of client interactions
Setup
Build it in a few focused steps.
- 1Connect Gmail and get your Notis webhook URL.
- 2Configure your feedback form or external system to send data to that URL.
- 3Create an automation: 'When this webhook receives feedback, create a reply in the matching Gmail thread.'
- 4Map the webhook fields to email data (sender, content, etc.).
- 5Test by submitting feedback; you'll see it appear as a thread reply in Gmail.
Questions about this workflow
How does Notis match feedback to the right thread?
It looks for matching email addresses, client names, or keywords. You configure which fields Notis uses to find the thread.
What if there's no matching thread?
Notis can create a new email thread or archive the feedback separately. You choose the fallback behavior.
Can I notify the team when feedback arrives?
Yes. Notis can post a message in Slack or send a notification email in parallel.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Slack to Gmail. A trigger fires from one place; an action lands in another.
Slack triggers
Gmail actions
New Channel Created Trigger
Triggered when a new channel is created in Slack.
Modify email labels
Adds and/or removes specified gmail labels for a message; ensure `message id` and all `label ids` are valid (use 'listlabels' for custom label ids).
Channel Message Received
Triggered when a message is posted in a Slack channel (public, private, or multi-party IM). Does NOT match direct messages.
Create email draft
Creates a gmail email draft, supporting to/cc/bcc, subject, plain/html body (ensure `is html=true` for html), attachments, and threading.
Direct Message Received
Triggered when a new direct message (DM) is sent to a user in Slack. Catches all DMs across all DM channels.
Create label
Creates a new label with a unique name in the specified user's gmail account.
Message Reaction Added
Triggered when a reaction is added to a message in Slack. Supports optional filtering by channel and emoji name.
Delete Draft
Permanently deletes a specific gmail draft using its id; ensure the draft exists and the user has necessary permissions for the given `user id`.
Message Reaction Removed
Triggered when a reaction is removed from a message in Slack. Supports optional filtering by channel and emoji name.
Delete message
Permanently deletes a specific email message by its id from a gmail mailbox; for `user id`, use 'me' for the authenticated user or an email address to which the authenticated user has delegated access.
Reaction Added Trigger
DEPRECATED: use `SLACK_MESSAGE_REACTION_ADDED` instead. Triggered when a reaction is added to a message in Slack.
Fetch emails
Fetches a list of email messages from a gmail account, supporting filtering, pagination, and optional full content retrieval.
Reaction Removed Trigger
DEPRECATED: use `SLACK_MESSAGE_REACTION_REMOVED` instead. Triggered when a reaction is removed from a message.
Fetch message by message ID
Fetches a specific email message by its id, provided the `message id` exists and is accessible to the authenticated `user id`.
New Bot Message Received Trigger
DEPRECATED: use `SLACK_CHANNEL_MESSAGE_RECEIVED` with `is_bot_message=true` instead. Triggered when a new bot message is posted to a Slack channel.
Fetch Message by Thread ID
Retrieves messages from a gmail thread using its `thread id`, where the thread must be accessible by the specified `user id`.
Connect any two apps with Notis in the middle.
Not just Slack and Gmail. 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 Gmail.