Zulip n8n integrationAutomate Zulip with n8n.

Removes one message from Zulip for good, in a stream or in a private conversation. Zulip works from the numeric identifier of the message, never from its text.

• Message ID: the unique identifier of the message, usually carried over from a Get a message step or from the node that posted it, through an expression such as {{ $json.id }}.

Pulls a single message back into the workflow so the branch that follows can read its content instead of guessing it.

• Message ID: the unique identifier of the message; it comes from a spreadsheet column, a form field or an earlier node, passed as {{ $json.messageId }}.

Delivers a direct message to one person or to a handful of them, without anything appearing in a stream.

• To: the recipients, picked from the list in the node or given as a comma separated list of usernames (emails); an expression works when the address comes from a previous step.
• Content: the body of the message, written the way it should appear in Zulip.

Posts a message in a stream, under a topic. Most Zulip workflows end on this operation.

• Stream Name or ID: the destination stream, chosen from the node list or given as an ID through an expression.
• Topic Name or ID: the topic the message lands under, which Zulip only uses for stream messages.
• Content: the text itself, often assembled in a Set node just before.

Edits a message already published, its text, its topic, or both, without deleting it and posting again.

• Message ID: the message to edit.
• Content: the replacement text, set in Update Fields.
• Topic: the new topic, which Zulip only accepts on stream messages.
• Propagate Mode: changeOne touches that message only, changeLater also moves the ones sent after it in the same topic, changeAll takes them all.

Sends a file carried by the workflow up to Zulip. The file arrives as binary data from the node before, a download, an export or a generated document.

• Put Output File in Field: the name of the binary field that carries the file, matching whatever the previous node used for its binary output.

Opens one or more streams and subscribes accounts to them in a single call, which is why the node asks for a list rather than one name.

• Subscriptions: the streams to subscribe to, each with a Name and a Description; a stream that does not exist yet is created.
• Invite Only: keeps the stream private, while History Public to Subscribers decides whether newcomers can read what was said before they joined.
• Principals: the email addresses to subscribe; left empty, only the account behind the credential is subscribed.

Takes a stream out of the organization, together with the topics it held.

• Stream ID: the identifier of the stream to delete, a number and not its name, which a Get many streams step provides through an expression.

Lists the streams of the organization. The Additional Fields decide how wide that list goes, so the same operation answers two very different questions.

• Include Public: adds every public stream of the organization.
• Include Subscribed: adds the streams the account follows.
• Include Default: adds the default streams of the realm; Include All Active adds all active ones and needs administrative privileges.
• Include Owner Subscribed: for a bot account, adds the streams its owner follows.

Returns only the streams the connected account follows. Shorter list, and the one most workflows actually need.

• Include Subscribers: adds a subscribers field to each stream returned, holding the user IDs of everyone subscribed to it.

Changes the settings of an existing stream: its name, its description, its privacy and who is allowed to post in it.

• Stream ID: the stream to update.
• New Name and Description: the new label and the line shown under it.
• Is Private and History Public to Subscribers: close the stream, and decide what its new subscribers can read.
• Stream Post Policy: 1 lets any user post, 2 only administrators, 3 only new members. Announcement Only limits the stream to announcements.

Opens an account in the Zulip organization. All four fields are required, so the workflow has to hold them before the node runs.

• Email: the address of the new user, in the name@email.com form.
• Full Name: the name shown to the rest of the organization.
• Short Name: a short name that stays invisible to other users.
• Password: the password of the new account, better passed through an expression than typed in the node.

Deactivates an account so the person can no longer log in to the organization.

• User ID: the identifier of the user to deactivate, a number that a Get many users step hands over through an expression.

Reads one account and returns its profile, which is how a workflow turns an identifier into a usable name or email.

• User ID: the identifier of the account to read.
• Custom Profile Fields: includes the custom profile field data in the response, such as the team or the job title your administrator added.
• Client Gravatar: when on, the avatar URL comes back only for a real Zulip avatar and stays null for accounts using gravatar.

Brings back the member list of the organization in one run, each account with its profile.

• Custom Profile Fields: adds the custom profile data to every account returned, useful when the team or the department lives in those fields.
• Client Gravatar: same rule as on the single lookup, the avatar URL is returned only for Zulip avatars.

Changes an account that already exists: its name, its permissions, or the custom fields of its profile.

• User ID: the account to update.
• Full Name: the name shown in Zulip.
• Role: 100 owner, 200 organization administrator, 300 moderator, 400 member, 600 guest.
• Is Admin and Is Guest: the two switches that mark the account as administrator or as guest.
• Profile Data: the custom profile field data to update.