Give pending email follow-ups a regular review point
Use a recurring check-in to bring open follow-ups into view, so important replies do not depend on remembering to revisit the inbox.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Post message to channel
Sends a message to a specified discord channel (text, embeds, stickers, components, attachments); requires `send messages` permission and one of `content`, `embeds`, `sticker ids`, or `attachments`.
Why this helps
Messages that need a later reply are easy to forget once they leave the top of the inbox.
- Create a recurring team review point for pending replies.
- Put follow-up information in a channel the team can revisit.
- Make missing inbox history visible rather than silently assumed.
Setup
Build it in a few focused steps.
- 1Connect Agent mail and Discordbot once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to post the pending follow-up information available to it, with message context and due dates when known, and identify gaps that need manual review.
- 4Choose a recurring schedule as the trigger and select where run reports should go.
- 5Test with one real example and confirm Notis has access to the follow-up list or history it needs.
Questions about this workflow
Can this find pending email in the Agent mail inbox automatically?
Only if the information or inbox history needed for that review is available to Notis. Supply the pending list or make the relevant history accessible; a schedule alone does not provide it.
Can it decide which replies are overdue?
It needs dates or a follow-up rule supplied or available to it. Ask Notis to flag missing dates rather than infer them.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Agent mail to Discordbot. A trigger fires from one place; an action lands in another.
Agent mail triggers
Discordbot actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add recipient to group channel
Adds a user to a discord group direct message (dm) channel.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Update guild member information
Adds a user (who is not already a member) to a guild using their `access token` (which must have `guilds.join` scope), optionally setting nickname, roles, mute/deaf status, or flags.
New Email Received
Trigger for new emails in an AgentMail inbox
Assign role to guild member
Assigns a role to a guild member, provided the bot has 'manage roles' permission in the guild and the role to be assigned is hierarchically lower than the bot's highest role.
Add reaction to message
Adds an emoji reaction from the authenticated user/bot to a specific message in a discord channel; does not return information about existing reactions.
Add or update thread member
Adds a user to a specific, unarchived thread; the user must have access to the thread's parent channel, and for private threads, the bot must already be a member.
Modify guild ban settings
Permanently bans a user from a discord guild, optionally deleting their recent messages (specify deletion period in seconds or days, not both).
Bulk ban users in guild with message deletion option
Bans up to 200 users from a discord guild, optionally deleting their recent messages; the bot must have 'ban members' permission in the guild, and this action is irreversible.
Bulk delete messages in channel
Atomically bulk deletes messages in a discord channel for moderation or maintenance; deletion may not be instantaneous and messages are unrecoverable.
Connect any two apps with Notis in the middle.
Agent mail and Discordbot, 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 Discordbot.