Resources · Make integration

Yeeflow Make integrationAutomate Yeeflow with Make.

Your Yeeflow lists can feed the rest of your tools without a single line of code. The Yeeflow Make integration gives you 3 triggers and 6 modules to watch, add, find, update and delete list items. This page shows how to link your account and build a first working scenario.

Try the Yeeflow integration on MakeSee the 9 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Yeeflow Make integration do for you?

The Yeeflow Make integration links your Yeeflow workspace to Make, a visual tool where you build a scenario: an automation made of modules, each one a brick that watches, reads or changes data. For Yeeflow, those bricks work on list items, so a change in a list can start work in another app, or another app can write into your lists.

React to new entries. Put Watch Created Item at the start of a scenario and every new item in the list you pick becomes a bundle, one package of data that the next module receives. From there, Add an Item to a List can copy it into a second list, or a module from another app can pass it along.

Keep other tools in step. Watch Updated Item notices edited items, which suits any setup where a status or an owner changes in Yeeflow and another system should hear about it. Watch Removed Item covers the opposite case, when an item disappears and someone needs to know.

Write into Yeeflow from outside. Search Items and Get an Item find the right record, then Update an Item or Delete an Item act on it. When none of the listed modules fits, Make an API Call reaches the rest of the Yeeflow API with the same connection.

Two limits are worth knowing. The Make documentation for Yeeflow is flagged as AI-generated, so check important details with Yeeflow itself. The page also says nothing about fields or quotas, and neither does this one. Weighing another tool? Read n8n vs Make, check Make pricing, or, when a scenario stalls, open Make troubleshooting.

Connect

How do you connect Yeeflow to Make?

  1. 01

    Copy your Yeeflow API key

    Make signs in to Yeeflow with an API key, so you need an active Yeeflow account first. In your Yeeflow workspace, open Settings, go to the API Keys section and copy the key shown on screen.

  2. 02

    Add a Yeeflow module in Make

    Log in to Make, open your scenario, add any Yeeflow module and click Create a connection. A connection is your Yeeflow account linked to Make once, then reused by every Yeeflow module you add later.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when you run several workspaces. Paste the API key you copied, or follow the on-screen instructions, and save. Make can now read your Yeeflow lists.

First scenario

Build your first Yeeflow scenario in Make

GoalWhen a new item is created in a Yeeflow list, Make adds a copy of it to a second Yeeflow list.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to add the first module. Type Yeeflow in the search box to see its modules.

  2. 02

    Pick Watch Created Item

    Choose Watch Created Item, then select your connection or click Create a connection. Once linked, Make lists what it can read from Yeeflow, so you pick the source list instead of typing it.

  3. 03

    Add the second list

    Click the + on the right of the trigger and add Add an Item to a List. Pick a different target list, then map each value from the trigger's bundle into the matching field Make shows you.

  4. 04

    Test with Run once

    Create a test item in the source list, then click Run once. Each module shows the bundles it received; open them to confirm the copy landed in the second list with the right values.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set Scheduling: a new scenario checks every 15 minutes by default. Keep that or adjust it, then switch the scenario on so it runs without you.

Triggers

Yeeflow triggers: what starts your scenario

3 modules start a scenario when something happens in Yeeflow. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Yeeflow as soon as it happens.

Yeeflow1Watch Created Item

Watch Created Item

triggerIn the docs only

Watch Created Item hands your scenario every new entry in the Yeeflow list you choose, one bundle per item, so the next modules can copy, notify or file it without anyone lifting a finger.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, and never faster than every 15 minutes on the Free plan.
When to use it
any list where a fresh entry should trigger follow-up work somewhere else, such as a request that needs a copy in a team's own list.
Watch out
the Make documentation does not describe this module in detail, so run it once on a test item to see exactly which values it returns.
Yeeflow2Watch Removed Item

Watch Removed Item

triggerIn the docs only

Removals are easy to miss. Watch Removed Item gives you a signal when an entry leaves a Yeeflow list, so another tool or a colleague learns about it instead of finding a gap later.

How it fires
scheduled. Make checks the app on the scenario's schedule, so a removal shows up at the next check, not the moment it happens.
When to use it
lists whose content is mirrored elsewhere, where a deleted entry should also be cleaned up or at least flagged in the other system.
Watch out
the documentation does not say what data remains once an item is gone; test with Run once before mapping values into later modules.
Yeeflow3Watch Updated Item

Watch Updated Item

triggerIn the docs only

With Watch Updated Item, an edit made in Yeeflow reaches the rest of your stack: each changed item arrives as a bundle that later modules can read and pass along.

