Visual automation, no ceiling

Build automations visually
with unlimited power.

Task Plumber lets you lay out workflows on a canvas, connecting triggers, apps, routers and loops, and pipe data between them. Underneath sits an engine with no operation caps and parallel execution, and you can write your own apps when the built-in ones aren't enough.

Webhook Parallel Add a row Send an email Update contact

No operation caps

Run it on your own infrastructure. Nobody meters your steps, so a loop over 100,000 rows is just a loop.

Parallel by design

Fan work out across routes or items with bounded concurrency and rate limits, then merge it back.

Bring your own apps

Wrap any HTTP API as a custom app with its own modules, connections and OAuth, in a format you may already know.

Everything you need to move data around

Point-and-click where that's quicker, with full control underneath when you need it.

A real canvas

Drag modules in, wire them up, add routers, filters and error handlers. What you see is exactly what runs.

Expressions that keep up

Map fields with a fast expression language built in Rust, with around 80 functions for text, dates, math and arrays.

Connections handled

OAuth, API keys and tokens live in one credentials store, are verified live, and are reused across every scenario.

Run history you can read

Every run keeps each module's input and output bundles, so you can see where the data went wrong.

Webhooks, schedules, APIs

Trigger scenarios from incoming webhooks or a schedule, or from your own code with API tokens.

Yours to host

One container, your servers, your data. No vendor between your systems and your automations.

Plumb it in three steps

  1. 1

    Lay the pipe

    Start from a trigger, then add the apps and logic you need. Routers split the flow, iterators fan it out and aggregators bring it back together.

  2. 2

    Map the data

    Click into any field and pull values from earlier modules. When clicking isn't enough, transform them with expressions.

  3. 3

    Turn on the tap

    Run it once to watch every bundle flow through, then schedule it or point a webhook at it and let it go.

Already built it in Make?

Bring your scenarios with you. Task Plumber runs Make.com blueprints and custom apps in Make's app format, and handles connections the same way. Import a scenario, reconnect your accounts and run it, without rebuilding anything.

Then go further than Make does, for example with parallel routes and iterators.

// a Make blueprint, as-is
{ "name": "New lead → CRM",
  "flow": [
    { "module": "gateway:CustomWebHook" },
    { "module": "builtin:BasicRouter",
      "routes": [ … ] }
  ] }

// plus Task Plumber's own modules
{ "module": "taskplumber:ParallelIterator",
  "parameters": { "concurrency": 8 } }

Stop babysitting your integrations.

Build them visually and run them anywhere, at whatever scale you need.

Start building