Resources · Make integration

Zixflow Make integrationAutomate Zixflow with Make.

Can Make keep your Zixflow CRM up to date while you work elsewhere? The Zixflow Make integration gives you 12 action modules: records, list entries, activities and messages. This page shows how to link your account and build a first scenario, no code involved.

Try the Zixflow integration on MakeSee the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Zixflow Make integration do?

The Zixflow Make integration lets a Make scenario (the automation you build, a chain of modules) write into your Zixflow workspace. Each module is one brick of that chain: it creates, updates or deletes a record, a list entry or an activity, or sends a message, using data that arrives from another app.

Leads that land in the CRM on their own. A form app or a spreadsheet starts the scenario, and Create a Collection Record turns each new contact into a Zixflow record. Add Create a List Entry right after it to drop that person into the right pipeline list.

A first message sent without anyone typing it. Once the record exists, Send a WhatsApp Template Message or Send a Message reaches out to the contact from the same scenario, so nobody on the sales team copies phone numbers by hand.

A history that stays accurate. When a deal moves in another tool, Create an Activity or Update an Activity writes the trace in Zixflow, and the three Delete modules clean up what no longer belongs there.

What the integration does not give you: a trigger. Zixflow has no module that starts a scenario, so the start always comes from a schedule in Make or from another app. For anything the 12 modules do not cover, Make an API Call reaches the rest of the Zixflow API. Before you commit, the Make review and the Make pricing page help you size the plan, and n8n vs Make puts both tools side by side.

Connect

How do you connect Zixflow to Make?

  1. 01

    Generate an API key in Zixflow

    In your Zixflow dashboard, open Settings, then Workspace Settings, Developer and API Key. Click Generate or Create, then copy the key that appears on screen.

  2. 02

    Add a Zixflow module in Make

    In a scenario, add any Zixflow module and click Create a connection. A connection is your Zixflow account linked to Make once, then reused by every Zixflow module. The Connection name field is optional.

  3. 03

    Paste the key and save

    Paste the API key you copied from Zixflow into the connection window, or follow the on-screen instructions, and save. The module can now read your workspace and list what it finds there.

First scenario

Your first scenario: new lead to Zixflow and WhatsApp

GoalWhen a new lead arrives in another app, Make creates the Zixflow record and sends the contact a WhatsApp template.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. The first module is the app where your leads arrive, since Zixflow has no trigger of its own.

  2. 02

    Add Create a Collection Record

    Click the + on the right, search for Zixflow and pick Create a Collection Record. Pick your connection, then map the lead's details from the previous module into the fields Make shows.

  3. 03

    Add the WhatsApp template

    Add Send a WhatsApp Template Message after the record. Once the connection exists, Make lists what it can read in your workspace; pick your template and map the contact coming from the lead.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time; open each module to read the bundle it received, meaning the lead that passed through, and check the record in Zixflow.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. From then on, each new lead goes through without you opening Make.

Modules

What can Zixflow do in Make?

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

Zixflow1

Create a Collection Record

ActionIn the docs only

You get a new record in one of your Zixflow collections, filled from whatever the previous module sent. This is the entry point for putting a contact or a company into the CRM automatically.

When to use it
a form, a signup or a spreadsheet row should become a CRM record without anyone retyping it.
Watch out
each run creates a new record, so a scenario that fires twice on the same lead leaves you with a duplicate.
Zixflow2

Create a List Entry

ActionIn the docs only

This one places an item into a Zixflow list, which is how you slot a contact into a pipeline or a campaign audience from Make. It works well right after a record has been created in the same scenario.

When to use it
a new customer should appear in the onboarding list the moment the deal is signed.
Watch out
an entry is separate from the record, so creating one does not create the other.
Zixflow3

Create an Activity

ActionIn the docs only

Your Zixflow timeline gains a new activity, so the team sees what happened with a contact without leaving the CRM. The data can come from any app earlier in the scenario.

When to use it
a call logged in your phone tool, or a meeting booked elsewhere, should leave a trace next to the contact.
Watch out
the activity needs to point at the right contact, so map an identifier from a previous module rather than a name typed by hand.
Zixflow4

Delete List Entry

ActionIn the docs only

Pulling a contact out of a list happens here, while the record itself stays in the CRM. That keeps pipelines and audiences clean when someone no longer belongs in them.

When to use it
a lead unsubscribes in your email tool and should leave the nurturing list in Zixflow.
Watch out
a deletion cannot be undone from Make, so test it with Run once on a dummy entry before you switch the scenario on.
Zixflow5

Delete a Collection Record

ActionIn the docs only

Removing a whole record from a collection is the job of this module, which makes it the strongest cleanup tool of the integration. Keep it for cases where the record really has to disappear.

