Ryver
CommunicationPost chat messages, run topics and tasks, and manage teams with the Ryver REST API. Agents deliver updates into the workspace where the team already tracks the work.
What This Integration Enables
Ryver's premise is that a team should not need three products to hold a conversation, a decision, and a piece of work. Chat scrolls. Topics are threaded posts that stay put and are meant to be found again. Tasks live on a board with categories and assignees. This connector reaches all three, which means a FlowRunner agent can put a fast update in chat, file the thing that needs to survive as a topic, and open the actual work as a task on the right board, without leaving the workspace or making a person retype anything.
Then it goes a step further than most chat integrations do. This is one of the few chat connectors in the catalog that is also a directory administration surface: agents can create teams, list and change team membership, promote and demote members, invite people into the organization as members or guests, and deactivate accounts. Invite User and Deactivate User require administrator credentials, which is the platform being appropriately careful, and it is a good signal about which parts of this connector deserve a human-in-the-loop step. On New Topic and On New Task give a flow a way to react when work appears rather than when someone talks about it.
Two details save time at build. Ryver's API calls private teams "workrooms" for historical reasons, and the Chat Type dropdown handles the translation for you. And Create Task needs a task board identifier, which is not the team identifier, so resolve it first with Get Task Board.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Escalated tickets become tasks on the owning team's board
When a Zendesk ticket is escalated, the agent resolves the owning team, calls Get Task Board to find its board, picks the right category with List Task Board Categories, and creates a task with the customer, the symptom, the SLA clock, and a link back to the ticket. It also posts a short chat message in the team so the board change does not go unseen. When the ticket resolves upstream, a second flow finds the task and closes the loop. The board stays an honest picture of what the team owes.
Deployment and build events filed where they will still be readable next quarter
Routine build results go to chat, because they are disposable. Anything that changes the state of production goes into a topic instead: what shipped, which services it touched, who approved it, and the link to the run in GitHub. Six weeks later, when someone is reconstructing what changed and when, they are reading a threaded topic rather than scrolling a chat log. The agent decides which of the two a given event deserves based on rules the team set.
Onboarding that ends with the person already in the right rooms
A new hire record appears upstream. The agent calls Invite User to bring them into the organization as a member or a guest, joining them to the teams and forums their role calls for in the same step. It then sets their role on each team and posts a welcome topic in the team they will spend most of their time in. Their first day starts with the workspace already shaped around their job rather than with a request to be added to things.
Human-in-Loop Highlight
Deactivate User revokes a person's access to the entire Ryver organization. Their content is preserved, but they are locked out, and the trigger for that action is almost always a field in another system: a status column in an HR record, a termination date, a contract end. Those fields are wrong often enough to matter. A contractor gets rehired the same week. A name matches two people. A departure date is entered in advance and then moved. An agent that deactivates on rule will eventually lock a working person out in the middle of their day, and they will find out by being logged out.
So the agent does the whole job except the last step: it resolves the user, lists their teams, collects their open tasks off each board, creates a handover topic in each affected team so the work does not vanish with the account, and then stops. "The HR record for Alan Whitfield moved to departed with an effective date of yesterday. He is a member of four teams and has nine open tasks, six of them on the Implementation board. I have posted a handover topic in each team. Deactivate now, deactivate after the handover is acknowledged, or hold, because there is a second Alan Whitfield in the user list?" The admin answers, and Deactivate User runs against the account a person picked. Everything up to the revocation is work the agent should absolutely be doing. The revocation is not.
Agent Capabilities
17 actionsChat and Topics
3- Post Chat Message Posts a chat message into a Ryver team or forum, with Markdown formatting. Used for fast, disposable updates: build results, acknowledgments, and nudges that do not need to survive the week.
- Create Topic Creates a topic, a threaded post, in a team or forum. Used for anything that should still be findable later: release records, decisions, handovers, and incident summaries.
- List Topics Lists the topics posted in a team or forum, newest first, with paging. Used to check whether something has already been filed before the agent files it again.
Tasks
5- Create Task Creates a task on a task board, optionally filed into a category and assigned to one or more users. Needs a task board identifier rather than a team identifier, which Get Task Board resolves. Used to turn a ticket, a form, or a CRM record into work someone owns.
- List Tasks In Category Lists the tasks filed under a single task board category, with paging. Used for column level digests and for checking the size of a queue before adding to it.
- List Task Board Tasks Returns every task on the board attached to a team or forum, across all categories. Used for handovers, workload checks, and end of sprint reporting.
- Get Task Board Resolves the task board attached to a team or forum and returns its identifier. Used as the lookup step before any task write, because the board identifier is not the team identifier.
- List Task Board Categories Lists the categories on a task board with their identifiers and names. Used to place a new task in the right column instead of dropping it in the default one.
Teams and Membership
6- List Teams Or Forums Lists the private teams or open forums in the organization, with paging. Used to resolve a destination by name before posting or provisioning.
- Create Team Creates a new private team in the organization. Used to provision a room per project, per client, or per initiative from an upstream record.
- List Team Members Lists the membership records of a team or forum, each carrying the member's role and the linked user. Used for access reviews, and used first, because the membership record identifier is what the removal and role actions need.
- Add User To Teams Adds an existing organization user to one or more teams with the chosen role. Used for onboarding and for moves between projects.
- Remove Team Member Removes a member from a team or forum using the membership record identifier from List Team Members, not a user identifier. Used when someone rolls off work, and worth confirming when the team is where an active project is being run.
- Set Team Member Role Promotes or demotes an existing team member using the membership record identifier. Used to grant or withdraw moderator level responsibility as roles change.
Users
3- List Users Lists the users in the Ryver organization, with paging. Used to resolve a person from an upstream record, and used to catch duplicate name matches before an account level action.
- Invite User Invites someone to the organization as a member or a guest, optionally joining them to teams and forums immediately. Requires administrator credentials. Used to onboard staff and to bring a client into a guest forum.
- Deactivate User Deactivates a user in the organization, revoking their access while preserving their content. Requires administrator credentials. This is the action that locks a person out, so it belongs behind an approval rather than behind a field in another system.
Triggers
2 triggersEvent Triggers
2- On New Topic Fires when a topic is posted in the selected team or forum. Used to react to things a team decided to write down: mirror an incident summary into a tracker, notify a stakeholder outside Ryver, or start a review flow when a decision is filed.
- On New Task Fires when a task is created on the task board of the selected team or forum. Used to keep an external system in step with the board: open a matching ticket, notify an owner outside the workspace, or check the task against a policy before anyone starts it. Both triggers poll. Ryver's outbound webhooks are a private beta feature enabled through support and configured in the interface, and the API documents no call to create or delete one, so a real time trigger could not tear itself down when disabled.
Frequently Asked Questions
What can FlowRunner do with Ryver?
FlowRunner agents can run Post Chat Message, Create Topic, and List Topics in Ryver, plus 14 more actions.
Does connecting Ryver to FlowRunner require OAuth?
No. Ryver connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.
Can Ryver trigger a FlowRunner workflow automatically?
Yes. Ryver supports 2 triggers that can start a FlowRunner workflow automatically.
Start building with Ryver
$100 in credits. No card required. Connect in minutes.