Start in minutes

Ready-made templates with Interruptor

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

Interruptor in practice

How different teams use Interruptor in everyday automations.

Illustration of Interruptor being used in a Pluga automation
  • When the deal progresses, the rep takes over and Switch pauses the agent's replies. Every time the rep responds, the pause window renews. No interruptions at the critical moment of closing.

    Control pauses with Switch
  • Order tracking, exchanges and returns are things the agent handles. But some cases call for a human. When the rep takes over, Switch pauses the agent for that customer.

    Prioritize humans with Switch
  • During a launch, the agent can answer questions at scale. But when someone from the team wants to talk directly to a lead, Switch pauses the agent for that contact until the personal conversation ends.

    Silence the agent with Switch
  • The agent covers the first level of support and escalates the rest. As soon as the technician takes over the conversation, Switch pauses the agent: during the configured window, only human replies reach the customer.

    Escalate without conflict

All automations with Interruptor

Trusted by over 10.000 amazing companies

Possibilities with Interruptor on Pluga

Available actions with Interruptor

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

Premium Action
Interruptor

Interromper fluxo

Interruptor

  • Prevent an AI agent from responding while a human is actively handling the same conversation
  • Avoid duplicate or conflicting responses in automated support channels
  • Pause a sensitive workflow for a set period without disabling the entire automation
  • Pause a specific conversation without affecting other automations in progress

Evaluated information Required

Condition type Required

Comparison value Required

Flow identifier Required

Interruption duration selection mode

Interruption duration

Interruption duration (minutes)

How it works

How to integrate with Interruptor

1. Trigger Source app When something happens…
2. Intermediate action Interruptor Interromper fluxo
3. Action Target app Perform an action…
Works even better with

Boost Interruptor with other workflow features

Combine multiple resources to build even smarter workflows with Interruptor.

Kit de IA

Kit de IA

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

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.

Webhooks

Webhooks

Webhooks bridge the systems you use, including those that aren’t yet available in Pluga’s app library. They send and receive data through a unique URL using POST, GET, PUT, PATCH, and DELETE requests.

Frequently Asked Questions

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

  • Set up Interruptor between the WhatsApp trigger and the agent. It checks whether the incoming message came from your number (the conversation "owner") and, if so, pauses the flow for the time you define. The agent simply doesn't receive the message while the pause is active.

  • Yes. Interruptor uses a flow identifier (the customer's number, for example) to know which conversation to pause. The rest keep running normally. There's no global pause.

  • You choose: from 1 to 24 hours, or a dynamic time coming from another piece of data in the flow. The clock resets with every new message you send in that conversation. As long as you keep replying, the agent stays paused.

  • It can, but with risk: a prompt instruction is probabilistic, and the agent might ignore it or misinterpret it. Interruptor is deterministic: it's a fixed rule in the flow, not a decision made by the model. The pause happens every time the condition matches, no exceptions.

  • The same logic works with Telegram Bot. Any channel that fires a trigger on message received can use Interruptor the same way.

  • Not necessarily. The most common use today is alongside AI Agents in messaging channels, but Interruptor works with any flow where a temporary conditional pause makes sense.