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.
Create custom HTTP Request and Pusher 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.
Trigger event
Trigger an event on a specified channel.
List channels
Query for a list of channels within an application that have active subscriptions.
Get channel information
Retrieve the state of an individual channel by its name.
Get presence users
Retrieve a list of users present on a presence channel.
Fetch info for multiple channels
Allows fetching a hash of occupied channels optionally filtered by prefix.
Fetch info for one channel
Retrieves information about a specific channel.
Trigger event
Triggers an event on one or more channels.
Trigger event
Triggers an event on a specified channel.
Trigger multiple events
Triggers multiple events on specified channels.
Trigger multiple events
Triggers multiple events in a single call (up to 10 per call on the multi-tenant clusters).
Fetch info for one channel
Fetch one or some attributes for a given channel.
Terminate user connections
Terminates all connections established by the given user.
Fetch users
Fetch user IDs of users currently subscribed to a presence channel.
Terminate user connections
Terminates all connections of a specified user.
Fetch users
Retrieves a list of users connected to a channel.
To set up Pusher integration, add the HTTP Request node to your workflow canvas and authenticate it using a generic authentication method. The HTTP Request node makes custom API calls to Pusher to query the data you need using the API endpoint URLs you provide.
See the example hereThese API endpoints were generated using n8n
n8n AI workflow transforms web scraping into an intelligent, AI-powered knowledge extraction system that uses vector embeddings to semantically analyze, chunk, store, and retrieve the most relevant API documentation from web pages. Remember to check the Pusher official documentation to get a full list of all API endpoints and verify the scraped ones!
Discover our latest community's recommendations and join the discussions about HTTP Request and Pusher integration.
Moiz Contractor
Describe the problem/error/question Hi, I am getting a - Google hasnt verified this app error. I have Enable the API, the domain is verified on the Cloud Console, the user is added in the search console and the google do…
Open topic
theo
Describe the problem/error/question I a http request node, I use a Google service account API credential type. I need the “Impersonate a User” field to be dynamic, pulling data from the “email” field in the previous nod…
Open topic
Jon
Describe the problem/error/question I have a simple workflow that retrieves an image from url with http node and prints the json/binary in code. I have a few logs, but I am confused why I see duplicate messages for each …
Open topic
Dan Burykin
Hi! I’m still in the beginning. Now I need to make an API call via HTTP node, and send all static parameters, but with the array of emails parameter (named it wrongly just to show what I need {{ $json.email[all] }}). Wo…
Open topic
Tony
Hi! I have a question: I am making an app that allows a person to scrape some data via a Python library. I have a Python script that needs to be triggered after certain user actions. What is the best way to: Send a p…
Open topic
The world's most popular workflow automation platform for technical teams including
Build complex workflows, really fast