DashboardSign inStart your trial

UserflowUserflow
01Integration field card

Userflow Integration & Workflow Automation

Run Userflow on autopilot. Keep the veto.

18 actions

Onboarding changes fire across your user base before you've had a chance to review who gets hit. Rills proposes each Userflow action; you decide before it goes out.

Try the approval demo

Interactive. No signup. 14 days free · approvals always free.

Powered by Composio
02. The trust layer

Most automation fires first, asks later. Rills shows you the change before it ships.

Every consequential other action from Userflow arrives on your phone first. Approve in seconds. Decline without explaining yourself. Workflows wait, paused at zero cost, until you decide.

Queue 3

USERFLOW · GROUP CLEANUP
78

Remove 18 trial users from the paid-tier onboarding group?

18 users · trial status confirmed, no upgrade in 21d

Same cohort pattern as last month's cleanup batch

3 users still have an open content session — flagged

SWIPE → APPROVE
Illustrative. Your real proposals match your data and your approval history.
  1. 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.

  2. 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.

  3. 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.

03. Overview

About Userflow automation

Onboarding flows touch every new user you have, and a bad group assignment or a deleted user record sent at the wrong moment can quietly break the experience for dozens of people before a single support ticket arrives.

When Userflow runs unsupervised

Userflow changes are quiet. They don't announce themselves, and by the time you notice something is wrong, the flow has already run for a full cohort.

  • Create or Update a User fires with stale attribute data, tagging a paying customer as a free-trial user and locking them out of the right checklist.
  • Remove a User from a Group runs on a false condition, pulling someone mid-onboarding out of the sequence they need to finish.
  • Delete a Content Session clears progress records for users who were still active, resetting their place in a tour they hadn't completed.
  • Track an Event posts a duplicate event that skews your completion metrics and triggers a redundant flow for the same user.
  • Delete a Group removes a segment that other content and user assignments still depend on, breaking downstream logic silently.

What Rills does inside Userflow

Rills watches the conditions you care about and queues a proposal whenever a Create or Update a User, Remove a User from a Group, or Delete a Content Session action is about to run. You see exactly who is affected and why before anything touches a live account.

The group change still happens; you just see it before it ships.

Why Userflow has no triggers and how Rills fills the gap

Userflow has no native event triggers, so there is nothing to start a workflow on its own. Rills compensates by running scheduled checks and responding to upstream signals from other tools in your stack.

  • A scheduled poll against List Users flags accounts whose attributes haven't been updated in a defined window, queuing a Create or Update a User proposal for your review.
  • A scheduled scan of List Content Sessions surfaces sessions older than your retention threshold and proposes Delete a Content Session only after you approve.
  • An upstream signal from your billing or CRM tool triggers a check via Get a User to confirm the record exists before Rills proposes any group or attribute change.
  • List Groups runs on a schedule to catch empty or orphaned groups and queue a Delete a Group proposal so you can approve Userflow automation changes before they affect dependent content.

This is the core category gap for onboarding tools: event-driven logic has to come from outside, and every proposed change waits for your call.

04. Actions

What Rills can do in Userflow

4 of 18 actions across reads, writes, and updates.

  1. 01

    Create or Update a Group

    Create a new group or update an existing group's information, allowing you to manage company profiles and their attributes in your onboarding flows.

  2. 02

    Create or Update a User

    Synchronize user information to Userflow by creating new user profiles or updating existing ones, automatically merging data to keep your user database current.

  3. 03

    List Users

    Retrieve a paginated list of all users in your Userflow workspace, with options to filter, sort, and include related membership and group data. Use this to get an overview of your user base and manage access across your product.

  4. 04

    Track an Event

    Record custom user actions and behaviors to track engagement and enable personalized experiences based on what your customers do in your product.

05. FAQ

Common questions about Userflow automation

How do I automate Userflow user and group management?

Rills reads your Userflow data and proposes actions like creating users, updating groups, or removing stale members. Nothing fires until you approve it. You stay in control of who gets added or deleted without doing the work yourself.

Can I get mobile approvals before Rills deletes a Userflow user?

Yes. Before Rills deletes a user or removes someone from a group, the proposed action lands in your mobile approval queue. You review it from your phone, swipe to approve or reject, and only then does anything happen in Userflow.

How do I keep Userflow content sessions and groups in sync automatically?

Rills can list, update, and delete content sessions and groups on a schedule or as part of a larger workflow. Each proposed change waits for your approval before it ships, so a bad sync job does not quietly corrupt your onboarding data.

Can I automate Userflow group cleanup without letting AI run unsupervised?

That is exactly what Rills is built for. It proposes which groups to delete or which users to remove, then waits for your call. You approve the ones that look right, reject the ones that do not, and nothing ships until you say so.

How do I automate Userflow content version management?

Rills can retrieve and list content versions across your Userflow account and propose actions based on what it finds. If a version needs to be archived or a session deleted, it queues that action for your review before touching anything.

How is Rills different from Zapier for Userflow automation?

Zapier runs the action the moment the trigger fires. Rills proposes the action and waits for you to approve it before anything ships. If you have ever had an automation delete the wrong user or wipe a group you needed, Rills is the version where that does not happen silently.

Why use Rills instead of Make for Userflow workflows?

Make builds execution chains that run end to end without stopping. Rills puts a human checkpoint between the AI decision and the real action. For Userflow automation touching users, groups, and content sessions, that checkpoint is the difference between a recoverable mistake and a support fire.

How much does Rills cost for Userflow automation?

Approvals and workflow logic are free. You only pay for real actions, meaning actual AI calls and external API work that Rills executes after you approve them. If you reject a proposed action, you pay nothing for it.

06. NEXT MOVE

Approve every Userflow change before it ships.

14 days free. No credit card. About 90 seconds to your first proposal.