Back to Integrations
integrationHTTP Request node
integrationMicrosoft Outlook node

HTTP Request and Microsoft Outlook integration

Save yourself the work of writing custom integrations for HTTP Request and Microsoft Outlook and use n8n instead. Build adaptable and scalable Development, Core Nodes, and Communication workflows that work with your technology stack. All within a building experience you will love.

How to connect HTTP Request and Microsoft Outlook

  • Step 1: Create a new workflow
  • Step 2: Add and configure nodes
  • Step 3: Connect
  • Step 4: Customize and extend your integration
  • Step 5: Test and activate your workflow

Step 1: Create a new workflow and add the first step

In n8n, click the "Add workflow" button in the Workflows tab to create a new workflow. Add the starting point – a trigger on when your workflow should run: an app event, a schedule, a webhook call, another workflow, an AI chat, or a manual trigger. Sometimes, the HTTP Request node might already serve as your starting point.

HTTP Request and Microsoft Outlook integration: Create a new workflow and add the first step

Step 2: Add and configure HTTP Request and Microsoft Outlook nodes

You can find HTTP Request and Microsoft Outlook in the nodes panel. Drag them onto your workflow canvas, selecting their actions. Click each node, choose a credential, and authenticate to grant n8n access. Configure HTTP Request and Microsoft Outlook nodes one by one: input data on the left, parameters in the middle, and output data on the right.

HTTP Request and Microsoft Outlook integration: Add and configure HTTP Request and Microsoft Outlook nodes

Step 3: Connect HTTP Request and Microsoft Outlook

A connection establishes a link between HTTP Request and Microsoft Outlook (or vice versa) to route data through the workflow. Data flows from the output of one node to the input of another. You can have single or multiple connections for each node.

HTTP Request and Microsoft Outlook integration: Connect HTTP Request and Microsoft Outlook

Step 4: Customize and extend your HTTP Request and Microsoft Outlook integration

Use n8n's core nodes such as If, Split Out, Merge, and others to transform and manipulate data. Write custom JavaScript or Python in the Code node and run it as a step in your workflow. Connect HTTP Request and Microsoft Outlook with any of n8n’s 1000+ integrations, and incorporate advanced AI logic into your workflows.

HTTP Request and Microsoft Outlook integration: Customize and extend your HTTP Request and Microsoft Outlook integration

Step 5: Test and activate your HTTP Request and Microsoft Outlook workflow

Save and run the workflow to see if everything works as expected. Based on your configuration, data should flow from HTTP Request to Microsoft Outlook or vice versa. Easily debug your workflow: you can check past executions to isolate and fix the mistake. Once you've tested everything, make sure to save your workflow and activate it.

HTTP Request and Microsoft Outlook integration: Test and activate your HTTP Request and Microsoft Outlook workflow

Phishing Analysis - URLScan.io and VirusTotal

This n8n workflow automates the analysis of email messages received in a Microsoft Outlook inbox to identify indicators of compromise (IOCs), specifically suspicious URLs. It can be triggered manually or scheduled to run daily at midnight.

The workflow begins by retrieving up to 100 read email messages from the Outlook inbox. However, there seems to be a configuration issue as it should retrieve unread messages, not read ones. It then marks these messages as read to avoid processing them again in the future.

The messages are then split into individual items using the Split In Batches node for sequential processing. For each email, the workflow analyzes its content to find URLs, which are considered potential IOCs. If URLs are found, the workflow proceeds to check these URLs for potential threats using two services, URLScan.io and VirusTotal, in parallel.

In the first path, URLScan.io scans each URL, and if there are no errors, the results from URLScan.io and VirusTotal are merged. If there are errors, the workflow waits 1 minute before attempting to retrieve the URLScan results again. The loop then continues for the next email. In the second path, VirusTotal is used to scan the URLs, and the results are retrieved.

Finally, the workflow checks if the data field is not empty, filtering out items where no data was found. It then sends a summarized Slack message to report details about the analyzed email, including the subject, sender, date, URLScan report URL, and VirusTotal verdict for URLs that were reported as malicious.

Potential issues during setup include configuring the Outlook node to retrieve unread messages, resolving a configuration issue in the VirusTotal node, and handling authentication and API keys for both URLScan.io and VirusTotal nodes. Additionally, proper error handling and testing with various email content types and URLs are essential to ensure the workflow accurately identifies IOCs and reports them to the Slack channel.

Nodes used in this workflow

Popular HTTP Request and Microsoft Outlook workflows

Code node
Merge node
Slack node
+4

Phishing Analysis - URLScan.io and VirusTotal

