Back to homeA Fluxo rule is three things: a trigger, an optional condition and an action. It answers a direct message or replies to a comment in about a second, and captures the lead while it is there. Every automated message is checked against Meta's messaging policy before it goes out — and a message that fails a check is skipped, not queued, not retried, not forced.
You build the top half. The bottom half is not a setting, because Meta's messaging policy is not a setting — and losing API access would take the product with it.
A blocked send is logged and dropped. It does not queue and it does not retry. Meta's Human Agent tag, which extends the window to seven days, can only be attached by a human pressing send — the automation is structurally incapable of using it.
Simulated — an illustration of the rule builder and the guardrails around it, not a real conversation.
Trigger on an inbound DM or a comment on your post. Match everything, or a list of keywords you write. On DMs you can add a gate that asks for an email before anything is handed over. The action is a reply, a captured lead, or both — and a comment rule replies in public, on the comment itself.
Rules run in priority order, oldest first on a tie. The first one that matches acts and evaluation ends there, so one person can never collect two automated replies from one message. Group rules under a campaign and pausing that campaign switches all of them off together.
Queue a post and the worker checks every minute: it creates the media container, polls until Instagram reports the upload finished, then publishes. The daily publishing allowance is read live from Meta rather than hardcoded, so when you are at the limit the post waits for the next window instead of failing.
Most Instagram automation gets accounts restricted because it does the three things below. Fluxo cannot do them, which is the point.
Fluxo cannot message someone who has not messaged you. The send path reads the conversation's last inbound timestamp and refuses without one, and there is no route around it. There is no broadcast, no bulk send and no list upload anywhere in the product.
Campaigns group rules together and attribute the messages and leads those rules produce, so you can measure a launch as one thing. A campaign sends nothing by itself. Nothing in Fluxo sends on a schedule, to a list, or to anyone who has not just written to you.
Reply text goes out exactly as you typed it. There is no generated copy, no model in the send path and no rewriting in your voice. If a reply reads badly, that is fixable in one place — the rule.
Fluxo is not open yet. Leave your details on the home page and you will hear the moment it is.
Notify me on launch