ZULIP n8n INTEGRATION: AUTOMATE ZULIP WITH N8N

This action allows you to programmatically create new user accounts in your Zulip organization. It's essential for automating user provisioning workflows, especially when onboarding new team members from HR systems or external directories.

Key parameters:

• Email: A required text field where you enter the email address for the new Zulip user. This will be their login identifier.
• Full Name: A required text field for the user's complete display name as it will appear in Zulip.
• Password: A required text field to set the initial password for the new account.
• Short Name: An optional text field for a brief username or display identifier within Zulip.

Use cases:

• Automatically create Zulip accounts when new employees are added to BambooHR or Workday
• Provision users when they're invited to a Notion workspace or added to a project in Asana
• Sync user creation with your identity provider (Okta, Auth0) for seamless onboarding

This action retrieves detailed information about a specific Zulip user by their unique ID. Perfect for verifying user existence, fetching profile data, or enriching workflows with user context before performing other operations.

Key parameters:

• User ID: A required text field where you provide the unique numerical identifier of the Zulip user whose information you want to retrieve.
• Additional Fields: An optional section allowing you to add extra query parameters or specify which data to return.

Use cases:

• Fetch user details before sending personalized private messages
• Verify that a user exists in Zulip before attempting to add them to a stream
• Retrieve user information for logging or audit purposes

This action retrieves a list of multiple users from your Zulip organization in a single request. Ideal for synchronization workflows, reporting, and batch operations that need to work with your entire user base or filtered subsets.

Key parameters:

• Additional Fields: An optional section where you can add extra parameters to filter or customize the user retrieval, such as limiting results or specifying particular query criteria.

Use cases:

• Sync your Zulip user list with an external database or spreadsheet
• Generate periodic reports of all active users
• Compare Zulip users against another system to identify missing accounts

This action modifies existing user account details in Zulip. Use it to keep user profiles synchronized with your source of truth or to programmatically update user information based on events in other systems.

Key parameters:

• User ID: A required text field specifying the unique identifier of the user to be updated.
• Additional Fields: An optional section with an "Add Field" button allowing you to dynamically select which properties to update, such as full name, email, or other user attributes.

Use cases:

• Update user names in Zulip when they change in your HR system
• Sync role or title changes from your org chart tool
• Bulk update user properties based on spreadsheet imports

This action deactivates a user account in Zulip, preventing them from accessing your organization while preserving their message history. Essential for offboarding workflows and access management.

Key parameters:

• User ID: A required text field where you must enter the unique identifier of the Zulip user to be deactivated.

Use cases:

• Automatically deactivate Zulip access when an employee is marked as terminated in your HR system
• Revoke access when a contractor's project ends
• Part of a broader offboarding automation that also removes access from other tools

This action creates a new stream (channel) in your Zulip organization. Streams are fundamental to Zulip's topic-based communication, and automating their creation helps maintain consistent organization structures.

Key parameters:

• JSON Parameters: A toggle switch that, when enabled, allows you to define stream configuration in raw JSON format for advanced setups.
• Subscriptions: An optional section where you can define who should be subscribed to the new stream, including stream name, description, and subscriber details.
• Additional Fields: An optional section for adding custom properties like stream description, privacy settings, or other configuration options.

Use cases:

• Automatically create project-specific streams when new projects are initiated in Jira or Monday.com
• Generate customer support streams when new enterprise clients sign contracts
• Create onboarding streams for new team members with preset configurations

This action permanently removes a stream from your Zulip organization. Use with caution as this also deletes all messages and topics within the stream.

Key parameters:

• Stream ID: A required text field where you must provide the unique identifier of the Zulip stream to be deleted.

Use cases:

• Clean up temporary project streams when projects are completed
• Remove deprecated channels as part of organization restructuring
• Automated housekeeping for streams that haven't been active for a specified period

This action retrieves a list of multiple streams from your Zulip organization. Useful for discovering available streams, generating reports, or building dynamic stream selection interfaces.

Key parameters:

• Additional Fields: An optional section that allows you to add filtering criteria or limit parameters to customize which streams are returned and how many.

