Start in minutes

Ready-made templates with Roteador

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

PREMIUM
Conta Azul
Roteador
Asaas

When a payment is received in Asaas, issue an invoice or create an accounts receivable entry, depending on the payment method.

Automate
PREMIUM
RD Station CRM
Roteador
eNotas
Mercado Pago

When a payment is approved in Mercado Pago, issue an invoice in eNotas and mark the customer as VIP in RD Station CRM when the order value is high

Automate
PREMIUM
Trello
Slack
Roteador
Zendesk

Forward Zendesk tickets with the Router based on priority or category: urgent tickets go to a Slack channel, while all others are added to a Trello board.

Automate
PREMIUM
Slack
Agendor
Roteador
Typeform

Use the Router to split new Typeform leads based on their source or score, send them to the appropriate Agendor pipeline, and notify your sales team in Slack.

Automate
PREMIUM
Z-API
Roteador
Facebook Lead Ads

Based on each response submitted by a new lead captured through Facebook Lead Ads, send a personalized WhatsApp (Z-API) text message.

Automate
See all templates with Roteador

Roteador in practice

How different teams use Roteador in everyday automations.

Illustration of Roteador being used in a Pluga automation

  • Every lead passes through Router before becoming an opportunity and is forwarded to a pipeline or rep based on the rule your sales team defines: region, product of interest, company size, and so on.

    Distribute leads with Router

  • One automation, three routes: a PIX sale issues an invoice and settles the payment. A card sale becomes an accounts receivable entry, with adjusted terms and fees deducted. High-value purchases notify the VIP support team.

    Route charges with Router

  • Router reads each new lead's profile and forwards it to the nurturing track that makes sense: separate tool, cadence, and content from the very first moment.

    Segment contacts with Router

  • A new ticket comes in, Router checks its subject or source channel and routes it instantly. Critical issues go to priority support, billing questions go to sales, and cancellation requests trigger the retention team.

    Organize tickets with Router

All automations with Roteador

Trusted by over 10.000 amazing companies

Possibilities with Roteador on Pluga

Available actions with Roteador

The action is the task Pluga performs automatically on Roteador, every time a trigger runs.

Roteador

Single match (recommended)

E.g.: Route A Email contains “bob” / Route B Email contains “pluga”. On email “bob@pluga”, only the Route A will run

How it works:

Whenever something happens on the source app

1. Route each piece of data through a dedicated path based on mutually exclusive criteria

2. Separate payments by payment method, such as Pix, credit card, or bank slip

3. Route support tickets to different channels based on priority or category.

4. Send leads to separate pipelines based on their source or score

All happening in a single automation! ✨

Premium Action
Roteador

Single match (recommended)

E.g.: Route A Email contains “bob” / Route B Email contains “pluga”. On email “bob@pluga”, only the Route A will run

  • Route each piece of data through a dedicated path based on mutually exclusive criteria
  • Separate payments by payment method, such as Pix, credit card, or bank slip
  • Route support tickets to different channels based on priority or category.
  • Send leads to separate pipelines based on their source or score
Asaas Mercado Pago Zendesk RD Station CRM HubSpot

Roteador

Multiple matches

E.g.: Route A Email contains “bob” / Route B Email contains “pluga”. On email “bob@pluga”, all routes will run

How it works:

Whenever something happens on the source app

1. Run multiple actions in parallel from a single event

2. Issue an invoice while simultaneously tagging the customer based on their purchase amount

3. Notify different teams about the same order, with each team receiving only the information that matters to them

4. Apply multiple criteria that can coexist in the same data, such as purchase amount and payment method

All happening in a single automation! ✨

Premium Action
Roteador

Multiple matches

E.g.: Route A Email contains “bob” / Route B Email contains “pluga”. On email “bob@pluga”, all routes will run

  • Run multiple actions in parallel from a single event
  • Issue an invoice while simultaneously tagging the customer based on their purchase amount
  • Notify different teams about the same order, with each team receiving only the information that matters to them
  • Apply multiple criteria that can coexist in the same data, such as purchase amount and payment method
Nuvemshop (Tiendanube) Mercado Pago RD Station CRM Slack Google Sheets

How it works

How to integrate with Roteador

1. Trigger Source app When something happens…
2. Intermediate action Roteador Single match (recommended), Multiple matches
3. Action Target app Perform an action…
Works even better with

Boost Roteador with other workflow features

Combine multiple resources to build even smarter workflows with Roteador.

Formatador

Formatador

Explore

The Formatter standardizes dates, numbers, and text as they pass through your automation, formatting everything automatically. Data leaves one app and arrives in the next in the expected format.

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.

HTTP Request

HTTP Request

Explore

The HTTP Request step connects your tools to external APIs to retrieve, send, or update data. You configure the URL, request method, and response schema. Pluga takes care of the rest.

Frequently Asked Questions

Everything you need to know to get started with Roteador on Pluga.

  • Roteador is a Premium Pluga tool that works as a controller within the flow. Instead of always following the same path, the automation reads the data coming from the trigger, compares it against the conditions you defined, and routes execution to the correct path. The practical result is replacing several parallel automations sharing the same trigger with a single one, organized and easier to maintain.

  • These are Roteador's two operating modes. In single match, the automation follows the first route whose condition is true and ignores the rest. In multiple matches, every route is checked and all the ones that are true run in parallel. When in doubt, start with single match: it's the most common mode.

  • No. Even if you set up 4 or 5 routes in Roteador, your plan only consumes events for the actions that actually run. Routes that aren't triggered in a given execution generate no cost. This means you can build sophisticated flows without worrying about wasting events on routes that stayed idle.

  • Conditional filters block or allow the execution of an entire automation based on one rule. Roteador goes further: it keeps the automation active and distributes execution across different paths, each with its own action and field mapping.

  • Roteador is added as an intermediate step. It's never the final step of a flow, since its job is to direct execution to actions, not to end them. You can chain Roteador after other intermediate steps, like AI Toolkit, creating flows where AI processes the data first and Roteador decides where the result goes.