Resources · Make integration

Zulip Make integrationAutomate Zulip with Make.

Can Make post to Zulip and manage its users for you? Yes. The Zulip Make integration gives you 10 modules: 8 actions and 2 searches. This page shows how to link your account with an API key, build a first scenario, and pick the right module.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Zulip Make integration do for your team?

The Zulip Make integration lets Make, a no-code automation tool, act inside your Zulip organization for you. It sends messages to a stream or to one person, uploads files, looks up users, and lets admins create, deactivate or reactivate accounts, all from a scenario (the automation you build in Make, a chain of steps).

Onboarding without the checklist. When a new hire signs their contract in another tool, Create a User opens their Zulip account and Send a Message posts a welcome in the team stream. Nobody has to remember the admin panel.

Clean offboarding. A departure logged in your HR tool can feed Deactivate a User. If the person comes back as a contractor, Reactivate a User restores the same account instead of creating a duplicate.

Reports that land where people read. A scenario that builds a PDF elsewhere can push it with Upload a File, then share the link with Send a Message, because an uploaded file stays invisible until a message carries its link.

What the integration does not do: Zulip has no trigger module in Make, so nothing starts on its own when a message arrives in Zulip. The scenario starts on a schedule or on another app's event. If you are still weighing tools, read the n8n vs Make comparison or the Zulip n8n integration page. To learn the editor from scratch, the Make training covers it.

Connect

How do you connect your Zulip account to Make?

  1. 01

    Grab your API key in Zulip

    In Zulip, click the gear icon at the top right, open Personal settings, then Account & privacy. Under API key, click Manage your API key, type your password, click Get API key and copy it.

  2. 02

    Add a Zulip module and create the connection

    In your scenario, add any Zulip module and click Create a connection. A connection is your Zulip account linked to Make once, then reused by every Zulip module. The Connection name field is optional but helps when you have several workspaces.

  3. 03

    Paste the credentials and save

    Enter the credentials you copied from Zulip, or follow the instructions Make shows on screen, then save. The connection now appears in the dropdown of every Zulip module you add later.

First scenario

Your first scenario: ping the teammate your CRM just assigned

GoalWhen your CRM or form tool hands over a teammate's email, Make finds that person in Zulip and sends them a private message.

  1. 01

    Start with your other app's trigger

    On the Scenarios page, create a scenario and click the big +. Pick the trigger of the tool that knows the email, such as your CRM when a deal gets an owner. Zulip has no trigger of its own.

  2. 02

    Add Get a User by Email

    Click the + on the right, search for Zulip and pick Get a User by Email. Click Create a connection if needed, then map the email coming from the first module.

  3. 03

    Add Send a Message

    Add Send a Message after it, choose a private message and map the user found in the previous step as the recipient. Write the text your teammate should read, with details from the trigger.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received (a bundle is one item passed along, here one user). Check that your teammate got the message.

  5. 05

    Schedule it and switch it on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, unless your other app's trigger is instant. Then switch the scenario on: each new assignment now pings the right person.

Modules

The 10 Zulip modules, and when to pick each one

Zulip gives you 10 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Zulip1

Create a User

Action

In MakeCreates a new user account. This endpoint is only available to organization administrators.

Opens a brand new account in your Zulip organization, so a newcomer can log in without an admin doing it by hand. Each run creates one person.

When to use it
right after a hire is confirmed in your HR tool or a signed contract lands in your CRM.
Watch out
only organization administrators can call it, so the connection must use an admin's API key or the module fails.
Zulip2

Deactivate a User

Action

In MakeDeactivates a user given their user ID. This endpoint is only available to organization administrators.

Switches off a Zulip account from its user ID. Because Zulip also offers Reactivate a User, a deactivation is a pause you can undo later, not a deletion step in your scenario.

When to use it
when a departure or the end of a contractor mission is recorded somewhere else.
Watch out
it needs the user ID, not an email, so put Get a User by Email in front, and it is reserved to administrators.
Zulip3

Get a User

Action

In MakeFetches details for a single user in the organization.

Fetches the profile of one member of your organization when you already hold their user ID, for example from an earlier step. The details it returns become fields you can map further down.

When to use it
a message or an earlier module gave you an ID and you need the name or email behind it.
Watch out
if you only have an email address, Get a User by Email is the direct route.
Zulip4

Get a User by Email

Action

In MakeFetches details for a single user in the organization given a Zulip display email address.

