Resources · Make integration

Ycode Make integrationAutomate Ycode with Make.

Tired of pasting the same entries into your Ycode site by hand? The Ycode Make integration gives you 7 modules (6 actions and 1 search) that work on collection items. This guide shows how to connect your project and build a first scenario step by step.

Try the Ycode integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Ycode Make integration do?

The Ycode Make integration links your Ycode project to Make, so a scenario (the automation you build in Make, a chain of modules) can read and change the items of your collections. Each module is one brick of that chain. Here, all of them act on collection items, and none of them starts a scenario by itself.

Fill a collection from another tool. Picture a studio that collects project briefs in a form app. The form app starts the scenario, and Create a Collection Item turns each answer into a new entry of your Ycode collection, with no copy and paste.

Keep existing entries in sync. When a price or a status changes in the tool your sales team uses, List Collection Items fetches the entries, then Update a Collection Item or Patch a Collection Item writes the new value on the right one. Every item that moves between modules is a bundle, and every module run on one bundle counts as one operation on your Make plan.

Clean up what is no longer relevant. An event that closes in your ticketing tool can trigger Delete a Collection Item so the page disappears from the list on your site.

What Make does not give you here: a trigger. Ycode has no module that watches your project, so the scenario starts from another app or from the schedule on its first module. When a listed module is not enough, Make an API Call reaches any endpoint of the Ycode API with the same connection. The same app may also exist on n8n; the n8n vs Make page explains how the two tools differ. For budget questions, see Make pricing, and if you want help building it, the Make agency team is there.

Connect

How do you connect your Ycode account to Make?

  1. 01

    Generate an API token in Ycode

    You need an active Ycode project. Open the project settings, go to the API Tokens tab, click Add API token, give the token a name, then copy the token that appears on screen.

  2. 02

    Add a Ycode module in Make

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

  3. 03

    Paste the token and save

    If you like, type a label in the Connection name field so you can tell projects apart later. Paste the API token you copied from Ycode, or follow the on-screen instructions, and confirm to create the connection.

First scenario

Build your first scenario with Ycode

GoalWhen a record changes in another app, Make finds the matching entry in your Ycode collection and updates it.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Ycode has no trigger, so the first module comes from the app where your data lives, such as your spreadsheet or your form tool.

  2. 02

    Add List Collection Items

    Click the + on the right, search for Ycode and pick List Collection Items. Click Create a connection and paste your token. Once linked, Make lists what it can read in your project.

  3. 03

    Add Update a Collection Item

    Add Update a Collection Item after the search. Map the item returned by the previous module and the new values coming from your first app, so each bundle lands on the right entry.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received. Check on your Ycode site that the right entry changed before going further.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set the Scheduling. A new scenario runs every 15 minutes by default. Then switch the scenario on, and it keeps working without you.

Modules

What can Ycode do in Make?

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

Ycode1

Create a Collection Item

ActionIn the docs only

This module adds a fresh entry to one of your Ycode collections, filled with the data your scenario carries from another app.

When to use it
a new lead, product or article appears somewhere else and should show up on your site as its own entry.
Watch out
if the scenario runs twice on the same data, you get two entries, so test with Run once before switching it on.
Ycode2

Delete a Collection Item

ActionIn the docs only

With this module, an entry leaves your Ycode collection as soon as the scenario reaches it, so outdated content stops living on your site.

When to use it
an offer closes, an event is cancelled, or a record is archived in the tool your team relies on.
Watch out
treat the removal as final and test it on a throwaway entry first, since the doc describes no way to bring it back.
Ycode3

Get a Collection

ActionIn the docs only

Get a Collection returns one collection of your project as a single bundle, which is handy to see what Make can read before you write anything.

When to use it
you are setting up a scenario and want to check the collection you target, or pass its details to the next module.
Watch out
it reads the collection itself, not its entries; List Collection Items is the one that brings back items.
Ycode4

List Collection Items

SearchIn the docs only

Here is the only search of the app: it brings back the entries of a collection so the next modules can work on them one by one.

When to use it
you need to find an existing entry before you update, patch or delete it.
Watch out
a search can return zero, one or many bundles, and every following module runs once per bundle, which adds operations to your plan.
Ycode5

Make an API Call

ActionIn the docs only

Make an API Call is your way out when the six other modules stop short: it calls any endpoint of the Ycode API, reusing the connection you already created.

When to use it
the action you need is in the Ycode API but has no dedicated module in Make.
Watch out
you build the request yourself, so keep the Ycode API documentation open and test with Run once.
Ycode6

Patch a Collection Item

ActionIn the docs only

Patch a Collection Item changes an existing entry of your collection. The name suggests it only touches the values you send, but that is a guess, not a documented fact.

When to use it
a status, a price or a date changes in another app and you want the site to follow.
Watch out
the doc does not spell out how it differs from Update a Collection Item, so compare both on a test entry with Run once.
Ycode7

Update a Collection Item

ActionIn the docs only

Update a Collection Item updates an entry you already have in Ycode with the values mapped from earlier modules in the scenario.

When to use it
another tool holds the reference version of a record and your site should mirror it.
Watch out
the module needs to know which entry to change, so place List Collection Items before it and map the item it returns.
Need help

Need help automating Ycode with Make?

A person reads every message.

FAQ

Questions about the Ycode Make integration

01Is the Ycode Make integration free?
Yes, on the Make side. Ycode is a standard app, available from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, up to 5 minutes of execution and files up to 5 MB, with 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module run on one bundle. Your Ycode subscription is a separate matter, covered on the Ycode pricing page.
02What do you need to connect Ycode to Make?
You need a Ycode account with an active project and an API token from that project. In Ycode, open the project settings, choose the API Tokens tab, click Add API token, name it and copy the token shown on screen. In Make, add a Ycode module, click Create a connection, optionally fill the Connection name field, then paste the token. The same connection then serves every Ycode module in your scenarios, including Make an API Call.
03Can a Ycode scenario start on its own without a trigger?
It depends on what starts it. Ycode has no trigger module in Make, neither scheduled nor instant, so nothing inside Ycode can launch a scenario. You have two ways around it. Put a trigger from another app first, such as a form tool or a spreadsheet, and the Ycode modules follow. Or start the scenario with a Ycode module and set the schedule on it: a new scenario runs every 15 minutes by default, and paid plans go down to 1 minute.
04What if a Ycode module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Ycode API with the connection you already have, so you are not limited to the 6 other modules. Keep in mind that the Make documentation for Ycode is flagged as AI-generated from the official Ycode docs and may contain mistakes, so check important details with Ycode and test every new module with Run once on a sample entry before switching the scenario on.
05Should you pick Make or n8n for Ycode?
It depends on the tool your team already works in. On Make, Ycode offers 7 modules focused on collection items, plus Make an API Call, and it is available from the Free plan. Many apps also have an n8n node, so check whether Ycode does before choosing. The information here covers Make only; it does not rank the two tools, their speed or their cost. The n8n vs Make comparison linked above sets out the differences in more detail.
Same platform

Other docs you might need on this stack.

Browse all integrations