Outlook Integration
Outlook is the email and calendar backbone of Microsoft 365 workplaces. The Outlook node in NoClick uses the Microsoft Graph API to cover mail, calendar events, contacts, folders, and inbox rules in one place. It lets a workflow not only send and read email but also schedule meetings and find open time on a calendar.
What you can automate with Outlook
Pick one to start building it.
Outlook Operations
Triggers8
Email Message20
Mail Folder6
Mailbox2
Inbox Rule5
Message Category5
Calendar Event14
Calendar26
Room1
Contact5
Contact Folder5
Templates using Outlook
Outlook Lead Qualification Agent
Reads every email in the shared Outlook mailbox, scores it on the criteria you wrote, records the contact and a written note in HubSpot, and posts to Teams only when a lead is worth a call. A shared sales mailbox is mostly supplier pitches, invoices and recruiters, with two or three real buyers hidden in the pile. This agent reads all of it, scores each email against criteria you write in plain English, and records what it found in HubSpot: the contact, and a note a rep can read on the way to the call. Only the ones that passed reach Teams, which is what keeps that channel worth having notifications on. ## What people use it for - **Microsoft shop, no new tools** - Your sellers already live in Outlook and Teams, so nothing has to move. The agent reads the mailbox you have and posts where the team already looks. - **Every lead reaches the CRM** - The buyer is matched to an existing HubSpot record or added as a new one, with the note attached, the day their email arrives. Nobody has to remember to log anything after the call. - **Weak leads stop being noise** - Unqualified mail gets its note and goes no further. A channel that only fires for real buyers is a channel people still read in month three. - **Overnight mail already scored** - An email landing at 23:40 on Friday is read, scored and filed before Monday standup. The week starts from a scored list rather than an unopened mailbox. ## Before you fork **What has to be connected before the first run?** Three connections: the Outlook or Microsoft 365 mailbox your inbound mail lands in, a HubSpot account allowed to search and create contacts and write notes, and the Teams channel that should receive alerts. The writing you do is short, your bar for a real lead and the summary style your reps prefer. Setup collects both, and the staged test runs show you a scored email before a live one ever arrives. **Can it email a prospect or change my HubSpot data?** There is no reply tool wired to it, so reaching a sender is not something it can do. Inside HubSpot it looks the address up before writing and only adds a contact when there was no match, and it appends notes rather than editing properties, deals or lifecycle stages. Everything it leaves behind is a note or a record you can delete in one click. **What does it cost to run?** You pay for one short run per email that reaches the trigger, so the bill follows inbound volume rather than team size. A mailbox that also collects newsletters and invoices should point the trigger at a filtered Outlook folder, which keeps that traffic from starting runs at all. A lead that fails your bar ends at its HubSpot note and costs nothing after that.
Outlook Support Agent
Turns every support email in Outlook into a reply draft grounded in your Notion pages and your policies, ready for a person to read and send. Support email is slow not because the answers are hard, but because someone has to go and find them first. This agent reads the whole conversation, searches your Notion knowledge base, and leaves the answer waiting in Outlook as a reply draft. You change what you want to change and hit send yourself, so nothing reaches a customer that a person did not read first. ## What people use it for - **Cover the unstaffed hours** - An email landing at 02:00 already has a drafted answer attached when the first person opens the inbox. Someone else did the reading and the page hunting overnight. - **One answer, whoever sends it** - Drafts are built from your playbook and your Notion pages, so the fifth reply about the same policy matches the first four no matter who is on the inbox. - **New hires start grounded** - Week one is editing a drafted answer rather than guessing at policy. The drafts double as training in how your team writes to customers. - **Nothing leaves without a human** - The agent has a draft tool and no send tool. The worst case is a draft you disagree with, and anything it could not settle carries a NEEDS A HUMAN line on top. ## Before you fork **What do I need in place before it starts drafting?** Two connections: the Outlook or Microsoft 365 mailbox your support mail arrives in, and Notion with the relevant pages shared. After that, the playbook and the knowledge base notes are what actually decide draft quality, so spend your time there. A thin knowledge base will not break anything, it just means more drafts that say the team is looking into it. **Could it ever send an email to a customer?** No. Drafting is the only mail ability it has, so a draft you dislike sitting in Outlook is the worst outcome available to it. Anything it could not ground fully is marked NEEDS A HUMAN on the first line, before the greeting. Money, cancellations, account access and anything legal or security related get an acknowledgement and nothing else, because those are yours to decide. **How do I keep the drafts sounding like us?** The playbook carries your tone, your sign-off and the promises you allow, and the agent is told to answer only from it and your Notion pages. Run the test runs, read the drafts, and rewrite the playbook line the agent got wrong, which is a faster loop than editing instructions. Most teams have the voice right after a handful of drafts.
Outlook Daily Calendar Brief
Reads today's Outlook calendar at 7am and posts one Slack brief: internal meetings on a line each, every outside meeting carrying the company, open deals and last contact from HubSpot, and the parts of the day that still need moving. In a Microsoft shop the calendar is the org chart, and it is also where a customer meeting hides behind a distribution list and a room booking. This agent reads today's Outlook calendar at 7am, separates the outside meetings from the internal ones, and puts what HubSpot knows about each external attendee under their meeting: the company, the deals in play, the last time anybody spoke to them. It then names the parts of the day that will hurt: the runs with no gap, the meeting nobody has accepted, the call where only optional colleagues were invited. ## What people use it for - **Ready before the commute** - The whole day arrives at 7am on a phone with outside meetings already separated from internal ones. Nothing to open on the train, nothing to cross reference before the first call connects. - **Distribution lists unpacked** - An invite reading all EMEA or hiring panel tells you nothing about who is coming. The brief opens the event and reports the actual people, while never mistaking a room or a mailbox for an attendee. - **The day's pressure named early** - Back to back runs, a customer call nobody has accepted, and two things booked in the same hour all surface while there is still time to move one of them. - **Works from a delegated calendar** - Assistants who run somebody else's diary connect the mailbox they manage, and the brief lands wherever that pair actually talks. Same output, different chair. ## Before you fork **Can it read a shared or delegated mailbox?** Yes, provided the Microsoft account you connect already has access to that calendar, which is how most assistants work anyway. A single workflow covers a single calendar, so a team of five ends up with five copies, each posting into whichever channel or direct message suits that person. **Our channel is not private. What about sensitive meetings?** An event marked private is reduced to its time and its length, with subject, body and attendees left out completely. Everything else is what a colleague would see by opening the invite, plus CRM records anyone with HubSpot access can already read. If a meeting should not appear at all, mark it private in Outlook and the brief respects that. **What does it need from HubSpot, and what does a run cost?** Read access to contacts and deals and nothing beyond it: the CRM is never written to, and no attendee is ever mailed or messaged. A run is one calendar read, a lookup for each external attendee, and one message, so a day holding two customer meetings costs a fraction of a day holding eight.
Frequently asked questions
Use Outlook as an AI agent tool
Wire Outlook into a coding agent and let it use these operations as tools.
Connect Outlook with
Related integrations
Ready to build with Outlook?
Start building workflows in minutes with our visual builder. No code required.