> ## Documentation Index
> Fetch the complete documentation index at: https://parabola.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Run and schedule

> Run a flow by hand, or let a schedule, webhook, or inbound email start it for you.

A flow doesn't have to wait for you to open it. Run it by hand when you need it now, or let a schedule, a webhook, or an inbound email start it without you.

There are four ways to run a flow: manually, on a schedule, triggered with a webhook, or triggered with an email attachment.

<div className="docs-figure-sm">
  <Frame>
    <img src="https://mintcdn.com/parabola-7119dfb0/uIqbmf7B5bgC4gZQ/images/run-and-schedule-run-flow-panel.png?fit=max&auto=format&n=uIqbmf7B5bgC4gZQ&q=85&s=f1cb5aadc8da60e025f4624ae609a877" alt="The Run Flow panel listing the flow's destinations, with a Run Flow button and a note that running flows uses credits" width="886" height="966" data-path="images/run-and-schedule-run-flow-panel.png" />
  </Frame>
</div>

## Run manually

Click **Run flow** in the top right of your canvas, or the **Run flow** button in the flow dashboard.

<div className="docs-figure-sm">
  <Frame>
    <img src="https://mintcdn.com/parabola-7119dfb0/uIqbmf7B5bgC4gZQ/images/run-and-schedule-triggers-panel.png?fit=max&auto=format&n=uIqbmf7B5bgC4gZQ&q=85&s=61b7019e24807f32873b3d368225c003" alt="The Schedules / Triggers panel offering Add a recurring schedule, Add an inbound email trigger, and Add a webhook trigger" width="868" height="688" data-path="images/run-and-schedule-triggers-panel.png" />
  </Frame>
</div>

## Run on a schedule

Schedule a flow to run automatically from the published flow page by adding a scheduling rule. Set it to run on a certain day of the month, once a day, every hour, every 30 minutes, or as often as every 10 minutes (depending on your plan). You can specify which days of the week, what time, and which time zone to use.

Open the **Schedules / Triggers** panel to see the rules you've set, either by:

* Clicking **Add schedules/triggers** beneath the flow's name, or
* Clicking the lightning bolt in the upper-right corner

From the panel you can:

* **Edit a schedule.** Click the pencil icon next to it.
* **Remove a schedule.** Click **Remove this trigger**.
* **Pause or resume.** Use **Pause existing flow schedules** and **Resume flow schedules** at any time.

<div className="docs-figure-sm">
  <Frame>
    <img src="https://mintcdn.com/parabola-7119dfb0/uIqbmf7B5bgC4gZQ/images/run-and-schedule-webhook-config.png?fit=max&auto=format&n=uIqbmf7B5bgC4gZQ&q=85&s=1b9faf9763e3d84247ec19f46566c7f3" alt="The Configure webhooks dialog with the trigger URL, a chart of successful and failed invocations over the last 7 days, and a Remove this trigger action" width="916" height="699" data-path="images/run-and-schedule-webhook-config.png" />
  </Frame>
</div>

## Trigger with a webhook

Users on Team and Advanced plans can trigger a flow with a webhook. From the flow dashboard, under the **Schedules / Triggers** panel, select **Add a webhook trigger**. A pop-up gives you a webhook URL to copy into the external service that should trigger the flow. A graph shows successful and failed webhook invocations from the last 7 days.

<div className="docs-figure-sm">
  <Frame>
    <img src="https://mintcdn.com/parabola-7119dfb0/uIqbmf7B5bgC4gZQ/images/run-and-schedule-email-trigger.png?fit=max&auto=format&n=uIqbmf7B5bgC4gZQ&q=85&s=ca76d3842917d07aa27839fb5705f528" alt="The Email trigger settings dialog with the flow's inbound address, attachment requirements, and a choice between running once per email or once per attachment" width="1076" height="1398" data-path="images/run-and-schedule-email-trigger.png" />
  </Frame>
</div>

## Trigger with an email attachment

From the **Schedules / Triggers** panel, select **Add an inbound email trigger** for a dedicated email address. When we receive a CSV or XLS file at that address, we run your flow automatically.

### Managing a queue of triggered runs

Flows with email or webhook triggers can accumulate a queue of pending runs (up to 1,000). The Run History panel shows how many are pending, and you can manage the queue by pausing new runs, pausing execution of queued runs, or clearing all pending runs.