Route new requests to the right team's board

A Router reads the team each Fluent Forms request names: Design requests become ClickUp tasks, Ops requests become FluentBoards tasks, and Other requests post to Slack for someone to triage.

Fluent Forms

Router

ClickUp

FluentBoards

Slack

Download this workflow Browse more workflows

5 steps Setup ~8 min Used on 512 sites Productivity Free to import

The Route new requests to the right team's board workflow on the FlowMattic canvas, with 5 steps across Fluent Forms, Router, ClickUp, FluentBoards, Slack — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

A single internal request form is easy for colleagues, but someone then has to copy each request into the right team's tool. This workflow reads the team the requester picks and sends the request straight to that team, whether it works in ClickUp, in FluentBoards inside WordPress, or nowhere fixed yet.

The Fluent Forms trigger starts on every new submission. A Router then checks the form's team field against three values: Design, Ops and Other. Each condition is an exact match that ignores capitals, so design or DESIGN still counts as Design. The routes can't overlap, and each request follows the route its value matches. A request with any other value, such as a blank or "Graphic design", matches no route and creates nothing.

Design requests become a ClickUp task named after the subject field, with the message as the description. Ops requests become a FluentBoards task titled with the subject. Other requests post a Slack message with the requester's name and the subject, so a person can decide where it belongs.

Your form needs fields named team, subject, message and name. Use a dropdown or radio field for team whose choices are just Design, Ops and Other, with no extra words. After import, connect ClickUp, choose the FluentBoards board and pick the Slack channel.

Agency request desk

Account managers file client asks on one form. Design work lands in the designers' ClickUp space, while hosting and admin jobs go to the ops board in FluentBoards.

In-house marketing team

Staff request banners and flyers as Design, event logistics as Ops, and anything unusual as Other for the team lead to sort in Slack.

Small business back office

A shop's staff log jobs on a WordPress form, with print and layout work sent to ClickUp and stock or delivery tasks kept on a FluentBoards board.

How this workflow runs

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

Step 1Trigger
Fluent Forms New Form Submission
Starts whenever someone submits the request form in Fluent Forms. The team, subject, message and name fields are what the routes and actions use.
Step 2Logic
Router 3 paths
Sends each request down the route whose team value it matches exactly: Design, Ops or Other. The values can't overlap, so one request runs one route at most.
Step 3Action
ClickUp Create Task
On the Design route, creates a ClickUp task with the form's subject as the task name and the message as its description. Set where the task goes when you connect ClickUp.
Step 4Action
FluentBoards Create Task
On the Ops route, creates a FluentBoards task titled with the request's subject. Choose the board after import, and run a test to see the task it creates.
Step 5Action
Slack Send Channel Message
On the Other route, posts a Slack message with the requester's name and the subject so someone can triage it. Choose the triage channel when you connect Slack.

What you need

FlowMatticCore
Fluent Forms PluginPlugin
ClickUp AccountAccount
FluentBoards PluginPlugin
Slack 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.

Use a dropdown or radio field for team in Fluent Forms with the options Design, Ops and Other spelled exactly that way, since a typed answer may not match any route.
To catch blanks and unexpected values, change the Other route's condition from an exact match on Other to does not exactly match Design and does not exactly match Ops. It still can't overlap the other two routes.
Add a Slack message after the ClickUp step and after the FluentBoards step, so each team also hears about new work in its own channel.
Put the requester's name or email in the ClickUp and FluentBoards task details, so the team knows who to ask about the request.

Questions about this workflow

What happens if the Fluent Forms team field is empty or spelled differently?

Nothing is created. Each route needs the whole team value to be Design, Ops or Other, in any case, so any other value matches no route. Use fixed choices for the field, or widen the Other route's condition.

Can one request create both a ClickUp and a FluentBoards task?

Not with the imported conditions. The Router runs every route that matches, but a team value can only equal one of Design, Ops or Other, so each request runs a single route.

Do I need both ClickUp and FluentBoards?

Only for the routes you keep. If all your teams work in one tool, swap the other route's action for that tool's Create Task action.

Does the FluentBoards task include the request message?

Not as imported. Only the title is mapped, from the subject. Open the FluentBoards step after import to see what else it accepts, and map the message there if it fits.