When to use it
a deletion request arrives through a form and the contact must be erased from the CRM.
Watch out
nothing brings the record back from Make; add a filter before this module so only the right bundles reach it.
Zixflow6

Delete an Activity

ActionIn the docs only

With this module a single activity leaves the timeline, and the contact and its other activities stay in place. Useful when an automated log turns out to be wrong.

When to use it
a meeting is cancelled in your calendar app and the matching activity in Zixflow should go too.
Watch out
you need the identifier of that exact activity, usually stored when it was first created by another scenario.
Zixflow7

Make an API Call

ActionIn the docs only

Any part of the Zixflow API becomes reachable from your scenario with this module, using the connection you already set up. It covers what the other 11 modules leave out.

When to use it
you need to read data from Zixflow, since the integration has no search module, or call an endpoint no module offers.
Watch out
you write the request yourself, so keep the Zixflow API documentation open while you set it up.
Zixflow8

Send a Message

ActionIn the docs only

A message goes out through Zixflow, right after another app of the scenario hands over the data. The text can mix fixed words with data mapped from earlier modules, like a first name.

When to use it
an order ships in your store and the customer should hear about it from the same channel your team uses.
Watch out
each bundle sends one message, so a list of contacts turns into as many sends and as many operations.
Zixflow9

Send a WhatsApp Template Message

ActionIn the docs only

Your contact receives a WhatsApp message built from a template, with the variable parts filled by the scenario. Pick it over Send a Message when the text must follow a prepared template.

When to use it
a lead has just been created and should get a welcome message with its first name inside.
Watch out
map the phone number from the previous module so each bundle reaches the right person, and test on your own number first.
Zixflow10

Update List Entry

ActionIn the docs only

Changes to an existing entry in a Zixflow list land through this module, so a contact can move along a pipeline without anyone dragging a card. Only the entry changes, not the underlying record.

When to use it
a payment clears in your billing app and the deal should switch to its won stage.
Watch out
the module edits an entry that already exists, so map its identifier from an earlier step.
Zixflow11

Update a Collection Record

ActionIn the docs only

Fields on an existing record are refreshed here, which keeps the CRM in line with the tools where data actually changes.

When to use it
a customer changes their company name or phone number in your app, and Zixflow should show the new value.
Watch out
pick this module rather than Create a Collection Record whenever the contact already exists, or you end up with two records.
Zixflow12

Update an Activity

ActionIn the docs only

An activity already in the timeline gets corrected or completed, instead of piling a second one next to it. The team keeps one clean line per event.

When to use it
a meeting is moved in your calendar and the Zixflow activity should reflect the new details.
Watch out
without the activity's identifier, the module cannot find what to change; save it when the activity is created.
Need help

Need help automating Zixflow with Make?

A person reads every message.

FAQ

Zixflow and Make: frequent questions

01Is the Zixflow Make integration free?
Yes, on the Make side. Zixflow is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Each module that runs on a bundle counts as one operation, which is what Make measures on your plan. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. You still need your own Zixflow subscription.
02What do you need to connect Zixflow to Make?
An active Zixflow account and an API key. The key is generated in Zixflow under Settings, Workspace Settings, Developer, API Key, with the Generate or Create button. In Make, add any Zixflow module, click Create a connection, give it a name if you want to and paste the key. That single connection then serves all 12 Zixflow modules, so you only do this once per account. Once it is saved, Make lists what it can read in your Zixflow workspace, so you pick from a list instead of typing names.
03Can the Zixflow Make integration start a scenario in real time?
No. Zixflow has no trigger module in Make, so a scenario cannot start from an event inside Zixflow. It starts in one of two ways: from a trigger of another app, such as the form or store where the data first appears, or from the schedule on the first module, every 15 minutes by default. On a paid plan, the schedule can go down to 1 minute. The Zixflow modules then run as actions further down the chain.
04What if a Zixflow module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Zixflow API with the connection you already have, which matters here because the integration has no search module to read data back. Keep in mind that the Zixflow documentation on Make is flagged as AI-generated and may contain mistakes, so check important details with Zixflow directly before you rely on them in a live scenario. When you use it, each call still counts as an operation, like any other module.
05Should you use Make or n8n for Zixflow?
It depends on the tool your team already runs. In Make, Zixflow comes with 12 action modules, one connection by API key and Make an API Call for the rest, all available from the Free plan. Many apps also have a node in n8n; check whether one exists for Zixflow and what it covers before you decide. If your other automations already live in one of the two tools, keeping Zixflow there is usually the simpler choice.
Same platform

Other docs you might need on this stack.

Browse all integrations