Revolt integration

Communication · 3 actions · Bearer token auth

Revolt open-source chat platform — group management and friend requests

Put Revolt to work View Revolt integration docs

Overview

The ModuleX Revolt integration lets a ModuleX agent operate Revolt on your behalf — running create and send actions across groups, group members and friend requests — directly from a plain-English request, using your organization's own Revolt credentials. No pre-built workflow is required: the agent picks the right Revolt action for the task.

Revolt is a communication platform. ModuleX adds the agent layer: ask for an outcome and it selects and runs the right Revolt action — or, when you want a repeatable process, the composer assembles a Revolt workflow for you, streaming the nodes onto the canvas as it builds.

Ask the assistant

Drive Revolt in plain English

Type what you want. A ModuleX agent picks the right Revolt action — or chains several — and runs it. No workflow to build.

Create a new group channel
resolves tocreate_group
Send a friend request to another user
resolves tosend_friend_request

Use cases

What you can automate with Revolt

Create a group straight from a requestcreate_group
Add a group member on the flyadd_group_member
Send a friend request where it needs to gosend_friend_request

At a glance

Revolt integration at a glance

VendorRevolt

CategoryCommunication

Actions available3

AuthenticationBearer token

Uses your own credentialsYes

Works with the assistantYes

Works in the composerYes

Multi-step / tool-chainingYes

Technical referenceView docs

Integration version1.0.0

Last updatedJun 2026

Reference

All 3 Revolt actions

Groups1

create_group

Create a new group channel

Group Members1

add_group_member

Add another user to a group channel

Friend Requests1

send_friend_request

Send a friend request to another user

See full parameters and response schemas in the Revolt integration docs

Two ways

Two ways to use Revolt in ModuleX

Ask the assistantType what you want done and a ModuleX agent picks the right Revolt action and runs it — no workflow to build.

Compose a workflowNeed it to happen every time? Describe the process and the composer wires Revolt into a repeatable workflow you can run on a schedule, from chat, or as an API.

Security

Connecting Revolt

Bearer tokenRevolt uses bearer-token authentication. You provide a Revolt access token; ModuleX encrypts it and scopes it to your organization so the whole team can use Revolt.

Step-by-step setup in the Revolt docs

Pairs well with Revolt

Agents often chain Revolt with these — connect them once and the agent can use all of them in a single task.

Zoom23 actions

AgentMail21 actions

Microsoft Outlook20 actions

Telegram Bot17 actions

Twilio17 actions

Microsoft Teams12 actions

FAQ

Revolt + ModuleX FAQ

A ModuleX agent can run any of Revolt's 3 actions — across groups, group members and friend requests — from a plain-English request, using your organization's own Revolt credentials.

No. The agent selects the right Revolt action from your prompt. A workflow is only needed when you want a repeatable process — and the composer builds that for you from a description.

With your own Revolt access token, stored encrypted and scoped to your organization.

3, spanning groups, group members and friend requests.

Revolt runs on your own credentials, so any Revolt usage is billed by Revolt directly. ModuleX meters the agent run — and if you connect your own model keys, there's no ModuleX markup on model usage.

Put Revolt to work in ModuleX.

Connect Revolt once with your own credentials and let your agent run all 3 actions on demand.

Put Revolt to work View technical docs

Last updated: Jun 2026Browse all 175 integrations →