> ## Documentation Index > Fetch the complete documentation index at: https://docs.fetchhive.com/llms.txt > Use this file to discover all available pages before exploring further. # Linear > Configure a workflow step that creates or queries Linear issues and teams using a connected Linear account Use **Linear** when you want a workflow step to create issues, list issues, update issues, or retrieve team information from a connected Linear workspace. ## Configuration | Option | Required | Description | | ------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Name | No | Label for the step in the workflow canvas. | | Authentication | Yes | The connected Linear account to use for this step. | | Action | Yes | The Linear action to perform (Create Issue, List Issues, Update Issue, List Teams). | | Arguments | Yes | Per-action form fields generated from the action's schema. Each text field has an **Insert Variable** button for injecting `{{placeholder}}` values. A **Raw JSON** tab is available for advanced usage. | | When the step fails | No | Controls whether the workflow should **Terminate Workflow** or **Continue** if this step fails. | Before you configure this step, connect Linear in **Integrations** for your workspace. If no active Linear connection is available, the step shows a warning with a link to **Integrations** instead of the account selector. ## Arguments form When you select an action, the **Arguments** section automatically renders a form driven by the action's input schema — no manual JSON editing required. Each field includes: * A label and description from the action's schema. * An **Insert Variable** button next to the label that injects references like `{{step_1.output.id}}` at the cursor position. * Validation feedback inline if a required field is left empty. ### Field types | Field type | How it renders | Insert Variable available | | ------------------------- | -------------------------------------------------------------------------------------- | -------------------------------------------------- | | Text / number | Plain input. | Create Issue and Update Issue only | | Boolean | Toggle switch (label on the left, switch on the right). | No | | Team (`team_id`) | Dropdown populated from your connected Linear workspace — select your team by name. | No | | Project (`project_id`) | Dropdown populated from your connected Linear workspace — select your project by name. | No | | Issue (`issue_id`) | Dropdown populated from your connected Linear workspace — select an issue by title. | No | | Label IDs / string arrays | List of text inputs. The **Add** button appears next to the array label. | No (array items do not support variable insertion) | All dropdown options are fetched in a single request when you select a connected account, so opening the settings panel does not trigger multiple API calls. If the lookup fails for a specific field, it falls back to a plain text input so you can still enter a value manually or use a `{{variable}}`. Switch to the **Raw JSON** tab for power users or when you prefer to write the full arguments object by hand. Changes in either tab stay in sync. ## Actions | Action | Description | | ------------ | ------------------------------------------------- | | Create Issue | Create a new issue in a specified team. | | List Issues | Search or list issues with optional filters. | | Update Issue | Modify an existing issue by ID. | | List Teams | List all teams in the connected Linear workspace. | ## Output This step stores the Linear API response as the step output. The shape of the response depends on the action. Use the full output reference in later steps: ```text theme={null} {{STEP_IDENTIFIER.output}} ``` For example, after a **Create Issue** step you might reference the new issue's ID: ```text theme={null} {{step_3.output.id}} ``` ## Example 1. Open **Integrations** and connect Linear if you have not already done that. 2. Add a **Linear** step to your workflow. 3. Select a connected account in **Authentication**. 4. Choose **Create Issue** in **Action**. 5. In the **Arguments** form, use the **Team** dropdown (auto-populated from your Linear account) to select a team, fill in **Title** and optionally **Description**. Use **Insert Variable** next to any field label to reference an earlier step's output — for example, `{{step_1.output}}` as the issue title. 6. Click **Run** in the step header to test the action, then review the returned payload in **Output**. {/* Add screenshot: Linear step output tab after a test run */} ## Notes * This step depends on a connected Linear integration in your workspace. * The **Raw JSON** tab in Arguments is always available if you prefer to write JSON directly. * The **Team**, **Project**, and **Issue** fields show dropdowns populated from your connected Linear workspace. If no options load, check that the integration is active in **Integrations**. * The **Update Issue** action provides an **Issue** dropdown so you can select an existing issue by title rather than entering an ID manually. ## Using Linear as an Agent Tool You can also add Linear as a tool in the **Agent Editor**. Open the agent, click **Add tool**, and select **Linear**. In the tool settings panel, choose the connected Linear account the agent should use. The agent will create, search, and update issues automatically during conversations when relevant. See also: [Integrations](../../../workspace/integrations), [Creating and Editing](../../creating-and-editing), and [Testing and Iteration](../../testing-and-iteration)