↗
Send from your own workflow
Trigger authorized text or interactive messages from your backend, CRM or n8n automation using a simple bearer-authenticated API.
Messaging operations without the clutter
Turn WhatsApp into a working business channel.
FluxRelay gives your team one practical control layer for connected devices, message APIs, delivery receipts, customer conversations and automation workflows — without making day-to-day operations complicated.
Device session managementREST API + webhooksDelivery/read visibility
Built for actual workflowsUse it manually from the console or connect it to n8n, your CRM, order system or custom backend.
One gateway, several business jobs.
Customer supportOrder updatesLead follow-upRemindersOperational notificationsDeveloper messaging
What the app can do
Useful features that map to real work.
The interface is organized around the tasks a business actually performs: connect, test, send, track, support and automate. No feature is buried behind a decorative dashboard.
◫
Manage connected devices
Keep sender sessions visible, check connection state and use QR or pairing-code flows from one workspace.
✓
Track delivery progress
Use WhatsApp message IDs to follow sent, delivered and read states whenever those receipt signals are available.
◎
Operate a support inbox
See customer conversations and reply from the same workspace used for message operations and device management.
⚡
Connect automations
Use API endpoints and webhooks as the messaging layer inside order, support, lead, reminder or notification workflows.
⌁
Audit what happened
Review message activity and analytics so your team can diagnose failures and understand the state of production messaging.
Scroll through the product
A control panel that stays easy to understand.
Each workspace is separated into clear jobs instead of putting every control on one screen.
Know what is live.
See connected senders, receipt state and recent activity before you start changing anything.
Fit messaging into your workflow.
Your application handles business logic; FluxRelay handles the messaging layer. This keeps automations easier to maintain.
Keep human follow-up available.
Automation should not remove visibility. The support workspace keeps customer conversations accessible when a person needs to step in.
Measure operational health.
Delivery, read and inbound activity provide useful signals for debugging and day-to-day monitoring.
Where it helps
Use the same infrastructure across different business workflows.
FluxRelay is not tied to one industry. It is useful anywhere your team repeatedly sends or receives operational WhatsApp messages.
RestaurantsOrder confirmations, pickup updates, support and status notifications.
E-commerceOrder updates, COD follow-up, customer questions and post-purchase flows.
Service businessesAppointment reminders, lead response, confirmations and follow-up messages.
AgenciesRun client messaging workflows from a controlled API workspace.
Internal teamsOperational alerts, workflow notifications and controlled outbound messaging.
For technical teams
Simple enough to test. Structured enough to automate.
Start in Message Studio, confirm the real WhatsApp result, then move the same idea into your backend or n8n flow. Keep API credentials private and let your business logic decide when messages should be sent.
01
Connect a senderPair a WhatsApp device and confirm the session is live.
02
Test your messageValidate content and interactive actions from the dashboard.
03
Call the APIUse your private bearer key from server-side code or automation.
POST /api/send-message
{
"sender": "92323...",
"recipient": "92300...",
"message": "Your order is ready."
}
→ message_id
→ tracking_url
→ connection_status
{
"sender": "92323...",
"recipient": "92300...",
"message": "Your order is ready."
}
→ message_id
→ tracking_url
→ connection_status
Operational discipline
Designed around safe, understandable controls.
Messaging infrastructure should be easy to operate without making sensitive controls casual.
Workspace-scoped controls
Device operations, API credentials and account pages stay behind authenticated workspace sessions.
Private API credentials
Use bearer credentials server-side. The interface provides copy and regeneration controls without requiring them in public pages.
Explicit destructive actions
Logout, deletion and API key regeneration remain deliberate actions instead of invisible background behavior.
Clear message-state language
Accepted, delivered and read are treated as different states so your team does not confuse submission with final delivery.
Give your business messaging a proper control layer.
Create a workspace, connect a sender, test the real flow and then integrate it into your business.