download dots

💡 Turn Feature Requests Into Linear Issues with AI

A submitted request is read by an agent and the flow splits: product work is opened as an issue, a support question is answered instead.

  • Event-triggered
  • 100+ integrations
  • Branching logic
  • Schedule + monitor
UNIT · TASKADE.FLOW3 STEPS

How this flow runs

When

Form Submitted

A Taskade form is submitted. The fields become the data the rest of the flow works on. How it works

Then 1

Agent

Request Triage

Ask an agent · Taskade AI

Knows
your roadmap, your product areas and what is already planned
Remembers
which requests turned out to be duplicates or support issues

Then 2

Branch

Branch

Take the first path whose condition is true, each with its own steps. Paths are evaluated in order.

  1. 01Product request

    Create Issue

    Linear

    Add Task

    Taskade

  2. 02Support question

    Send an email

    Taskade

    Add Task

    Taskade

This agent carries its knowledge and memory between runs, and can call your other automations as its own tools. How custom agents work

Branch is a step you add in the builder, in the same list as an app step — there is no separate scripting surface. All automation actions

Build this flow with AI

Opens the builder with these steps already described. Free to start, no card.

What does this automation do?

A submitted request is read by an agent and the flow splits: product work is opened as an issue, a support question is answered instead.

What can you do with it?

  • Let anyone file a request without access to the tracker
  • Keep support questions off the product backlog
  • Open the real ones with enough context to prioritize

The Steps

This automation runs in 3 steps:

  1. When Form Submitted
  2. Then Taskade AI — Ask an agent ("Request Triage")
  3. Then Branch — Product request: Create Issue, Add Task · Support question: Send an email, Add Task

What makes this different from a Zapier-style flow?

The "Request Triage" step is not a one-off model call. It is a Taskade AI agent that knows your roadmap, your product areas and what is already planned, remembers which requests turned out to be duplicates or support issues, so every run builds on the last one instead of starting from an empty prompt.

A stateless "ask the model" step forgets everything the moment it returns. An agent keeps its knowledge and its memory between runs, carries its own tools, and can be handed work by other automations.

Who is this automation for?

Built for product teams taking requests from people without a Linear seat. A submitted request is read by an agent and the flow splits: product work is opened as an issue, a support question is answered instead.

How do you set it up?

  • Open the "Automations" tab in your workspace.
  • Click ➕ Add automation, then start from scratch.
  • Add the "Form Submitted" trigger.
  • Add the action "Ask an agent" from Taskade AI. Point it at an agent called "Request Triage".
  • Add a Branch step: Branch — Product request: Create Issue, Add Task · Support question: Send an email, Add Task.
  • Enable the toggle in the top-right corner to activate the automation.

Prefer to describe it instead? Click Build this flow with AI above and Taskade wires the trigger, the steps, and the agent for you.

Related from the blog