Zulip

Permanently removes a message from a Zulip stream or direct message thread, keeping your topic history clean.

Fetches the full content, sender, and metadata of a single Zulip message by ID for downstream processing.

Delivers a direct message to one or more Zulip users outside of any stream, ideal for personal alerts and sensitive notifications.

Posts a message to a named Zulip stream under a specified topic, routing information directly into the right conversation thread.

Edits the content of an existing Zulip message in place, letting the agent correct, extend, or reformat a post without deleting and reposting.

Uploads a file to Zulip's media server and returns a hosted URL that can be embedded in any subsequent message.

Creates a new Zulip stream with a specified name, description, and privacy setting, scaffolding the right communication channel automatically.

Permanently removes a Zulip stream and all its messages, used to retire obsolete project or temp channels during cleanup workflows.

Retrieves the full list of streams in the Zulip organisation, including metadata, for inventory, auditing, or dynamic routing decisions.

Returns only the streams the authenticated bot or user is subscribed to, for scoped routing that avoids acting outside the agent's authorised channels.

Modifies a Zulip stream's name, description, privacy level, or announcement setting, keeping channel metadata in sync with evolving project or team structure.

Provisions a new Zulip account for a given email address, automating seat creation during employee onboarding or external collaborator invitations.

Disables a Zulip account so the user can no longer log in, used to revoke access instantly when someone leaves or a contract ends.

Fetches a single Zulip user's profile, including their user ID, email, full name, and status, for enrichment or conditional routing.

Returns the complete list of active Zulip users with their IDs, names, and emails, enabling bulk operations or organisation-wide audits.

Modifies a Zulip user's profile fields such as full name, role, or custom attributes, keeping user data in sync with authoritative HR or directory systems.

Fires when any message is posted to a monitored Zulip stream, optionally filtered to a specific topic.

Fires when a direct message is sent to the bot's Zulip inbox, enabling command-driven workflows triggered by individual users.

Fires whenever the connected Zulip bot or user is @mentioned in any stream or topic, routing work to the agent only when explicitly summoned.

Fires when a new stream is created in the Zulip organisation, enabling automatic provisioning and governance workflows.

Fires when a new Zulip account is created or a user joins the organisation, kicking off automated onboarding sequences.

Fires when a specific emoji reaction is added to a Zulip message, enabling lightweight approval and voting workflows without forms.

Fires when a Zulip user changes their presence status or status message, enabling availability-aware routing and coverage handoffs.