How it fires
scheduled. Make checks the app on the scenario's schedule, which is every 15 minutes for a new scenario unless you change it.
When to use it
a status, an owner or a due date gets changed in Yeeflow and another app or a teammate should follow that change.
Watch out
if the same scenario then runs Update an Item on the watched list, its own edit can come back as a new update; write to a different list or add a filter.
Modules

Yeeflow modules: what Make can do in your lists

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

Yeeflow1

Add an Item to a List

ActionIn the docs only

Add an Item to a List creates a new entry in the Yeeflow list you pick, filled with values mapped from earlier modules, so data collected elsewhere lands in Yeeflow without retyping.

When to use it
a form, an email or another app produces a record that belongs in a Yeeflow list.
Watch out
each run adds a fresh item, so a scenario that runs twice on the same data creates a duplicate.
Yeeflow2

Delete an Item

ActionIn the docs only

This module removes one item from a Yeeflow list, which keeps lists tidy when a record is closed or cancelled in another tool.

When to use it
an entry has lost its purpose and leaving it in place would confuse the people who work in that list.
Watch out
Make has no undo button here. Treat every deletion as final, and try the module with Run once on a throwaway item before you point it at real data.
Yeeflow3

Get an Item

ActionIn the docs only

Get an Item fetches one specific entry and hands its full content to the next module, which is handy when you already know exactly which record you want.

When to use it
an earlier step, such as a trigger or another app, gives you the item's identifier and you need the rest of its values.
Watch out
as its name suggests, it fetches one item you can point to; when you only have a value to match, reach for Search Items instead.
Yeeflow4

Make an API Call

ActionIn the docs only

Make an API Call is your way around the gaps: it calls any endpoint of the Yeeflow API from the scenario, using the connection you already set up.

When to use it
you need something none of the other eight modules offers, and the Yeeflow API documents how to do it.
Watch out
this module expects you to read the API reference yourself; start from the Yeeflow documentation and test each call with Run once.
Yeeflow5

Search Items

SearchIn the docs only

Search Items looks through a Yeeflow list and returns every matching entry, so you can find a record from a value you already have, such as a name or a reference passed on by another app.

When to use it
before updating or deleting, to locate the right item from a value supplied by another app.
Watch out
a search can return zero, one or several bundles; each result runs the following modules once, which also costs one operation each.
Yeeflow6

Update an Item

ActionIn the docs only

Update an Item changes the values of an existing Yeeflow entry, so a list stays current when the truth changes in another system.

When to use it
a payment clears, a ticket closes or an owner changes elsewhere, and the matching Yeeflow item should reflect it.
Watch out
the module needs to know which item to change; place Search Items or Get an Item before it, and avoid writing to a list that Watch Updated Item watches in the same scenario.
Need help

Need help automating Yeeflow with Make?

A person reads every message.

FAQ

Yeeflow and Make: common questions

01Is the Yeeflow Make integration free?
Yes, on the Make side. Yeeflow is a standard app, so its modules are available from the Make Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans lower the minimum interval to 1 minute and remove the cap on active scenarios. Every module run counts as an operation on your plan. You still need an active Yeeflow account, whose own subscription is set by Yeeflow.
02What do you need to connect Yeeflow to Make?
An active Yeeflow account and its API key. In your Yeeflow workspace, open Settings, then the API Keys section, and copy the key shown there. In Make, add any Yeeflow module, click Create a connection, give it a name if you like, and paste the key. That single connection then serves all 9 Yeeflow modules, including Make an API Call, so you do this once per workspace rather than once per scenario.
03Do Yeeflow triggers in Make react in real time?
No. The 3 Yeeflow triggers, Watch Created Item, Watch Updated Item and Watch Removed Item, are scheduled: Make checks Yeeflow on the scenario's schedule rather than being called by Yeeflow. A new scenario checks every 15 minutes by default, and the Free plan cannot go below that. Paid plans allow a check every minute. None of the Yeeflow modules is an instant trigger, so expect a short wait between a change in Yeeflow and the scenario picking it up.
04What if a Yeeflow module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Yeeflow API through the same connection, which covers actions the 8 other modules do not offer. You will need to read the Yeeflow API documentation to know which call to send. Keep in mind that the Make documentation for Yeeflow is labelled as AI-generated, so confirm important details with Yeeflow before relying on them in a production scenario that other people depend on.
05Should you use Make or n8n for Yeeflow?
It depends on the criteria that matter to you, not on a winner. On Make, Yeeflow comes with 9 ready modules, a guided connection by API key, and a visual editor where each step shows the bundles it received. Before choosing n8n, check whether it offers a Yeeflow node and which operations that node covers, then compare both on the modules you actually need, how you prefer to build and how your team works day to day.
Same platform

Other docs you might need on this stack.

Browse all integrations