Skip to main content

Pro and API plans

Workflow

Chain GistCite's tools on a canvas and run them as one background job, with a record of what every step took in, produced and cost.

Published · Reviewed

Who it is for

  • Researchers and analysts who repeat the same chain
  • Content teams
  • Developers and automation builders

The problem

Each tool does one thing, and chaining them is manual: fetch a transcript, copy it out in pieces, summarise it, then send the result somewhere, the same way every time.

How GistCite solves it

A workflow is that chain saved once. Steps go on a canvas and wires carry each result to the next; a wire attaches only when the next step can take what the one before it gives. The workflow runs as a background job, shows the most it can cost before it starts, and keeps a record of every step.

Capabilities

Wire the tools together

Drag steps onto a canvas and connect them: a YouTube transcript, a document from a link or a source from your library, then plain text, chunks, an AI summary or an AI draft.

Benefit: Build the chain once and run it whenever you need it.

Build a workflow on the canvas

Decide and branch

Only if sends a result one way when a condition holds and another when it does not; Join brings the two ways back together.

Benefit: Pay for a summary only when the source is worth one.

How Only if and Join work

Send it where it goes

Save the result as a file, add the source to a project, email it to yourself, or post it to your own HTTPS address.

Benefit: The result arrives in n8n, Zapier, Make or your inbox without a copy and paste.

Every output step explained

A record of every step

Each run lists what every step took in, what it produced, its fingerprint and its units.

Benefit: Any result can be traced back to its source.

Read the Workflow guide

Benefits

  • Building and running a workflow is free; each step costs what its tool costs on its own page.
  • The most a run can cost is shown before it starts, and a spending limit stops it before it goes over.
  • A failed step stops the run and costs nothing; the steps that already worked are served from the cache on the next run.

How it works

  1. Step 1

    Start from a source

    A YouTube link, a link to a document, or a source already in your library.

  2. Step 2

    Wire the steps

    Plain text, chunks, an AI summary or draft, with Only if and Join for decisions.

  3. Step 3

    Run and trace

    A file, a project entry, an email or a webhook post, plus a record of every step's input, output and cost.

Integrations and formats

  • YouTube Transcripts
  • Document Extractor
  • AI summaries and drafts
  • Email
  • Webhooks to n8n, Zapier or Make

Security and data handling

Read the full picture on the security and compliance page.

  • A webhook step posts only to the HTTPS address you enter; nothing else leaves your account.
  • Every extraction endpoint is rate-limited per IP; signed-in use is metered against the plan's monthly quota.
  • TLS in transit; passwords bcrypt-hashed; API keys stored only as SHA-256 digests.

Evidence

  • What each step takes, gives and costs, and the limits of a run, are listed in the Workflow guide. Check this

Pricing

Plans
Pro and API
Cost per action
The workflow itself is free; each step costs what its tool costs (a transcript 1 unit, an AI summary 10 or 30).
How it is priced
Included in Pro and API plans, or with a top-up pack.

Compare the Free, Pro and API plans

Workflow questions

What does a workflow cost?
Nothing by itself. Each step costs what its tool costs on its own page, the most a run can cost is shown before it starts, and a failed step costs nothing.
How large can a workflow be?
Up to 20 steps in a workflow, 50 workflows in an account and 3 runs at a time. There are no loops or schedules yet.
Can a workflow start from a file I upload?
Not directly. Upload the document on Documents or the recording on Speech to Text, then start the workflow from it with the From your library step.
Can I send the result to n8n, Zapier or Make?
Yes. The Send to webhook step posts the result as JSON to any HTTPS address, which is how those tools receive it.

Try Workflow now

Sign in and start a Pro plan, or begin with the free tools and upgrade when you need this one.

Prefer to talk first? Contact the team · Read the API documentation