ThoughtPivotIn use internally

The AI workflow engine.

A workflow is fixed steps plus AI steps. Build it on the canvas, or have an agent author and run it from the AI client you already use, over MCP. Start it manually, from a webhook, on a schedule, or on Repeat. A schedule follows a cron timetable. Repeat runs continuously: the next run starts when the last one finishes. A human-approval step pauses the run until someone signs off.

See how a run works Workflows to start with

Closed source. In use internally at ThoughtPivot.

Example runOct 6

Vendor watch

Question / What changed with the vendors we depend on, and what should wait for a person?

Changed

2 material

Primary vendor raised list prices

The public price sheet now lists a 6% increase on the two plans we use.

Pricing page · Oct 4

Backup vendor published a new SLA

The scheduled maintenance window moved from 4 hours to 1 hour.

Status docs · Oct 5

Inferred

AI interpretation

The cost gap between primary and backup is narrowing.

Medium confidence · based on the two source items above

Approval

Human approval

Approve a note to finance before renewal?

Waiting

Hold the SLA change for the quarterly review?

Waiting

What a workflow holds

A chat can draft an answer. A workflow keeps the run.

Build it once. Read every run.

Compose the workflow from fixed steps and AI steps — on a canvas, or from an agent that can author and run it over MCP. A trigger starts it manually, from a webhook, on a schedule, or on Repeat. A schedule follows a cron timetable. Repeat runs continuously: the next run starts when the last one finishes. Where a person has to decide, a human-approval step pauses the run until someone signs off. The finished run stays open to inspect.

In use internally at ThoughtPivot. Closed source.

How a run works

The same workflow, started again

Draw it on the canvas, or have an agent author it from the AI client you already use.

Compose

Lay the blocks out visually, or have an agent author the workflow over MCP.

Trigger

Start a run manually, from a webhook, on a schedule, or on Repeat. A schedule follows a cron timetable. Repeat runs continuously: the next run starts when the last one finishes.

Approve

A human-approval step pauses the run until someone signs off.

Inspect

Open the run afterward. The steps, the sources, and the approval stay with it.

Blocks

Workflows are built from blocks.

Place them on the canvas, or have an agent define them over MCP.

Source

Read a data source.

ExampleFetch a public page, or start from a short list you paste in.

Workflow output

A source that reads the latest finished run of another workflow. No model call.

ExampleA Monday brief starts from Friday's report, and stops if that report is too old.

AI condition

Branch on AI judgment.

ExampleIf the brief names a price change, send it on for a person. Otherwise skip it.

Report

Render markdown output.

ExampleKeep a titled brief with the run, so a later step can quote it.

Prompt

Generate text with AI.

ExampleTurn a list of changes into a one-page brief.

Human-in-the-loop

Pause for human approval.

ExampleHold the brief until someone approves it or turns it down.

MCP

Call external MCP tools from written instructions.

ExampleAsk a connected tracker for the items updated this week.

Store

Get, set, delete, or list JSON by key. An expiry is optional.

ExampleLoad the ids this workflow already saw, or save them under a key that expires after seven days.

Group

Hold other blocks on the canvas. It does not run a step.

ExampleBox the research steps so the canvas stays readable.

Workflows

Workflows to start with

Patterns in use internally. A construction question can use the same shape.

Recurring research

What changed since the last run that is worth reading?

A sourced delta. What is known stays separate from what is inferred.

Approval hold

Which step should wait until someone signs off?

The run pauses on a human-approval step and resumes only after that call.

Scheduled check

What should run every Monday without someone remembering to start it?

The same workflow, triggered on a schedule. The timetable is cron. Each run stays open to inspect.

Repeat trigger

What should start again as soon as the last run finishes?

The same workflow, triggered on Repeat. It keeps going. The next run starts when the last one ends.

A construction watch

What moved in one regional market that a pursuit lead should see?

One example of the same workflow, pointed at a construction question.

Status

In use internally at ThoughtPivot.

Vran is closed source. We run it ourselves. This page is a description of the product as it is used today.

Workflows of fixed steps and AI steps. Agents can author and run them over MCP, with API access

Manual, webhook, and scheduled triggers. A schedule is a cron timetable

Repeat triggers that run continuously: the next run starts when the last one finishes

Human-approval steps that pause a run

Every run left open to inspect