Webhooks listen for a request and receive data when an event occurs. This reminds me of myself as a kid, waiting for the school bell to ring. When the bell rang, my workflow in life was to run home for a snack! Webhooks work in a similar manner; they are triggered by events — making webhooks an excellent way of receiving and returning data, as they are very efficient and fast, eliminating the need for maintaining a client state (such as a timestamp, for example) that would be necessitated in a polling-based setup.
The Webhook node is a versatile and powerful node in the n8n ecosystem. It receives HTTP Requests, instead of sending them. This makes the node useful — you guessed it, to receive data from any other service that supports Webhooks. …
Every year, I help organize the South Indian Model United Nations, the third-largest Model UN conference in South India. We host over 850+ students and a total of around 1000 attendees at our conference each year. The team cuts across a lot of data about our speakers, sessions, and attendees. We do this with a team of just 10 people.
Once you start organizing several of these conferences, you start to realize that a lot of human effort can be reduced by automating some seemingly mundane tasks — almost 45%, according to an article published by McKinsey & Company.
One example that I can think of for this is the registration process for attendees. With COVID-19 forcing us to virtualize our conference, moving online has presented us with new challenges for the registration and onboarding of delegates — we now have to coordinate video conferences, permissions management, payments, chat rooms, to name a few. …
Video calls are an invaluable tool that can connect people from around the world. As the pandemic progresses, we’ve depended on these conversations to effectively disseminate company knowledge, enabling us to build more collaboratively.
Video calls are meant to be easy — like simply walking up to a person and starting a conversation. But in reality, this is far from the truth. It requires the user to maintain an account, logging into a platform every time to start a video meeting.
At n8n, we use Mattermost and Whereby. Mattermost is an open-source, self-hostable online chat service with file sharing, search, and integrations. It is designed as an internal chat for organizations and companies. …
With over 150 nodes, n8n saves countless hours by automating repetitive tasks. But what happens when n8n doesn’t have a node for a tool you love?
Enter the HTTP Request node. This node can send any type of HTTP request, making it useful to talk to any RESTful API. This makes the HTTP Request node one of the most versatile and powerful nodes in the n8n ecosystem.
In this article, we are going to explore three examples to showcase how the HTTP Request node can be used in your workflow to automate tasks:
Blogging isn’t just about writing quality content, but also ensuring that it reaches as many members of your audience as possible. This means that bloggers have to post an article multiple times on different platforms. This often entails ensuring that the formatting and layouts are consistent across platforms, which tends to be a time consuming (and exhausting) ordeal.
Automating these processes can save large amounts of time and effort, allowing bloggers to reclaim time to focus on what they do best — writing. This tutorial will teach you how to post blog posts to multiple blogging platforms automatically.
In this tutorial, we’re going to create and store all our posts in one central platform — Strapi. It is a headless CMS which will store all our content. We will use n8n to create a workflow that will take content from Strapi using webhooks and create posts on Medium and Dev.to using their REST APIs. Strapi supports post creation through markdown formatting, which will help maintain the layouts of articles across platforms. …