Skip to content
One platform. From customer conversation to completed work.Take a closer look
All connections
Messaging · CONNECTION

Matrix + NodeHub

Send and remove messages, read rooms and manage membership on a Matrix homeserver.

Explore 15 workflow actions for Matrix, including account permissions and operation limits.

7 read actions8 write actions
WORKFLOW ACTIONS

What you can configure.

Choose an action in the workflow builder, connect an account, and map its inputs. These actions are available in the catalog; your account access and a successful test determine whether they work for your setup.

Create room

Write

Create a room, optionally inviting people.

Permissions and limits

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

  • Rooms are created unencrypted so NodeHub can post to them. A lost answer remains uncertain: creating again would make a second room.

A repeated request may repeat the external action. Review the previous result before retrying a write.

Download file

Read

Download one Matrix content URI into this workflow's protected business file store.

Permissions and limits

Account permissions

  • Access to the media through the connected homeserver

Operation limits

  • Uses Matrix's authenticated media endpoint and stores at most 16 MB. At most two public HTTPS redirects are followed; the access token is removed when a redirect leaves the homeserver. This operation accepts an unencrypted event URL only and cannot decrypt encrypted Matrix file metadata.

Get account

Read

Read the user ID and device of the connected account.

Permissions and limits

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Get event

Read

Read one event of a room by its ID.

Permissions and limits

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

  • Encrypted message content cannot be read.

Get room state

Read

Read the current state events of a room the account may access.

Permissions and limits

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

  • Returns current room state. Event content depends on each event type.

Invite user

Write

Invite a person to a room.

Permissions and limits

Account permissions

  • Power level to invite

A repeated request may repeat the external action. Review the previous result before retrying a write.

Join room

Write

Join a room by its ID or alias.

Permissions and limits

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

  • Joining twice is harmless.

A repeated request may repeat the external action. Review the previous result before retrying a write.

Leave room

Write

Leave a room the account has joined.

Permissions and limits

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

  • Rejoining a private room needs a new invite.

A repeated request may repeat the external action. Review the previous result before retrying a write.

List joined rooms

Read

Read the IDs of the rooms the account has joined.

Permissions and limits

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

List messages

Read

Read one page of a room's events, newest first by default.

Permissions and limits

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Operation limits

  • Encrypted message content cannot be read.

Pagination: cursor. Check the result for additional pages; a single action may not return every record.

List room members

Read

Read the joined members of a room with their display names.

Permissions and limits

Account permissions

Depends on the connected account and selected operation. Check the service documentation.

Remove message

Write

Redact (remove) an event, such as a message, from a room.

Permissions and limits

Account permissions

  • Power level to redact the event

Operation limits

  • The event stays in the room's history as removed; its content is gone.
  • NodeHub sends the step's idempotency key as Matrix's transaction ID, which the homeserver uses to recognize a repeat of the same request. A lost answer still remains uncertain and is never resent automatically.

A repeated request may repeat the external action. Review the previous result before retrying a write.

Remove user

Write

Remove a person from a room.

Permissions and limits

Account permissions

  • Power level to kick

A repeated request may repeat the external action. Review the previous result before retrying a write.

Send file

Write

Upload one protected workflow file and send it to an unencrypted room.

Permissions and limits

Account permissions

  • The account has joined the room and may upload content and send messages

Operation limits

  • Files must belong to this business, be at most 16 MB, and are sent as m.file. Encrypted rooms are refused before file upload because NodeHub does not hold encryption keys.
  • Upload and message delivery are one single-attempt workflow action. A lost upload or message receipt is uncertain and NodeHub never repeats it automatically. If Matrix accepts the upload but rejects the message, the unreferenced upload can remain in the homeserver's media repository.
  • NodeHub sends the step's idempotency key as Matrix's transaction ID, which the homeserver uses to recognize a repeat of the same request. A lost answer still remains uncertain and is never resent automatically.

A repeated request may repeat the external action. Review the previous result before retrying a write.

Send message

Write

Post a text message to a room the account has joined.

Permissions and limits

Account permissions

  • The account has joined the room and may send messages

Operation limits

  • Plain text only; formatted HTML is not offered. Messages to encrypted rooms are refused: NodeHub does not hold encryption keys.
  • NodeHub sends the step's idempotency key as Matrix's transaction ID, which the homeserver uses to recognize a repeat of the same request. A lost answer still remains uncertain and is never resent automatically.

A repeated request may repeat the external action. Review the previous result before retrying a write.

SETUP

Start with a controlled test.

01Connect the intended account

Use the account and permissions required for your process. Review the connection check before configuring a workflow action.

02Review inputs and access

Select a listed operation and map its required inputs. Use test records and add a human approval before writes that need review.

03Confirm the result

Inspect step outputs and confirm the result in Matrix. A saved workflow is not a completed provider action.

Follow the workflow quickstart
EXPLORE YOUR STACK

More in Messaging.

Matrix integration | NodeHub