An agent that watches your store, so a person sees only the exceptions.
On the schedule you set, the agent reads your Shopify store for what is out of line: stock running low, a price outside the range you set, an order that stalled. It reports what it found in one place and brings the ones that need a decision to a named person.
What the agent does
It reads and reports. Nothing in your store changes because the agent looked: it reads Shopify, sorts what it found and writes one summary. Every change is a person’s to make.
- Reads the store on a schedule
At the times you set, the agent reads Shopify: inventory levels, product prices and the orders that changed since it last looked.
- Sorts what is out of line
Stock below the level you set, a price outside the range you set, an order that has not moved in the time you set. What counts as an exception is written in the spec with you, and the agent applies that and nothing else.
- Reports what it found in one place
One message in the channel your operations team already works in: what it read, what it found out of line, and which of those need a decision.
- Brings a decision to a person
An exception that needs a decision comes to a named person with everything the decision needs: the product, the order or the price, and what the choices are. The change is that person’s to make, in Shopify.
The gate sits in front of every change to the store, and this agent stops there every time. An exception that needs a decision comes to a named person with the product, the order or the price it concerns and the choices open, and that person makes the change in Shopify.
What it touches
Your agent works in the systems your team already pays for. We connect it to each one, and the spec names every account it needs before you commit to anything.
- Shopify
The store it reads: inventory, products and their prices, and orders. The agent reads, and writes nothing back.
Where your agent lives
A person addresses your agent by name in a chat channel. A system wakes it with an event. Both lists are what Flue verifies, so you can check them.
A person reaches it in
- Slack
- Microsoft Teams
- Discord
- Telegram
- Google Chat
- SMS through Twilio
Teams needs one step that Slack does not: an Azure Bot registration and an app password stored in your project. We do that work and quote it as its own line.
An event wakes it from
- GitHub
- Linear
- Notion
- Stripe
- Shopify
- Zendesk
- Intercom
- Resend
- Salesforce Marketing Cloud
What it costs
A job we have not built before is custom work, so this one is priced at the custom door. The numbers below are floors: we read your workflow first, then name one fixed price.
The door says what a custom agent needs from you, and what the month after it goes live buys. How a custom agent is built