Find the right Dailybot user for Outlook requests
Resolve names quickly before a request gets sent to the wrong person.
Trigger
New Outlook Message
Triggered when a new message is received in the Outlook mailbox.
Action
Get All Users
This tool retrieves a list of all users within the organization from dailybot. it doesn't require any input parameters other than authentication. the returned json contains user details including uuid, active status, full name, and organizational data.
Why this helps
Email names and team directory names do not always match, causing routing errors.
- Reduce routing mistakes
- Resolve ambiguous names
- Speed up handoffs
Setup
Build it in a few focused steps.
- 1Connect Outlook and Dailybot once in Notis.
- 2Create an automation named Outlook Attendee Lookup Routing.
- 3Tell Notis to extract named teammates from each request, look them up in Dailybot, and report the matching users and uncertainties.
- 4Pick New Outlook Message as the trigger and choose a report destination.
- 5Test with one real request naming a teammate.
Questions about this workflow
What happens when no match exists?
Notis reports that no Dailybot user was found so you can resolve it manually.
Does this send a message to the matched user?
This workflow performs the lookup and report. Add a separate instruction if you want a message sent.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Outlook to Dailybot. A trigger fires from one place; an action lands in another.
Outlook triggers
Dailybot actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Find User by UUID
This tool allows you to find and retrieve information about a specific user in dailybot. it uses the provided user uuid to lookup the user and returns detailed information including the user's uuid, full name, image, username, occupation, birth date, chat platform data, and organization details.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Find Workflow by Name
This tool allows users to find a specific workflow within dailybot by providing the workflow name. it returns detailed information including the workflow id, workflow name, workflow status, workflow type, created at, and updated at. it is especially useful to locate a workflow before running or modifying it.
New Contact Added
Triggered when a new contact is added in the Outlook contacts.
Get All Users
This tool retrieves a list of all users within the organization from dailybot. it doesn't require any input parameters other than authentication. the returned json contains user details including uuid, active status, full name, and organizational data.
Calendar Event Changes
Triggered when a new calendar event occurs (created, updated, or deleted) in the Outlook calendar.
Get Workflows List
This tool retrieves a list of all workflows that the authenticated user has access to in dailybot. it can be executed independently with only the authentication required, and it supports optional pagination parameters (page, per page) to refine the response.
New Calendar Event
Triggered when a new calendar event is created in the Outlook calendar.
Give Kudos to Users
This tool allows giving kudos to one or multiple users in dailybot. kudos can be given either on behalf of dailybot or the api key owner.
New Outlook Message
Triggered when a new message is received in the Outlook mailbox.
Send Message
This tool allows sending a message through dailybot to either specific users or channels/rooms. the message can include markdown formatting.
New Sent Message
Triggered when a new message is sent from the Outlook mailbox.
Connect any two apps with Notis in the middle.
Outlook and Dailybot, 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 Dailybot.