Botpress Automation & Mobile Approvals
Run Botpress on autopilot. Keep the veto.
53 actions
Your Botpress bots send messages and charge invoices before you've seen the customer response. Rills proposes the action, you approve from your phone.
Interactive. No signup. 14 days free · approvals always free.
Most automation fires first, asks later. Rills shows you the change before it ships.
Every consequential payments action from Botpress arrives on your phone first. Approve in seconds. Decline without explaining yourself. Workflows wait, paused at zero cost, until you decide.
Queue 3
Charge 12 overdue workspace invoices totaling $1,847?
12 workspaces · all >45 days past due
3 have open support tickets this week
Workspace 'Acme-Corp' disputed last charge
Free to wait. Free to think.
Approvals and logic don't cost a credit. Pause a workflow for three hours or three weeks. The price is the same: zero. You only pay when something real happens: an AI call, an outbound action.
Approve from your phone in five seconds.
Swipe right when you're sure. Decline when you're not. Between meetings, mid-coffee, on the train. No dashboard to babysit, no inbox triage, and no surprise send you find out about after it's already out the door.
Routine cases graduate themselves.
Every approval feeds a confidence score for that exact workflow shape. The obvious cases (the ones you've green-lit fifty times) start running on their own. The judgment calls still come to you.
About Botpress automation
Chatbots live inside your business logic: charging, messaging, creating conversations. When a Botpress bot fires off an invoice charge at 2am because a customer's card expired, you're the one who wakes up to a support thread. The bot doesn't know it's sending a “thanks for your order” to a user who already filed a cancellation. That gap between what the AI can see and what the context actually means is where the damage lands.
When Botpress runs unsupervised
Botpress automation treats every event as a signal to act, even when the human picture says pause. The costs stack up quietly:
- BOTPRESS_CHARGE_WORKSPACE_UNPAID_INVOICES runs a batch charge on overdue accounts, including one that just disputed a previous charge.
- BOTPRESS_SEND_MESSAGE replies to a customer who's already escalated to your personal email, doubling the confusion.
- BOTPRESS_CREATE_BOT spins up a new bot for a workspace that hasn't set up its billing, running up usage you'll later have to unwind.
- BOTPRESS_UPDATE_WORKFLOW changes a live conversation flow mid-campaign, and the old logic that prevented duplicates disappears.
- LIST_WORKSPACES combined with BOTPRESS_CREATE_CONVERSATION can trigger a mass outreach to every workspace, including inactive trials.
What Rills does inside Botpress
Rills sits in the middle of these decisions. When your Botpress integration fires a charge or sends a message, Rills pauses the action and surfaces the full context on your phone: which workspace, what trigger, the customer's recent history. You evaluate the proposal, decide to approve or reject, and the action only executes if you say yes. The same works for creating bots, updating workflows, and listing integrations — any operation from the list can be flagged for human review.
The charge still happens; you just see the customer's dispute ticket first.
Why Botpress has no triggers and how Rills fills the gap
Botpress automation relies entirely on inbound events it receives (from external sources) or manual triggers you configure inside the platform. It does not expose native event hooks for internal state changes like a new invoice being generated or a bot's health degrading. Rills bridges this by running scheduled checks and upstream integration hooks:
- Polling workspaces every hour via LIST_WORKSPACES to detect billing anomalies before an automated charge hits.
- Reviewing pending invoices with List Workspace Invoices to catch duplicate line items or customer complaints from the previous day.
- Checking bot health via LIST_BOT_ISSUES to pause message send workflows when the error rate climbs — without waiting for a human to notice.
- Validating integration updates with BOTPRESS_VALIDATE_INTEGRATION_UPDATE before a broken connector changes how your bots authenticate with external services.
What Rills can do in Botpress
6 of 53 actions across reads, writes, and updates.
- 01
BOTPRESS_CREATE_BOT
Creates a new bot in your Botpress workspace with custom configurations like name, tags, and integrations. This allows you to quickly set up automated conversational agents for different business needs without manual setup.
- 02
BOTPRESS_CREATE_CONVERSATION
Initiates a new conversation thread in Botpress, allowing you to start fresh interactions with customers or users. This is essential for organizing separate discussion topics and tracking distinct customer inquiries.
- 03
LIST_CONVERSATIONS
Retrieve all chat conversations with your customers to review interactions, track engagement, and analyze communication history. This helps you understand customer needs and monitor bot performance across all conversations.
- 04
List Integrations
Retrieve a list of all available integrations in your Botpress workspace with filtering and sorting options to find exactly what you need. Use this to discover, search for, and organize integrations by type, status, or other criteria.
- 05
LIST_KNOWLEDGE_BASES
Retrieve all knowledge bases associated with your bot, with optional filtering by tags and pagination support to manage large collections efficiently.
- 06
BOTPRESS_SEND_MESSAGE
Send messages directly to users within Botpress conversations to deliver notifications, responses, or updates in real-time. This enables your bot to proactively communicate with customers or team members without waiting for them to initiate contact.
Common questions about Botpress automation
How do I automate charging unpaid Botpress workspace invoices?
You set a rule: when an invoice is overdue, Rills proposes a charge. You review the amount and the customer before it fires. Approve from your phone or wait for a better time. Nothing charges until you say yes.
Can I approve Botpress bot creation from my phone?
Yes. When someone requests a new bot, Rills proposes the creation with all settings. You get a notification on your phone. Swipe to approve or reject. No one deploys a bot without your say-so.
How do I get mobile approval before sending Botpress messages?
You configure Rills to propose every outbound message. It lands in your mobile approval queue. You review the content, the recipient, and the timing. The message ships only after you approve.
Can I review Botpress invoice charges before they go out?
Absolutely. Rills flags each unpaid invoice and proposes a charge. You see the amount, the workspace, and the history before any money moves. Approve from your phone or browser. No surprise charges.
How do I schedule Botpress workflow updates with human approval?
You define the update logic. Rills proposes the change at the scheduled time. You get a prompt to approve or postpone. The workflow never updates without your nod. You stay in control.
How is Rills different from Zapier for Botpress automation?
Zapier runs actions the moment a trigger fires. Rills holds each action in a queue for your approval. You see proposed charges, bot creations, or messages before anything ships. Approve from your phone. No auto-pilot surprises.
Does Rills support Botpress webhooks to trigger actions?
Yes, Rills can listen for Botpress webhooks. When an event comes in, it proposes the next action based on your rules. You approve or deny before it executes. Webhook-triggered automation with a human veto.
How much does Rills cost for Botpress automation?
Approvals, logic, and workflow rules are free. You only pay for real actions API calls or external operations. No hidden fees for setting up your approval queue. You decide what to spend.