This n8n workflow automates the analysis of email messages received in a Microsoft Outlook inbox to identify indicators of compromise (IOCs), specifically suspicious URLs. It can be triggered manually or scheduled to run daily at midnight. The workflow begins by retrieving up to 100 read email messages from the Outlook inbox. However, there seems to be a configuration issue as it should retrieve unread messages, not read ones. It then marks these messages as read to avoid processing them again in the future. The messages are then split into individual items using the Split In Batches node for sequential processing. For each email, the workflow analyzes its content to find URLs, which are considered potential IOCs. If URLs are found, the workflow proceeds to check these URLs for potential threats using two services, URLScan.io and VirusTotal, in parallel. In the first path, URLScan.io scans each URL, and if there are no errors, the results from URLScan.io and VirusTotal are merged. If there are errors, the workflow waits 1 minute before attempting to retrieve the URLScan results again. The loop then continues for the next email. In the second path, VirusTotal is used to scan the URLs, and the results are retrieved. Finally, the workflow checks if the data field is not empty, filtering out items where no data was found. It then sends a summarized Slack message to report details about the analyzed email, including the subject, sender, date, URLScan report URL, and VirusTotal verdict for URLs that were reported as malicious. Potential issues during setup include configuring the Outlook node to retrieve unread messages, resolving a configuration issue in the VirusTotal node, and handling authentication and API keys for both URLScan.io and VirusTotal nodes. Additionally, proper error handling and testing with various email content types and URLs are essential to ensure the workflow accurately identifies IOCs and reports them to the Slack channel.
Microsoft Outlook node
HTTP Request node

Create, add an attachment, and send a draft using Microsoft Outlook

This workflow allows you to create, add an attachment, and send a draft using the Microsoft Outlook node. Microsoft Outlook node: This node creates a draft message with HTML content. You can either set the content as Text or HTML. You can also add the recipients to the draft in this node. HTTP Request node: This node fetches the logo of n8n from a URL and returns the binary data. You might want to fetch files from your machine or another email or a database. You can replace this node with the relevant node. Microsoft Outlook1 node: This node adds the attachment that we receive from the previous node to the draft message that we created. Microsoft Outlook2 node: This node sends the draft message to a recipient. Since we didn't mention the recipient in the Microsoft Outlook node, we add the recipient in this node. You can also enter multiple recipients.

Build your own HTTP Request and Microsoft Outlook integration

Create custom HTTP Request and Microsoft Outlook workflows by choosing triggers and actions. Nodes come with global operations and settings, as well as app-specific parameters that can be configured. You can also use the HTTP Request node to query data from any app or service with a REST API.

Microsoft Outlook supported actions

Create
Create a new calendar
Delete
Delete a calendar
Get
Retrieve a calendar
Get Many
List and search calendars
Update
Update a calendar
Create
Create a new contact
Delete
Delete a contact
Get
Retrieve a contact
Get Many
List and search contacts
Update
Update a contact
Create
Create a new email draft
Delete
Delete an email draft
Get
Retrieve an email draft
Send
Send an existing email draft
Update
Update an email draft
Create
Create a new event
Delete
Delete an event
Get
Retrieve an event
Get Many
List and search events
Update
Update an event
Create
Create a mail folder in the root folder of the user's mailbox
Delete
Delete a folder
Get
Retrieve a folder
Get Many
Get many folders
Update
Update a folder
Get Many
Retrieves the messages in a folder
Delete
Delete a message
Get
Retrieve a single message
Get Many
List and search messages
Move
Move a message to a folder
Reply
Create a reply to a message
Send
Send a message
Update
Update a message
Add
Add an attachment to a message
Download
Download an attachment from a message
Get
Retrieve information about an attachment of a message
Get Many
Retrieve information about the attachments of a message
Use case

Save engineering resources

Reduce time spent on customer integrations, engineer faster POCs, keep your customer-specific functionality separate from product all without having to code.

Learn more

FAQs

  • Can HTTP Request connect with Microsoft Outlook?

  • Can I use HTTP Request’s API with n8n?

  • Can I use Microsoft Outlook’s API with n8n?

  • Is n8n secure for integrating HTTP Request and Microsoft Outlook?

  • How to get started with HTTP Request and Microsoft Outlook integration in n8n.io?

Looking to integrate HTTP Request and Microsoft Outlook in your company?

Over 3000 companies switch to n8n every single week

Why use n8n to integrate HTTP Request with Microsoft Outlook

Build complex workflows, really fast

Build complex workflows, really fast

Handle branching, merging and iteration easily.
Pause your workflow to wait for external events.

Code when you need it, UI when you don't

Simple debugging

Your data is displayed alongside your settings, making edge cases easy to track down.

Use templates to get started fast

Use 1000+ workflow templates available from our core team and our community.

Reuse your work

Copy and paste, easily import and export workflows.

Implement complex processes faster with n8n

red iconyellow iconred iconyellow icon