Use cases:

• Build a dashboard showing all active streams in your organization
• Sync stream metadata to an external documentation system
• Audit stream permissions and configurations periodically

This action retrieves a list of all streams that the authenticated Zulip account is subscribed to. Perfect for understanding the connected account's visibility and permissions within the organization.

Key parameters:

• Additional Fields: An optional section for adding extra parameters to refine the subscription query if needed.

Use cases:

• Verify which streams a bot account can post to before sending automated messages
• Generate reports of stream subscriptions for specific users
• Check subscription status before attempting to send stream messages

This action modifies the properties of an existing stream in Zulip, such as its name, description, or permission settings. Essential for keeping stream configurations synchronized with external systems.

Key parameters:

• Stream ID: A required text field specifying the unique identifier of the stream to be updated.
• JSON Parameters: A toggle switch that allows you to provide update parameters in raw JSON format for advanced configurations.
• Additional Fields: An optional section where you can dynamically add specific properties to update, such as stream name, description, or privacy settings.

Use cases:

• Update stream descriptions when project details change in your project management tool
• Modify stream permissions based on team restructuring
• Rename streams to match new naming conventions from a central configuration

This action posts a message to a specific stream and topic in Zulip. It's the most commonly used action for notification workflows, allowing you to broadcast information to entire teams or project groups.

Key parameters:

• Stream Name or ID: A required field where you specify the target stream, either by name or unique ID.
• Topic Name or ID: A required field for the message topic, which helps organize conversations within the stream.
• Content: A required multi-line text field where you compose the message body. Supports both fixed text and dynamic expressions for personalized content.

Use cases:

• Post deployment notifications from CI/CD pipelines to development streams
• Share daily sales summaries from your CRM to the sales team stream
• Broadcast system alerts or monitoring notifications to operations channels
• Send automated standup reminders to project-specific streams

This action sends a direct private message to one or more specific users in Zulip. Perfect for targeted notifications that shouldn't be shared publicly or for personal alerts to individuals.

Key parameters:

• To: A required field specifying the recipient(s) of the private message. You can target individual users or create group private messages.
• Content: A required multi-line text field for composing the message body. Supports both fixed text and dynamic expressions.

Use cases:

• Send private onboarding instructions to new team members
• Alert managers privately when their team members submit time-off requests
• Deliver personal notifications about individual performance metrics
• Send confidential system credentials or access information securely

This action retrieves the details of a specific message by its ID. Useful for workflows that need to read message content, verify message delivery, or process message data.

Key parameters:

• Message ID: A required text field where you provide the unique numerical identifier of the message to retrieve.

Use cases:

• Fetch message content for logging or archival purposes
• Verify that an automated message was successfully posted
• Read message details as input for subsequent workflow steps

This action modifies an existing message in Zulip, allowing you to edit content or change message properties after posting. Useful for correcting automated messages or adding information.

Key parameters:

• Message ID: A required text field accepting the numerical ID of the message to be updated.
• Update Fields: An optional section with an "Add Field" button allowing you to specify which properties to modify, such as message content, topic, or reactions.

Use cases:

• Update deployment notification messages with final status once builds complete
• Correct typos or errors in automated messages
• Append additional context to existing notifications as workflows progress

This action permanently removes a message from Zulip. Use for cleaning up test messages, removing outdated notifications, or as part of data retention workflows.

Key parameters:

• Message ID: A required text field where you specify the unique numerical ID of the message to be deleted.

Use cases:

• Clean up automated test messages after workflow testing
• Remove temporary notifications that are no longer relevant
• Implement message retention policies for compliance

This action uploads a file to Zulip, making it available for sharing in messages. Essential for workflows that need to share documents, reports, or media files with team members.

Key parameters:

• Put Output File in Field: An optional text field (defaulting to "data") that specifies the output binary field name where the uploaded file's reference will be stored for use in subsequent workflow steps.

Use cases:

• Upload generated reports and share them in relevant streams
• Attach screenshots from monitoring tools to alert messages
• Share exported documents from other applications with your Zulip team