Start in minutes

Ready-made templates with HTTP Request

Pre-configured flows with HTTP Request, ready to activate in a few clicks.

PREMIUM
HTTP Request
Facebook Lead Ads

For each new lead on a Facebook Lead Ads, send a message to your app/system via HTTP Request

Automate
PREMIUM
HTTP Request
RD Station CRM

When a deal is marked as won in RD Station CRM, its data is sent to your internal ERP

Automate
PREMIUM
HTTP Request
Google Sheets

When a new row is added on Google Sheets, send a message to your app via HTTP Request

Automate
PREMIUM
HTTP Request
Asaas

For each created payment on Asaas, send a message to your app/system via HTTP Request

Automate
PREMIUM
HTTP Request
Omie ERP

When a sales order is moved to a specific stage in Omie ERP, send a notification to your logistics system.

Automate
See all templates with HTTP Request

HTTP Request in practice

How different teams use HTTP Request in everyday automations.

Illustration of HTTP Request being used in a Pluga automation

  • The sales team closes the deal and Pluga queries a business ID or postal code lookup service on the spot. Company name, address and business data come back ready to generate the contract or update the customer record in the CRM.

    Enrich records with HTTP Request

  • Deal closed in dollars, euros or another currency? HTTP Request queries a rates API, brings back the day's converted value, and the flow continues with adjusted amounts to post the entry in the ERP, spreadsheet or finance system.

    Pull exchange rates with HTTP Request

  • When an order moves to the delivery stage, the flow queries the carrier's API and brings back the updated delivery time. Then, an update email with the exact information is sent to the customer.

    Check shipping with HTTP Request

  • HTTP Request runs a daily search across ads and analytics APIs, captures the previous day's spend, clicks and conversions, and feeds the team's spreadsheet or dashboard. Every morning, the numbers are already logged.

    Pull campaign data

All automations with HTTP Request

Trusted by over 10.000 amazing companies

Possibilities with HTTP Request on Pluga

Triggers and Actions of HTTP Request

The trigger is the event that starts the flow with HTTP Request, while the action is the task Pluga performs automatically on that app.

HTTP Request

API new request

For each new HTTP Request to your tool

How it works:

Whenever something happens on the source app

1. Start a workflow from a system without a native integration

2. Use an event from your own API as the trigger

3. Capture data from your company's internal tools

All happening in a single automation! ✨

Premium Trigger
HTTP Request

API new request

For each new HTTP Request to your tool

  • Start a workflow from a system without a native integration
  • Use an event from your own API as the trigger
  • Capture data from your company's internal tools
Google Sheets RD Station CRM Asaas Omie ERP
HTTP Request

Send a message via HTTP Request

Send a request to your app/system via HTTP Request

How it works:

Whenever something happens on the source app

1. Send workflow data to a tool without a native integration

2. Query public APIs

3. Create, update, or delete records in a custom system

4. Build the request body in the exact format required by the API

All happening in a single automation! ✨

Premium Action
HTTP Request

Send a message via HTTP Request

Send a request to your app/system via HTTP Request

  • Send workflow data to a tool without a native integration
  • Query public APIs
  • Create, update, or delete records in a custom system
  • Build the request body in the exact format required by the API
Google Sheets RD Station CRM Asaas Omie ERP

API URL Required

Type of completion of the request fields

Request body (JSON)

Headers (JSON)

Query params (JSON)

Fields

Headers

Query Params

How it works

How to integrate with HTTP Request

1. Trigger Source app When something happens…
2. Intermediate action HTTP Request Send a message via HTTP Request
3. Action Target app Perform an action…
Works even better with

Boost HTTP Request with other workflow features

Combine multiple resources to build even smarter workflows with HTTP Request.

Kit de IA

Kit de IA

Explore

The AI Toolkit classifies, extracts data, summarizes, and translates the information flowing through your automations. You configure it, Pluga builds the prompt, and the result goes straight to the next step in your workflow.

Roteador

Roteador

Explore

The Router lets you create conditional paths within a single workflow. You define the criteria, and Pluga routes the execution to the right path based on the captured data.

Agendador

Agendador

Explore

The Scheduler runs your workflows on the days and times you choose. Set the frequency by the hour, day, week, or month, adjust the time zone, and select which days of the week to include.

Frequently Asked Questions

Everything you need to know to get started with HTTP Request on Pluga.

  • It's an advanced feature that lets you connect your apps to external APIs. With HTTP Request, you can fetch, send, create or update data in your own systems or in apps that don't yet have a native integration on Pluga. Just set up the URL, request method and data format, and Pluga takes care of the rest.

  • No. HTTP Request is a Premium feature. That means you need a paid Pluga plan to use it.

  • Yes! You can use it as an intermediate action in your flow. For example: a deal is won in RD Station CRM (Trigger), HTTP Request queries a currency exchange or business ID lookup API (Intermediate Action), and Pluga sends that enriched information to a Google Sheets spreadsheet or your finance ERP (Final Action).

  • Absolutely. The "API new request" trigger lets you start an automation on Pluga from your company's internal system or from an app without a native integration. Your own API fires the event, and Pluga captures the data to continue the flow.

  • Yes. HTTP Request becomes even more flexible and intelligent when combined with Pluga features. You can connect it to Scheduler (to fetch metrics every morning), use Router (to route the API data down different paths), or process the request's response with AI Toolkit.