Agent setup guide
Feature Request Router
Every #feedback message counted on the roadmap: customer plan and ARR from HubSpot, added to the matching Notion item or a new Triage item, with a link in the thread.
What it does
Every #feedback message counted on the roadmap: customer plan and ARR from HubSpot, added to the matching Notion item or a new Triage item, with a link in the thread.
- Starts within seconds of a new message in your Slack #feedback channel.
- AI pulls out the request, the problem behind it, the customer and urgency (customer quotes are treated as untrusted text).
- Finds the customer's company in HubSpot for plan and ARR, and reads up to 100 items of your Notion roadmap.
- Adds the customer, their words, plan and ARR to the matching roadmap item, or creates a new item with Status Triage for the PM.
- Replies in the Slack thread with the roadmap link.
What it needs
- A paid plan (agents run live on paid plans).
- An AI provider key (Settings → AI Providers).
- Slack, HubSpot and Notion, connected in Settings → Integrations, and a Notion roadmap database.
What it doesn't do
- It never promises dates, priority or that something will be built.
- It matches against the titles and properties of up to 100 roadmap items; the PM triages new items and merges duplicates.
- It doesn't reply to customers, only to your teammate in the thread. Bug reports are skipped.
Availability and plans
Available
Its workflow is built and tested, and every app it needs is live. You can get it and set it up now.
Included free on the Enterprise plan; on other paid plans it's a one-time purchase per workspace (the price is on the Agents page). The Agents page in the app always shows its current status.
Before you start
- A paid plan: agents run live, and the Free plan only runs Dry Runs.
- An AI provider key (OpenAI, Anthropic, Google and more) in Settings → AI Providers. AI usage is billed by your provider.
- These apps, connected in Settings → Integrations: Slack, HubSpot and Notion.
- The app it watches, connected in Settings → Integrations (the agent starts from an app event).
- About 20 minutes.
Set it up step by step
Get the agent first (buy it, or it's already yours when your plan includes it), then in Agents → My agents press “Set up this agent”. That creates the agent's workflow in your workspace (it counts towards your plan's workflow limit) and opens the canvas with a setup checklist above it. Each item links to the exact place to go and ticks itself off when it's done.
1. Connect your AI provider
The AI steps run on your own key (OpenAI, Anthropic, Google and more). Add one in Settings → AI Providers.
2. Connect Slack
Connect the Slack workspace with your feedback channel (Settings → Integrations → Slack).
3. Connect HubSpot
Connect your HubSpot account (Settings → Integrations → HubSpot).
4. Connect Notion
Connect Notion and share your roadmap database with the Fluxo Flow integration (Settings → Integrations → Notion).
5. Pick the feedback channel
Open the trigger and pick your Slack account and #feedback channel.
| Setting | What to enter | In step |
|---|---|---|
| Slack account (#feedback) | The Slack workspace with your feedback channel. Pick your connected Slack account. | “New message in #feedback” |
| Feedback channel | The channel teammates post customer requests in, e.g. #feedback. Invite the app first (/invite @Fluxo Flow). | “New message in #feedback” |
6. Describe your product and roadmap
Open “Pull out the request” and “Match it to the roadmap” and replace the placeholder in each with the same rules.
| Setting | What to enter | In step |
|---|---|---|
| Your product and urgency rules | Replace the placeholder with your product, HubSpot plan and ARR property names, how your roadmap is organised, what counts as urgent and how thread replies should sound. It starts as “[PASTE YOUR PRODUCT NAME, THE HUBSPOT PROPERTY NAMES FOR PLAN AND ARR, HOW YOUR ROADMAP DATABASE IS ORGANISED (TITLE AND SUMMARY PROPERTY NAMES), WHAT COUNTS AS URGENT AND HOW THE BOT SHOULD SOUND IN THREAD REPLIES HERE]” until you replace it. | “Pull out the request” |
| Your rules (matching) | Paste the same rules again, so matching knows your property names and reply voice. It starts as “[PASTE YOUR PRODUCT NAME, THE HUBSPOT PROPERTY NAMES FOR PLAN AND ARR, HOW YOUR ROADMAP DATABASE IS ORGANISED (TITLE AND SUMMARY PROPERTY NAMES), WHAT COUNTS AS URGENT AND HOW THE BOT SHOULD SOUND IN THREAD REPLIES HERE]” until you replace it. | “Match it to the roadmap” |
7. Pick HubSpot and the properties
Open “Find the company in HubSpot”, pick your account and list the company properties to read.
| Setting | What to enter | In step |
|---|---|---|
| HubSpot account | The HubSpot account with your customer companies. Pick your connected HubSpot account. | “Find the company in HubSpot” |
| HubSpot company properties to read | A JSON list of the company properties to return, including your plan and ARR properties, e.g. ["name", "domain", "plan_tier", "arr"]. | “Find the company in HubSpot” |
8. Pick the roadmap database
Open “Read your roadmap”, “Add the customer to the item” and “Create a Triage item” and pick your Notion account and roadmap database.
| Setting | What to enter | In step |
|---|---|---|
| Notion account (roadmap) | The Notion workspace with your roadmap database. Pick your connected Notion account. | “Read your roadmap” |
| Roadmap database | Your roadmap database: Name (title), Status (select with a Triage option), plus any summary property; the agent reads titles and properties of up to 100 items. | “Read your roadmap” |
| Notion account (add to an item) | The same Notion account, to add the customer to a matching item. Pick your connected Notion account. | “Add the customer to the item” |
| Notion account (new Triage item) | The same Notion account, to create Triage items. Pick your connected Notion account. | “Create a Triage item” |
| Roadmap database (same one) | The same roadmap database, where new Triage items are created. | “Create a Triage item” |
9. Pick Slack for the thread replies
Open both “Reply in the thread” steps and pick your Slack account.
| Setting | What to enter | In step |
|---|---|---|
| Slack account (thread reply) | The same Slack workspace, to reply in the thread. Pick your connected Slack account. | “Reply in the thread” |
| Slack account (thread reply, new item) | The same Slack workspace again. Pick your connected Slack account. | “Reply in the thread” |
10. Test it with Dry Run
Press Dry Run: the agent runs on sample data with no messages sent and nothing written to your apps.
11. Switch the trigger on
Open the trigger and press “Activate app trigger”: from then on each new #feedback message is routed.
How it works
The agent is a normal workflow with 14 steps (2 AI steps). You can open, edit and monitor it like any other workflow.
- New message in #feedback — Starts on “New message in channel (instant)” in Slack (an app event). Starts within seconds of a top-level message in your feedback channel (where sales, success and support post what customers ask for). The app's own messages never start it.
- Pull out the request — AI step (runs on your AI provider key). AI pulls out the request, the problem behind it, the customer (company, domain or email), how urgent it is and the customer's own words.
- A feature request? — Decision: picks the branch to follow. Chatter and bug reports are left alone; requests without a named customer skip the HubSpot lookup.
- Not a feature request — Kept in the run history. Branch: Not a request. The run history keeps the message and why it was skipped.
- Find the company in HubSpot — HubSpot: Find records. Branch: Customer named. Looks up the customer's company in HubSpot by domain (or name) for its plan and ARR.
- Read your roadmap — Notion: Query a database. Branch: No customer. Reads up to 100 items from your Notion roadmap database.
- Match it to the roadmap — AI step (runs on your AI provider key). AI compares the request with your roadmap items' titles and summaries: it adds to an existing item when it's the same need, or proposes a new one for triage.
- Existing item or new? — Decision: picks the branch to follow. Matches add the customer to that roadmap item; new needs get a Triage page for the PM.
- Add the customer to the item — Notion: Add content to a page. Branch: Existing item. Appends the customer, plan, ARR, urgency and their words to the matching roadmap item.
- Reply in the thread — Slack: Reply in a thread. Replies under the #feedback message with the roadmap item's link.
- Added to the roadmap item — Kept in the run history. The run history keeps the match and the reply.
- Create a Triage item — Notion: Create a page in a database. Branch: New. Adds a new item to your roadmap database with Status Triage, the need, the customer and their words.
- Reply in the thread — Slack: Reply in a thread. Replies under the #feedback message with the new Triage item's link.
- New item for triage — Kept in the run history. The PM triages it in Notion.
Test it with Dry Run
Press Dry Run in the canvas. The agent runs on the sample data stored on its trigger (the “Sample data for Dry Run” box), so you can check every step's output before anything is live. The sample has the same shape as a real event from the app.
Sample data fields
text, user, ts, thread_ts, channel, subtype, bot_id, team_id, event_id.
- Nothing is sent or written: app actions, emails and Slack posts are simulated, and AI steps don't call your AI provider.
Go live
- Open the trigger and press “Activate app trigger”: from then on each new #feedback message is routed.
- Activating the app trigger needs the trigger's connected account. The first check only remembers what's already there, so older items don't start runs; the same item never starts two runs.
- The setup checklist adds a “paid plan” item before activation: live runs need a paid plan (the Free plan only runs Dry Runs).
- When every checklist item is done and the trigger is on, the checklist says “Live — this agent is running”. Follow its runs in the workflow's History tab and in Analytics → Agents.
Questions
How does it match?
It compares the request with the titles and properties of up to 100 roadmap items and only matches the same underlying need. Everything else becomes a Triage item, so nothing is lost; the PM merges duplicates.
Where do plan and ARR come from?
From your HubSpot company record, found by the customer's domain or name. List the property names (e.g. ["name", "domain", "plan_tier", "arr"]) in “Find the company in HubSpot”.
Will it tell customers when something ships?
No. It never promises dates or that something will be built; it only logs demand and replies to your teammate in the thread.
Troubleshooting
- “No AI provider connected” or a rejected key: connect or fix the key in Settings → AI Providers, then press Test there.
- A checklist item stays unticked: the setting is still empty or still contains its placeholder text. Open the step from the checklist and fill it in.
- An app step fails with “Needs reconnect”: the account's access was revoked or expired. Reconnect it in Settings → Integrations.
- Slack says the app isn't in the channel: in Slack, type /invite @Fluxo Flow in that channel (always needed for private channels).
- No runs start: activate the app trigger with a connected account. Only items created after activation start runs.
- A step failed: open the run in History and check that step in the Trace tab for the error and what it received.
Generated from the agent's own workflow, so it always matches what the agent does. Last updated .