DashboardSign inStart your trial

ParallelParallel
01Integration field card

Parallel Integration & Workflow Automation

Run Parallel on autopilot. Keep the veto.

32 actions

Web research tasks fire inside Parallel and the results go straight into your next step before you've seen what the AI actually pulled. Rills proposes each action; you approve before anything moves.

Try the approval demo

Interactive. No signup. 14 days free · approvals always free.

Powered by Composio
02. The trust layer

Most automation fires first, asks later. Rills shows you the change before it ships.

Every consequential communication action from Parallel arrives on your phone first. Approve in seconds. Decline without explaining yourself. Workflows wait, paused at zero cost, until you decide.

Queue 3

PARALLEL · FINDALL LAUNCH
72

Start FindAll Run across 23 target company URLs?

23 URLs · sourced from last week's prospect list

Same schema as Tuesday's completed run

3 URLs flagged as low-confidence domain matches

SWIPE → APPROVE
Illustrative. Your real proposals match your data and your approval history.
  1. Free to wait. Free to think.

    Approvals and logic don't cost a credit. Pause a workflow for three hours or three weeks. The price is the same: zero. You only pay when something real happens: an AI call, an outbound action.

  2. Approve from your phone in five seconds.

    Swipe right when you're sure. Decline when you're not. Between meetings, mid-coffee, on the train. No dashboard to babysit, no inbox triage, and no surprise send you find out about after it's already out the door.

  3. Routine cases graduate themselves.

    Every approval feeds a confidence score for that exact workflow shape. The obvious cases (the ones you've green-lit fifty times) start running on their own. The judgment calls still come to you.

03. Overview

About Parallel automation

Structured web research sounds controlled until you realize a task group fired, pulled data from forty URLs, and fed it somewhere before you read the summary. That's the shape of unsupervised Parallel automation, and the failure usually shows up somewhere downstream, not in Parallel itself.

When Parallel runs unsupervised

Parallel is built to move fast, and when nothing is waiting for your call, that speed works against you. A misconfigured schema or a broader-than-intended search scope ships results you'd have caught in five seconds.

  • Start FindAll Run fires a broad research sweep before you've confirmed the query scope is actually what you meant.
  • Create Task Run sends a job into execution with parameters you set last week, not the ones that fit today's context.
  • Extract Content from URLs pulls and processes pages you didn't sandbag, including ones that return junk or sensitive data.
  • Create Monitor sets up a recurring watch you intended to review first, then forgets to wait.
  • Add Enrichment to FindAll Run appends data to a live run that's already mid-flight, with no pause before the enriched output goes forward.

What Rills does inside Parallel

Rills sits between your trigger and Parallel's execution layer. When a research job is ready to go, whether that's a Start FindAll Run, a Create Task Run, or a new monitor via Create Monitor, Rills surfaces the proposed action with the parameters it would use and holds it until you decide.

The research still runs; you just see the scope before it goes out.

Why Parallel has no triggers and how Rills fills the gap

Parallel has no native event triggers, which means there's nothing in the communication and research layer to start a Rills workflow automatically. Rills compensates by letting you attach upstream signals or schedules that watch for the right moment and then propose the Parallel action for your approval.

  • Schedule a nightly check that proposes a Start FindAll Run only when new prospect names have been added to your source list since the last cycle.
  • Use an upstream form submission or CRM row update to trigger a proposed Create Task Run, so research kicks off when a deal moves stages, not on a blind timer.
  • Poll Retrieve FindAll Run Status on a loop and propose the next step, such as Add Enrichment to FindAll Run, only after the prior run has completed cleanly and you've approved the handoff.
  • Watch List Monitors on a schedule and propose Delete Monitor for any monitor that hasn't returned useful results in a defined window, so stale watches don't pile up unnoticed.
04. Actions

What Rills can do in Parallel

6 of 32 actions across reads, writes, and updates.

  1. 01

    Extract Content from URLs

    Fetch and extract relevant content from web URLs, optionally focusing on specific information or topics you care about. Perfect for gathering information from multiple sources quickly without manually visiting each site.

  2. 02

    Create Monitor

    Set up automatic monitoring of web search results for specific queries, with periodic checks on your chosen schedule to track how information changes over time. This helps you stay informed about topics relevant to your business without manual checking.

  3. 03

    List Monitors

    Retrieve all active monitors configured in your account along with their current status and settings to track what's being monitored across your systems.

  4. 04

    Start FindAll Run

    Discover and match entities across your data using natural language descriptions, with support for custom filters and automated notifications when results are ready.

  5. 05

    Create Task Run

    Initiates an asynchronous task execution that processes in the background, allowing you to queue work without waiting for immediate completion. Ideal for handling time-consuming operations while keeping your workflow responsive.

  6. 06

    Retrieve Task Run Result

    Waits for a task to finish executing and retrieves its final result, blocking until completion or timeout. Essential for workflows where you need to ensure a task completes before proceeding with dependent actions.

05. FAQ

Common questions about Parallel automation

How do I automate Parallel search tasks without letting AI go rogue?

Rills queues every proposed Parallel search or task run for your review before anything executes. You see what the AI wants to do, why it flagged it, and you decide whether it goes. Nothing fires until you say so.

Can I get mobile approvals before Parallel task groups are created?

Yes. When Rills proposes creating a task group or starting a FindAll run, the action sits in your mobile approval queue. You review it from your phone, swipe to approve or reject, and only then does Rills act. No dashboard babysitting required.

How do I set up Parallel automation for content extraction without missing bad outputs?

Rills monitors proposed content extractions from URLs and flags anything that looks off before it ships downstream. You approve the action from your phone, so a misfire does not quietly corrupt a report or a client deliverable you haven't seen yet.

Can Rills automatically run Parallel monitors and alert me before results go anywhere?

Rills can create and list monitors in Parallel, then hold the results for your approval before they feed into any next step. If the output looks wrong, you kill it there. If it looks right, one tap sends it through.

How do I schedule Parallel task runs so they don't fire at the wrong time?

Rills lets you set conditions and schedules for Parallel task runs, but the actual execution waits for your sign-off unless you've already told Rills that specific routine is safe to handle on its own. Confidence scoring learns which tasks you always approve and can graduate those to autonomous over time.

How is Rills different from Zapier for Parallel automation?

Zapier executes actions the moment conditions are met. If the AI gets it wrong, it already shipped. Rills proposes the Parallel action first and waits for your approval before anything runs. You keep the veto on every step that matters, and you approve from your phone, not a desktop dashboard.

Does Rills support Parallel task run events and streaming outputs?

Rills can stream task run events and retrieve task run inputs and event groups from Parallel. Those outputs get routed into your workflow, but any action they trigger still goes through your approval queue before it executes. You see the data; you decide what happens next.

How much does Rills cost for Parallel automation?

Approvals and all workflow logic are free. You only pay for real actions, meaning the AI calls and external API work that actually execute. If a Parallel task run never gets your approval, you're not charged for it. The cost scales with what you actually ship, not with what Rills proposes.

06. NEXT MOVE

Approve every Parallel change before it ships.

14 days free. No credit card. About 90 seconds to your first proposal.