Back to Integrations
integrationHTTP Request node
integrationPhantombuster node

HTTP Request and Phantombuster integration

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

How to connect HTTP Request and Phantombuster

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

Step 2: Add and configure HTTP Request and Phantombuster nodes

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

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

Step 3: Connect HTTP Request and Phantombuster

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

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

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

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

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

Auto-like tweets from selected profiles with Phantombuster & SharePoint AI rotation

Who’s it for
Growth hackers, community builders, and marketers who want to keep their Twitter (X) accounts active by liking posts from selected profiles automatically.

How it works / What it does
Schedule Trigger fires hourly.
Profile Post Extractor fetches up to 20 tweets for each profile in your CSV.
Select Cookie rotates Twitter session-cookies.
Get Random Post checks against twitter_posts_already_liked.csv.
Builds twitter_posts_to_like.csv, uploads to SharePoint.
Phantombuster Autolike Agent likes the tweet.
Logs the liked URL to avoid duplicates.

How to set up
Add Phantombuster + SharePoint credentials.
In SharePoint “Phantombuster” folder:
• twitter_session_cookies.txt
• twitter_posts_already_liked.csv (header postUrl)
• profiles_twitter.csv (list of profiles).

Profile CSV format
Your profiles_twitter.csv must contain a header profileUrl and direct links to the Twitter profiles. Example:
profileUrl
https://twitter.com/elonmusk
https://twitter.com/openai

Nodes used in this workflow

Popular HTTP Request and Phantombuster workflows

Auto-like Tweets from Selected Profiles with Phantombuster & SharePoint AI Rotation

Who’s it for Growth hackers, community builders, and marketers who want to keep their Twitter (X) accounts active by liking posts from selected profiles automatically. How it works / What it does Schedule Trigger fires hourly. Profile Post Extractor fetches up to 20 tweets for each profile in your CSV. Select Cookie rotates Twitter session-cookies. Get Random Post checks against twitter_posts_already_liked.csv. Builds twitter_posts_to_like.csv, uploads to SharePoint. Phantombuster Autolike Agent likes the tweet. Logs the liked URL to avoid duplicates. How to set up Add Phantombuster + SharePoint credentials. In SharePoint “Phantombuster” folder: • twitter_session_cookies.txt • twitter_posts_already_liked.csv (header postUrl) • profiles_twitter.csv (list of profiles). Profile CSV format Your profiles_twitter.csv must contain a header profileUrl and direct links to the Twitter profiles. Example: profileUrl https://twitter.com/elonmusk https://twitter.com/openai

Automated Instagram Commenting on Selected Profiles with GPT-4o and Phantombuster

Who’s it for Influencers and social-media teams who want to comment automatically on posts from selected Instagram profiles—scaling engagement while staying within platform limits. How it works / What it does Schedule Trigger runs every 2 h. Profile Post Extractor fetches up to 20 posts per profile from your CSV. Select Cookie rotates Instagram session-cookies. Get Random Post selects one. Create Comment (GPT-4o) writes ≤150-character reply in your chosen language. Builds instagram_post_to_comment.csv, uploads to SharePoint. Phantombuster Autocomment Agent posts it. Logged in instagram_posts_already_commented.csv to prevent repeats. How to set up Same as the auto-liker, but also add instagram_posts_already_commented.csv (header postUrl). Define tracked profiles in profiles_instagram.csv. Configure comment prompt & language in Set ENV Variables. Profile CSV format Your profiles_instagram.csv must contain a header profileUrl and valid Instagram profile URLs. Example: profileUrl https://www.instagram.com/brand_account/ https://www.instagram.com/influencer123/

Auto-like Instagram posts from chosen profiles with Phantombuster + SharePoint

Who’s it for Social-media managers, growth hackers, and brands who want to keep their Instagram accounts active by auto-liking posts from specific profiles they track—without scrolling feeds manually. How it works / What it does Schedule Trigger runs every 2 h. Profile Post Extractor pulls up to 20 recent posts from each Instagram profile in your CSV. Select Cookie rotates Instagram session-cookies. Get Random Post picks one and checks against instagram_posts_already_liked.csv. Builds instagram_posts_to_like.csv, uploads to SharePoint. Phantombuster Autolike Agent likes the post. Liked URLs are appended to prevent duplicates. Wait nodes throttle activity (~12 likes/profile/day). How to set up Add credentials: Phantombuster API, SharePoint OAuth2. In SharePoint › “Phantombuster” folder create: • instagram_session_cookies.txt (one per line). • instagram_posts_already_liked.csv (header postUrl). • profiles_instagram.csv with profile URLs. Adjust schedule if needed. Activate the workflow—likes will run automatically. Requirements n8n 1.33+ Phantombuster Growth plan Microsoft 365 SharePoint tenant How to customize Add/remove tracked profiles in profiles_instagram.csv. Adjust throttle by changing Wait intervals. Swap SharePoint for Google Drive/Dropbox if needed.

Build your own HTTP Request and Phantombuster integration

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

Phantombuster supported actions

Delete
Delete an agent by ID
Get
Get an agent by ID
Get Many
Get many agents of the current user's organization
Get Output
Get the output of the most recent container of an agent
Launch
Add an agent to the launch queue
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
Use case

Supercharge your CRM

Need a more powerful integration with your CRM? n8n lets you go beyond standard integrations offered by popular CRMs!

Learn more

FAQs

  • Can HTTP Request connect with Phantombuster?

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

  • Can I use Phantombuster’s API with n8n?

  • Is n8n secure for integrating HTTP Request and Phantombuster?

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

Need help setting up your HTTP Request and Phantombuster integration?

Discover our latest community's recommendations and join the discussions about HTTP Request and Phantombuster integration.
Moiz Contractor
theo
Jon
Dan Burykin
Tony

Looking to integrate HTTP Request and Phantombuster in your company?

Over 3000 companies switch to n8n every single week

Why use n8n to integrate HTTP Request with Phantombuster

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