Xata Organization Automation & Approvals
Run Xata on autopilot. Keep the veto.
8 actions
Rills queues Xata organization updates and API key changes for human approval before they run, and records who approved each one.
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 data & storage action from Xata arrives on your phone first. Approve in seconds. Decline without explaining yourself. Workflows wait, paused at zero cost, until you decide.
Queue (3)
Update organization to add 2 instance types in eu-west-1?
Current project usage at 82% of limits in us-east-1
eu-west-1 instance types are 20% cheaper for same spec
No similar changes in past 30 days, so review needed
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.
Clear runs stop waiting on you.
Every run is scored against your review step. The ones that clearly match your judgment run above your threshold without a tap; the borderline ones still come to the queue. Autonomy is earned run by run, never switched on for good.
About Xata automation
A resource limit change or an API key rotation ships while you're away from the dashboard, and you don't find out until a service breaks. Xata infrastructure decisions are too sharp to leave unsupervised in any project management stack.
When Xata runs unsupervised
Without a review step, Xata operations fire off changes that ripple through your projects and your billing.
- Update Organization: a misconfigured setting alters billing profiles or access controls before anyone double-checks.
- List Organization API Keys: a stale key is rotated out, breaking integrations that rely on it, with no warning.
- List Available Regions: a new region is added to a project without confirming that it's needed, driving up costs.
- List Instance Types: an instance type is switched to a higher tier, and the monthly bill jumps before you notice.
- Get project resource limits: limits are hit silently, and the next deployment fails because no one was alerted.
What Rills does inside Xata
Rills watches your Xata organization settings, API keys, and resource limits. When a change is proposed—like updating an organization, rotating keys, or adding a region—it queues the action for your approval, not your dashboard. This is the Xata automation layer that keeps you in control.
The change still happens; you just see it first, from your phone.
Why Xata has no triggers and how Rills fills the gap
Xata itself doesn't fire events when organization settings change or when API keys are about to expire. Rills bridges that gap with scheduled checks and upstream signals.
- Update Organization: Rills polls organization details daily, flags unexpected billing or access changes, and proposes a rollback before you're surprised.
- List Organization API Keys: it inspects key creation dates and alerts you when keys are nearing expiry, suggesting a rotation before integrations break.
- Get project resource limits: Rills queries limits and compares to current usage, then proposes a limit increase only after you approve it.
- List Available Regions: when a deployment pipeline changes infrastructure code, Rills catches the intended Xata region additions and queues them for your review.
What Rills can do in Xata
6 of 8 actions across reads, writes, and updates.
- 01
Get Organization Details
Tool to retrieve detailed information about a specific organization by its ID.
- 02
Get project resource limits
Tool to retrieve the default resource limits for projects in a specified organization.
- 03
List Available Images
Tool to retrieve a list of all available postgres images for a specified organization and region.
- 04
List Available Regions
Tool to retrieve a list of all regions where new branches can be deployed for the specified organization.
- 05
List Extensions
Tool to get available PostgreSQL extensions for a specific image.
- 06
List Instance Types
Tool to retrieve a list of all instance types for the specified organization and region.
Common questions about Xata automation
How do I automate Xata organization updates with approval?
Rills can propose changes to your Xata organization like updating settings or region configurations, but nothing goes through until you approve. The AI drafts the change, explains what it wants to do, and waits for your swipe on your phone. Without approval, the update never ships. This way, you avoid the 'wish I'd reviewed that' moment when a bulk change to API keys or project limits goes out.
Can I get mobile approvals before updating my Xata organization settings?
Yes. Rills lets you review proposed updates like changing your organization name, member roles, or region assignments from anywhere. You get a notification on your phone, see the AI's suggested change, and swipe to approve or reject. Nothing alters your Xata setup until you give the green light. Approvals are free, and you only pay when Rills makes the actual API call to Xata.
How do I automate Xata resource limit checks and get notified before I hit them?
Rills can list your project's resource limits in Xata on a schedule, compare them against your usage, and propose actions like adjusting limits or pausing non-critical services. But you decide: the AI flags the threshold, explains the risk, and you approve the fix from your phone. No automatic scaling without your say. You avoid the surprise bill when a misconfigured script runs up CPU credits.
Can I automatically list Xata API keys and get a review before they're exposed?
Rills can pull your Xata organization API keys and list them for review without ever exposing them. The AI proposes whether to rotate a key, deactivate an old one, or flag unused keys; you approve each action on your mobile before it executes. This gives you oversight of your security posture without manual polling. Approvals and logic are free; you only pay for the API calls to Xata.
How do I set up Xata automation that checks available regions before I deploy?
Rills can list available Xata regions for your project type and propose the best one based on latency or cost. But you still have the final say: the AI presents its recommendation, and you swipe to approve from your phone before it creates a database in that region. This prevents the mistake of spinning up a critical workload in a region you didn't intend, with no rollback button.
How is Rills different from Zapier for Xata automation?
Zapier fires actions instantly when a trigger hits. Rills inserts a human decision step: the AI proposes the Xata update, and you approve or reject it from your phone before anything ships. That means you can automate critical operations like updating organization settings or rotating API keys without the risk of an erroneous trigger wreaking havoc. Plus, Rills charges only for real actions, not f