# Run App Actions in a Workflow

A **Plugin** step performs a configured app action. Use it when a repeatable
workflow needs a specific operation such as creating a file or reading a table.
A connector instead imports source content into Knowledge.

## Pick an Explicit Operation

Use a Plugin step when the workflow should perform one known app operation, with fields you can review before the run. An Agent step can reason about the task; a Plugin step makes the chosen operation and its inputs explicit.

For a launch checklist, first inspect the agent’s text, then pass that text into the create-file action. An empty content field can create an empty file even when the step succeeds. A connector serves a different purpose: it imports selected source content into Knowledge rather than performing that one workflow operation.

![The graph editor has a step palette and a configured Agent connected to Output.](/screenshots/current/workflow-graph-editor.png)

## Before you start

The plugin must be available in your deployment, enabled for the work, and
connected to an account that can access the target. Organization-managed sending
accounts can require an administrator’s setup. Available workflow actions can
be a subset of the plugin’s thread tools.

## Configure an action

1. Add a **Plugin** step in the workflow editor.
2. Choose a plugin and one of the actions offered by the picker.
3. Select the intended connected account where the configuration offers one.
4. Fill every required field with fixed input or a valid upstream reference.
5. Check the destination resource and any recipients.
6. Wait for **Saved**, run the workflow, and handle requested approvals.
7. Open the returned result in the destination app and inspect its contents.

For a Drive file action, choose a descriptive file name and use the agent’s
completed checklist as the content. A folder URL and a folder ID
are not interchangeable unless the field explicitly accepts both.

## Troubleshoot

If an action is missing, check the current picker and administrator configuration.
For authorization or not-found errors, confirm the selected account and exact
resource. If the outcome is unknown, inspect the external app before rerunning
a write. A successful connection is not proof that the action succeeded.

Related: [approvals](/threads/approvals/) and [run results](/workflows/results/).
