Review Onboarding User Records
Organize user attributes returned by the onboarding workspace.
/oo Userflow: List Userflow users and summarize the attributes returned for this page.
Use your application’s stable user IDs to inspect onboarding context or record an event with the attributes you supply.
Copy a prompt into your agent with the oo Skill installed. Add your page links and source notes before running it.
Organize user attributes returned by the onboarding workspace.
/oo Userflow: List Userflow users and summarize the attributes returned for this page.
Record a named event against a specified application user.
/oo Userflow: Track event [name] for user [user_id] with these event attributes: [attributes].
Set up oo CLI and the oo Skill in your agent.
Install OOMOL →Connect with your Userflow API Key.
Connect Userflow →Use /oo with the pages to read, the changes to make, and where to save the result.
Connection Guide →Choose Your Agent
Userflow stores users, groups, and events used in onboarding experiences. The assistant can work with those records through the connected workspace’s supported operations.
List Userflow users with optional cursor pagination and filters.
Track one Userflow event for a user.
List Userflow users with optional cursor pagination and filters.
userflow.list_users Fetch one Userflow user by ID.
userflow.get_user Create or update one Userflow user.
userflow.upsert_user Delete one Userflow user by ID.
userflow.delete_user Create or update one Userflow group.
userflow.upsert_group Fetch one Userflow group by ID.
userflow.get_group Delete one Userflow group by ID.
userflow.delete_group Track one Userflow event for a user.
userflow.track_event No matching tools.
Ask for a summary of returned user attributes or record a specified event for a user. Recording an event should reflect a business fact you supply; it does not verify that fact itself.
Tracking an event records it in Userflow; it does not prove that the user completed the underlying business task.
Connect a Userflow workspace API key. Use user and group IDs that match your application’s existing identifiers.
Manage which optional storage OOMOL can use. You can change these choices from the footer at any time.