# Run pipelines

Forms are a great way to extend pipelines with dynamic inputs by the end user. Pipelines can be triggered by manual interactions and automated (scheduled) actions alike.

## Run a pipeline once

Run a pipeline with your input data, make it available to your team, surpass complex problems with the flexible manual pipeline execution:

{% content-ref url="/pages/ytmg6K0gCHQ8vDF1ONW3" %}
[Manual execution](/pipeline-forms/user-guides/user-guide/run-pipelines/manual-execution.md)
{% endcontent-ref %}

## Recurring execution

Schedule recurring pipelines, edit and manage schedules, take advantage of infinite possibilities:

{% content-ref url="/pages/aL05L1kG2ZnxziBYGHhX" %}
[Schedule a Form](/pipeline-forms/user-guides/user-guide/run-pipelines/schedule-a-form.md)
{% endcontent-ref %}

## Execution history

See what has been executed:

{% content-ref url="/pages/92Fwh5qAcLACKcYe5sBN" %}
[Audit logs](/pipeline-forms/user-guides/user-guide/audit-logs.md)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.meta-inf.hu/pipeline-forms/user-guides/user-guide/run-pipelines.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.