Looks up a single member from their Zulip display email address. That is often the only identifier your other tools share with Zulip, so this module acts as the bridge between them.

When to use it
a form, a CRM or a spreadsheet hands you an email and the next Zulip step needs the matching user.
Watch out
it expects the display email Zulip shows, which may differ from the address stored in your other tool.
Zulip5

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Calls any endpoint of the Zulip API through the connection you already set up, with no second login. It is the way out when none of the nine ready-made modules covers what you need.

When to use it
you want a Zulip feature that has no dedicated module here.
Watch out
you write the request yourself, so keep the Zulip API reference open next to the editor.
Zulip6

Reactivate a User

Action

In MakeReactivates a user given their user ID. This endpoint is only available to organization administrators.

Brings a deactivated Zulip account back to life from its user ID, with the same identity as before. It saves you from creating a second account for someone who already had one.

When to use it
a former employee returns, or a seasonal contributor starts a new mission.
Watch out
like the other account modules, only an organization administrator's connection can run it.
Zulip7

Send a Message

Action

In MakeSends a stream or a private message.

Posts text into Zulip, either in a stream the whole team follows or as a private message to one person. It is the module most scenarios end with, because it puts the result in front of people.

When to use it
a deal closes, a support ticket escalates, or a file you just uploaded needs sharing.
Watch out
fed by a search, it sends one message per bundle, so check the count before switching the scenario on.
Zulip8

Upload a File

Action

In MakeUploads a file. To share the uploaded file, you'll need to send a message containing the resulting link.

Sends a file from an earlier module into Zulip storage and hands back a link to it. On its own, nobody sees the file yet.

When to use it
a quote, an export or an invoice generated elsewhere must reach a stream.
Watch out
sharing needs one more step, Send a Message with the link returned here. On the Free plan, keep in mind that Make handles files up to 5 MB.
Zulip9

Check if Messages Match a Narrow

Search

In MakeChecks whether a set of messages match a narrow.

Tells you whether a set of messages fits a narrow, the Zulip word for a filtered view of messages. Think of it as a checkpoint in your scenario rather than a way to pull new content.

When to use it
before acting on messages, to confirm they belong to the filtered view you expect.
Watch out
it checks a set of messages you already have from earlier steps, it does not go looking for new ones.
Zulip10

List Users

Search

In MakeRetrieves details on all users in the organization.

Returns every member of your organization, one bundle per person. Handy to audit accounts or to copy the team roster into a sheet.

When to use it
you need the whole roster rather than one person you can find by email.
Watch out
each bundle it outputs costs an operation in every module that follows (an operation is one module run on one bundle, what Make counts on your plan), so filter before sending anything.
Need help

Need help automating Zulip with Make?

A person reads every message.

FAQ

Zulip and Make: common questions

01Is the Zulip Make integration free?
Yes, Zulip is a standard app, so its modules are available from the Make Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, up to 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. Usage is counted in operations per month. Your Zulip subscription is a separate matter handled on the Zulip side.
02What does it take to connect Zulip to Make?
You need an active Zulip account and its API key. In Zulip, open the gear icon, then Personal settings, Account & privacy, and click Manage your API key. Enter your password, click Get API key and copy the value. In Make, add a Zulip module, click Create a connection and paste the credentials. If you plan to create, deactivate or reactivate users, the key must come from an organization administrator, since those three modules are restricted to admins.
03Can a new Zulip message start a Make scenario in real time?
No. Zulip has no trigger module in Make, neither scheduled nor instant, so a message posted in Zulip cannot start a scenario by itself. You have two ways to start one. Put a trigger from another app first, such as your CRM or a form, and the Zulip modules run right after it. Or rely on the schedule of the first module, which runs every 15 minutes by default on a new scenario and never faster than 15 minutes on the Free plan.
04What if the Zulip module you need is missing?
It depends on the feature, but Make an API Call usually covers it. That module reaches any endpoint of the Zulip API with the connection you already created, so you do not log in twice. You describe the request yourself, which means reading the Zulip API reference. Also note that the Make documentation for this app is AI-generated from Zulip sources and warns that it may contain mistakes, so double check anything important with Zulip.
05Make or n8n: which one fits Zulip better?
It depends on your context more than on Zulip. Both tools can talk to Zulip: Make offers the 10 modules described here, and Zulip is also covered by an n8n node, with its own page on this site. Look at which tool your team already builds in, where your other apps are connected, and who will maintain the scenarios. If the rest of your automations live in Make, keeping Zulip there avoids splitting your work across two editors.