Ziflow Make integrationAutomate Ziflow with Make.
Proofs, reviewers and comments can move on their own once Ziflow talks to Make. The Ziflow Make integration gives you 20 modules: 1 instant trigger, 10 actions and 9 searches. This guide shows creative and marketing ops teams how to connect the account and build a first scenario.
Verified Trustpilot reviews · AI, automation & growth agency
What can the Ziflow Make integration automate?
The Ziflow Make integration links your Ziflow account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick such as a trigger, an action or a search. Ziflow then creates proofs, routes reviewers and tidies folders without anyone copying data by hand.
Proofs that start themselves. When a design request lands in another tool, Create new proof opens the proof in Ziflow and Add a reviewer puts the right person on the right stage, using their email address. The agency account manager stops building each review by hand.
A reaction to every piece of feedback. Watch webhook is an instant trigger: Ziflow calls Make as soon as activity reaches the webhook. From there, List comments pulls the remarks on a proof so a scenario can hand them to a project tool or a chat channel.
Folders that stay in order. Create a folder, Update a folder and Search folders keep the Ziflow tree aligned with your client list, while Search proofs finds the proofs that match your criteria.
The Make documentation for Ziflow lists no specific limit. When a listed module does not cover a need, Make an API call reaches the rest of the Ziflow API with the same connection. Ziflow often has an n8n node too; the n8n vs Make comparison lays out the differences. To learn the editor step by step, the Make training starts from zero, and Make troubleshooting helps when a run fails.
How do you connect Ziflow to Make?
- 01
Copy your Ziflow API key
Make signs in to Ziflow with an API key, so you need an active Ziflow account first. In Ziflow, open Settings, pick API in the menu and copy the API key shown on screen.
- 02
Add a Ziflow module
In your Make scenario, add any Ziflow module and click Create a connection. A connection is your Ziflow account linked to Make once, then reused by every Ziflow module. The Connection name field is optional but handy with several accounts.
- 03
Paste the key and save
Paste the API key you copied, or follow the on-screen instructions, and save. Make can now read your Ziflow proofs, folders and contacts, and it offers them in the module fields instead of asking you to type IDs.
Your first scenario: turn a design request into a Ziflow proof
GoalWhen a design request arrives from another app, Make creates the proof in Ziflow and adds the reviewer to it.
- 01
Start from the request app
On the Scenarios page, create a new scenario and click the +. Pick the module of the app where requests arrive, such as a form tool, and connect it.
- 02
Add Create new proof
Click the + on the right, search for Ziflow and choose Create new proof. Select your connection, or click Create a connection and paste your API key.
- 03
Map the request data
Fill the module fields with data from the first module. Each request is a bundle, one item passed from one module to the next, so every request produces its own proof.
- 04
Add the reviewer
Add Add a reviewer after the proof, map the proof coming from the previous module and the reviewer's email, then pick the stage that person should join.
- 05
Test with Run once
Send one test request, then click Run once. Make runs the scenario a single time and shows the bundles each module received, so you can check the proof in Ziflow.
- 06
Schedule and switch on
Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Each run of a module on a bundle counts as one operation on your plan.
What starts a Ziflow scenario
1 module starts a scenario when something happens in Ziflow. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Ziflow as soon as it happens.
Watch webhook
Instant triggerIn Make“Watches for activity sent to webhook trigger.”
Watch webhook opens your scenario the moment Ziflow sends activity to Make, so a review event gets a follow-up without anyone checking the proofing screen. Each piece of activity reaches the next module as one bundle you can map.
Everything the Ziflow modules can do
Ziflow gives you 19 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Add a comment
ActionIn Make“Adds a new comment to the proof.”
Posts a new comment on a proof, so information from another tool shows up right where reviewers already read feedback. Nobody has to switch windows to pass a message along.
Create a folder
ActionIn Make“Create a new public or private folder.”
Creates a Ziflow folder, public or private, so every new client or campaign gets its own place for proofs from day one. The folder is ready before the first file is uploaded.
Delete a folder
ActionIn Make“Delete specific folders and its subfolders. Can be used to delete proofs within said folder.”
Removes a folder along with its subfolders, and it can take the proofs inside with it. It clears out an archived client in one step instead of dozens of clicks.
Delete a proof
ActionIn Make“Delete a Proof with the given ID.”
Deletes a single proof by its ID, which keeps Ziflow free of drafts that were created by mistake or cancelled. Only that proof goes, the folder around it stays.
Delete a reviewer
ActionIn Make“Deletes a reviewer from a specific stage on a proof using either Email or their reviewer ID.”
Takes a reviewer off one stage of a proof, found by email or by reviewer ID. The person stops receiving that review without you opening the proof settings.
Get a reviewer
ActionIn Make“Gets a reviewer from a specific stage on a proof using either Email or their reviewer ID.”
Returns the details of one reviewer on a given stage of a proof, looked up by email or reviewer ID. A scenario can then check who is on a review before it acts.
Make an API call
ActionIn Make“Performs an arbitrary authorized API Call”
Calls any endpoint of the Ziflow API with the connection you already set up, which covers what the other modules leave out. You stay inside the same scenario and the same login.
Resolve a comment
ActionIn Make“Resolves or unresolves a comment.”
Marks a comment as resolved, or reopens it, so the proof shows at a glance which remarks still need work. The status follows what happens outside Ziflow.
Update a folder
ActionIn Make“Update an existing folder by populating the fields with the data you wish to update. Only fields provided will be updated.”
Changes an existing folder and touches only the fields you fill in, leaving the rest as it was. Renaming a client space no longer means rebuilding it.
Update a proof
ActionIn Make“Update an existing proof by populating the fields with the data you wish to update. Only fields provided will be updated.”
Edits a proof that already exists, and only the fields you provide are rewritten. The review keeps its history while its details catch up with the brief.
Add a reviewer
SearchIn Make“Adds a reviewer to a specific stage on a proof using Email.”
Places a person on a specific stage of a proof using their email address, so the review reaches the right eyes without manual invitations. It pairs naturally with Create new proof.
Create new proof
SearchIn Make“Creates a new proof or batch of proofs.”
Opens a new proof, or a batch of proofs at once, straight from your scenario. Files coming from another app go to review without anyone uploading them by hand.
List comments
SearchIn Make“Returns comments made on the proof.”
Returns the comments left on a proof, each one as its own bundle, so feedback can travel to a report, a task list or a message. The remarks stop living in a single screen.
List contacts
SearchIn Make“Retrieves a contact by their email or ID. Can also list contacts to the account using pagination. Does not return users.”
Fetches a contact by email or ID, or pages through all contacts of the account, which helps keep external reviewers in sync with your address book.
Lists proofs
SearchIn Make“Get a specific proofs by ID or a general paginated list of proofs. Proofs are sorted from the most recent to oldest.”
Returns one proof by ID or a paged list of proofs, newest first, so a scenario can work through recent reviews without searching by hand.
List users
SearchIn Make“Retrieves a user by their email or ID. Can also list users to the account using pagination.”
Finds a user of your Ziflow account by email or ID, or lists all users page by page. Internal reviewers become easy to pick in later modules.
List webhooks
SearchIn Make“Returns a list of current webhook subscriptions. Can also get a specific webhook by ID.”
Shows the webhook subscriptions active on your account, or a single one by ID. It gives a clear view of what Ziflow is currently sending out to Make and other tools.
Search folders
SearchIn Make“Lists folder information with the given ID. Lists all root folders if empty.”
Returns the information of a folder by its ID, and when you leave the ID empty it lists every root folder. It is the easy way to find where proofs should go.
Search proofs
SearchIn Make“Allows to search for proofs based on given criteria.”
Looks for proofs that match the criteria you set, so the scenario can act on exactly the reviews that matter. It is the entry point before most updates and deletions.
Need help automating Ziflow with Make?
A person reads every message.
