Back to Integrations
integrationHTTP Request node
integrationNotion node

HTTP Request and Notion integration

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

How to connect HTTP Request and Notion

  • 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 Notion integration: Create a new workflow and add the first step

Step 2: Add and configure HTTP Request and Notion nodes

You can find HTTP Request and Notion 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 Notion nodes one by one: input data on the left, parameters in the middle, and output data on the right.

HTTP Request and Notion integration: Add and configure HTTP Request and Notion nodes

Step 3: Connect HTTP Request and Notion

A connection establishes a link between HTTP Request and Notion (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 Notion integration: Connect HTTP Request and Notion

Step 4: Customize and extend your HTTP Request and Notion 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 Notion with any of n8n’s 1000+ integrations, and incorporate advanced AI logic into your workflows.

HTTP Request and Notion integration: Customize and extend your HTTP Request and Notion integration

Step 5: Test and activate your HTTP Request and Notion workflow

Save and run the workflow to see if everything works as expected. Based on your configuration, data should flow from HTTP Request to Notion 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 Notion integration: Test and activate your HTTP Request and Notion workflow

Automate Competitor Research with Exa.ai, Notion and AI Agents

This n8n workflow demonstrates a simple multi-agent setup to perform the task of competitor research. It showcases how using the HTTP request tool could reduce the number of nodes needed to achieve a workflow like this.

How it works
For this template, a source company is defined by the user which is sent to Exa.ai to find competitors.
Each competitor is then funnelled through 3 AI agents that will go out onto the internet and retrieve specific datapoints about the competitor; company overview, product offering and customer reviews.
Once the agents are finished, the results are compiled into a report which is then inserted in a notion database.

Check out an example output here: https://jimleuk.notion.site/2d1c3c726e8e42f3aecec6338fd24333?v=de020fa196f34cdeb676daaeae44e110&pvs=4

Requirements

An OpenAI account for the LLM.
Exa.ai account for access to their AI search engine.
SerpAPI account for Google search.
Firecrawl.dev account for webscraping.
Notion.com account for database to save final reports.

Customising the workflow

Add additional agents to gather more datapoints such as SEO keywords and metrics.

Not using notion? Feel free to swap this out for your own database.

Nodes used in this workflow

Popular HTTP Request and Notion workflows

Analyse papers from Hugging Face with AI and store them in Notion

This workflow automates the process of retrieving Hugging Face paper summaries, analyzing them with OpenAI, and storing the results in Notion. Here’s a breakdown of how it works: ⏰ Scheduled Trigger: The flow is set to run automatically at 8 AM on weekdays. 📄 Fetching Paper Data: It fetches Hugging Face paper summaries using their API. 🔍 Data Check: Before processing, the workflow checks if the paper already exists in Notion to avoid duplicates. 🤖 Content Analysis with OpenAI: If the paper is new, it extracts the summary and uses OpenAI to analyze the content. 📥 Store Results in Notion: After analysis, the summarized data is saved in Notion for easy reference. ⚙️ Set Up Steps for Automation Follow these steps to set up this automated workflow with Hugging Face, OpenAI, and Notion integration: 🔑 Obtain API Tokens: You’ll need the Notion and OpenAI API tokens to authenticate and connect these services with n8n. 🔗 Integration in n8n: Link Hugging Face, OpenAI, and Notion by configuring the appropriate nodes in n8n. 🔧 Configure Workflow Logic: Set up a cron trigger for automatic execution at 8 AM on weekdays. Use an HTTP request node to fetch Hugging Face paper data. Add logic to check if the data already exists in Notion. Set up the OpenAI integration to analyze the paper’s summary. Store the results in Notion for easy access and reference. Result:
+3

Realtime Notion Todoist 2-way Sync with Redis

Purpose This solution enables you to manage all your Notion and Todoist tasks from different workspaces as well as your calendar events in a single place. All tasks can be managed in Todoist and additionally Fantastical can be used to manage scheduled tasks & events all together. Demo & Explanation How it works The realtime sync consists of two workflows, both triggered by a registered webhook from either Notion or Todoist To avoid overwrites by lately arriving webhook calls, every time the current task is retrieved from both sides. Redis is used to prevent from endless loops, since an update in one system triggers another webhook call again. Using the ID of the task, the trigger is being locked down for 15 seconds. Depending on the detected changes, the other side is updated accordingly. Generally Notion is treaded as the main source. Using an "Obsolete" Status, it is guaranteed, that tasks never get deleted entirely by accident. The Todoist ID is stored in the Notion task, so they stay linked together An additional full sync workflow daily fixes inconsistencies, if any of them occurred, since webhooks cannot be trusted entirely. Since Todoist requires a more complex setup, a tiny workflow helps with activating the webhook. Another tiny workflow helps generating a global config, which is used by all workflows for mapping purposes. Mapping (Notion >> Todoist) Name: Task Name Priority: Priority (1: do first, 2: urgent, 3: important, 4: unset) Due: Date Status: Section (Done: completed, Obsolete: deleted) <page_link>: Description (read-only) Todoist ID: <task_id> Current limitations Changes on the same task cannot be made simultaneously in both systems within a 15-20 second time frame Subtasks are not linked automatically to their parent yet Recurring tasks are not supported yet Tasks names do not support URL’s yet Prerequisites Notion A database must already exist (get a basic template here) with the following properties (case matters!): Text: "Name" Status: "Status", containing at least the options "Backlog", "In progress", "Done", "Obsolete" Select: "Priority", containing the options "do first", "urgent", "important" Date: "Due" Checkbox: "Focus" Text: "Todoist ID" Todoist A project must already exist with the same sections like defined as Status in Notion (except Done and Obsolete) Redis Create a Free Redis Cloud instance or self-host Setup The setup involves quite a lot of steps, yet many of them can be automated for business internal purposes. Just follow the video or do the following steps: Setup credentials for Notion (access token), Todoist (access token) and Redis - you can also create empty credentials and populate these later during further setup Clone this workflow by clicking the "Use workflow" button and then choosing your n8n instance - otherwise you need to map the credentials of many nodes. Follow the instructions described within the bundle of sticky notes on the top left of the workflow How to use You can apply changes (create, update, delete) to tasks both in Notion and Todoist which then get synced over within a couple of seconds (this is handled by the differential realtime sync) The daily running full sync, resolves possible discrepancies in Todoist and sends a summary via email, if anything needed to be updated. In case that contains an unintended change, you can jump to the Task from the email directly to fix it manually.

Automatically Import your Meta Threads Posts into Notion

Who is this for? This template is designed for social media managers, content creators, data analysts, and anyone who wants to automatically save and analyze their Meta Threads posts in Notion. It’s particularly useful for: Building a personal archive of your Threads content. Training AI models using your social media data. Tracking your online presence and engagement. What this workflow does This workflow uses the Meta Threads API to automatically retrieve your posts and import them into a Notion database. It retrieves the post content, date, and time, and stores them in designated properties within your Notion database. Setup Get Threads Access Token and ID: Obtain a long-lived access token and your Threads ID from the Meta Threads developer platform. This token auto-refreshes, ensuring uninterrupted workflow operation. Configure Credentials and Date Range: In the “Set Credentials” node (using edit fields), enter your token and ID. Set the since and until parameters in the “Set Date Range” node to specify the post import period. Connect to Notion and Create a Database: Connect to your Notion workspace and create a database with these properties (customize with the “Create Properties” node): a. Title: Threads post URL (Notion entry title). b. Threads ID: Unique post ID (prevents duplicate imports). c. Username: Post author (for future multi-account/source management). d. Post Date: Original post date. e. Source (Multi-Select): “Threads” tag (for future multi-platform import and filtering). f. Created: Import date and time. g. Import Check (Optional): For use with a separate post-categorization workflow.

2-way Sync Google Contacts and Notion

Sync your Google Contacts with your Notion database. You can filter contacts by label or sync all contacts. All contact information is kept in sync between Google and Notion. What happens if I delete a contact? It gets deleted on the other end. Google Contact deleted → Notion page deleted Notion page deleted → Google contact deleted But you can easily change this behavior by disabling the respective deletion nodes. Who is this template for? Service providers looking to keep track of client information Organized individuals who like to centralize their lives in Notion Automation nerds who enjoy creating interesting projects How it works First, you perform an initial import to bring your contacts from Google to Notion. After that, the workflow listens for changes in both Notion and Google and keeps everything in sync. How to set up Instructions are included within the workflow itself. Check out my other templates 👉 https://n8n.io/creators/solomon/

Automate Competitor Research with Exa.ai, Notion and AI Agents

This n8n workflow demonstrates a simple multi-agent setup to perform the task of competitor research. It showcases how using the HTTP request tool could reduce the number of nodes needed to achieve a workflow like this. How it works For this template, a source company is defined by the user which is sent to Exa.ai to find competitors. Each competitor is then funnelled through 3 AI agents that will go out onto the internet and retrieve specific datapoints about the competitor; company overview, product offering and customer reviews. Once the agents are finished, the results are compiled into a report which is then inserted in a notion database. Check out an example output here: https://jimleuk.notion.site/2d1c3c726e8e42f3aecec6338fd24333?v=de020fa196f34cdeb676daaeae44e110&pvs=4 Requirements An OpenAI account for the LLM. Exa.ai account for access to their AI search engine. SerpAPI account for Google search. Firecrawl.dev account for webscraping. Notion.com account for database to save final reports. Customising the workflow Add additional agents to gather more datapoints such as SEO keywords and metrics. Not using notion? Feel free to swap this out for your own database.

Automated Hugging Face Paper Summary Fetching & Categorization Workflow

How the Automated Workflow Works Scheduled Fetching from Hugging Face ⏰ The workflow triggers every weekday at 8 AM, automatically fetching the latest papers from Hugging Face for easy access. Duplication Check to Avoid Redundant Entries 🔍 It ensures the paper's summary is not already stored in your Notion workspace, preventing duplicate records and keeping your database organized. Content Analysis with OpenAI 🧠 Using OpenAI's powerful capabilities, the workflow analyzes the fetched paper summary, extracts key insights, and categorizes the content for easier understanding. Data Storage and Notification Integration 📥🔔 Once the summary is processed, it's automatically stored in your Notion workspace, and a notification containing the paper details is sent to your designated Slack channel for quick reference. Set Up Your Automated Workflow Create Your n8n Account 📝 Start by registering for an n8n account and logging into the n8n cloud service. Connect OpenAI, Notion, and Slack 🔗 Link your OpenAI, Notion, and Slack accounts by entering the appropriate tokens. This step will take approximately 10–15 minutes to complete. Import the Workflow Template 📥 Import the provided workflow template into your n8n instance to streamline the setup process. Activate the Workflow for Daily Summaries 🚀 After importing, simply enable the workflow, and you’re all set to receive daily paper summaries automatically. Setup Time ⏳: Approximately 15–20 minutes. Why Use This Automated Workflow? This automated workflow not only saves you time by fetching and categorizing the latest research papers but also helps streamline your Notion workspace and Slack notifications, allowing you to stay organized and efficient without manual intervention. Results Presentation

Build your own HTTP Request and Notion integration

Create custom HTTP Request and Notion 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.

Notion supported actions

Append After
Append a block
Get Child Blocks
Get many child blocks
Get
Get a database
Get Many
Get many databases
Search
Search databases using text search
Get
Get a database
Get Many
Get many databases
Create
Create a pages in a database
Get
Get a page in a database
Get Many
Get many pages in a database
Update
Update pages in a database
Create
Create a pages in a database
Get Many
Get many pages in a database
Update
Update pages in a database
Create
Create a page
Get
Get a page
Search
Text search of pages
Archive
Archive a page
Create
Create a page
Search
Text search of pages
Get
Get a user
Get Many
Get many users
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 Notion?

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

  • Can I use Notion’s API with n8n?

  • Is n8n secure for integrating HTTP Request and Notion?

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

Need help setting up your HTTP Request and Notion integration?

Discover our latest community's recommendations and join the discussions about HTTP Request and Notion integration.
Justin Cheu
Moiz Contractor
Cris A. Works
theo
Jon

Looking to integrate HTTP Request and Notion in your company?

Over 3000 companies switch to n8n every single week

Why use n8n to integrate HTTP Request with Notion

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