When a new task is created in ClickUp, get a feature request from Savio

Each new ClickUp task makes FlowMattic read one feature request from Savio by its ID, so its details are ready for steps you add. As imported, the workflow only reads the request.

ClickUp

Savio

Download this workflow Browse more workflows

2 steps Setup ~5 min Used on 1.4k sites Productivity Free to import

The When a new task is created in ClickUp, get a feature request from Savio workflow on the FlowMattic canvas, with 2 steps across ClickUp, Savio — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

When a feature request in Savio turns into work, the task in ClickUp often lacks the context: who asked for it and what they said. This template is a building block for bringing that context across. It fetches a Savio feature request whenever a new ClickUp task is created.

The ClickUp Task Created trigger runs when a task is created. The task's details, such as its name and description, are passed on; a test run shows whether your custom fields come with them.

The Savio step runs Get Feature Request, which FlowMattic describes as retrieving a single feature request by its ID. That ID is the key setting. The step ships unmapped, so you either enter one fixed ID, which fetches the same request every time, or map the ID from the task. Mapping only works if your team stores the Savio request ID on the task, for example in a ClickUp custom field.

The workflow only reads. It changes nothing in ClickUp or Savio, and nothing uses the request until you add a step that does, such as ClickUp's Post Task Comment. Create a test task and check Task History to see what Savio returned.

Feature context on development tasks

A product team stores the Savio request ID in a ClickUp custom field and adds a comment step, so each new task shows the request's details for the developer.

Base for a request-to-task sync

A no-code builder starts from this template to learn the shape of Savio's feature request data before building a fuller ClickUp and Savio workflow.

Tracking one flagship request

A team working on one large request uses a fixed ID, so every new task in its ClickUp list can carry that request's current details in a later step.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
ClickUp Task Created
Starts the workflow when a task is created in ClickUp. The task's fields are passed on; check a test run for the custom field where you keep a Savio request ID.
Step 2Action
Savio Get Feature Request
Reads a single Savio feature request by its ID. The step ships unmapped: enter a fixed ID or map one from the ClickUp task. It only reads data, so add a later step to use the result.

What you need

FlowMatticCore
ClickUp AccountAccount
Savio AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

Create a ClickUp custom field for the Savio feature request ID and fill it when you create tasks, then map it into the Get Feature Request step.
Put a Filter between the ClickUp trigger and the Savio step that continues only when the custom field holding the Savio ID is not empty. Tasks without one then stop before the lookup.
Add ClickUp's Post Task Comment action after the Savio step and map the new task's ID from the trigger, so the request's details appear on the task.

Questions about this workflow

How does the workflow know which Savio feature request to fetch?

From the ID you give the Get Feature Request step. Enter a fixed ID or map one from the ClickUp task, such as a custom field where your team pastes the Savio request ID.

Does this change the ClickUp task or the Savio request?

No. The Savio step only reads, and the template ends there. Add a step after it, such as a ClickUp comment, to use the feature request details.

Can it find a Savio request by the ClickUp task name instead of an ID?

Not with this step, which needs the ID. FlowMattic's Savio integration also has List Feature Requests, which returns all requests, if you want to build a match on another field yourself.