Resources · Make integration

Iteration X Make integrationAutomate Iteration X with Make.

Need your Iteration X projects, teams and issues somewhere else without copying them by hand? The Iteration X Make integration gives you 9 modules: 4 actions and 5 searches. This guide shows how to link your account, build a first scenario and pick the right module.

Try the Iteration X integration on MakeSee the 9 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Iteration X Make integration do for you?

The Iteration X Make integration lets Make read your Iteration X workspace: projects, teams, issues and their comments. You build a scenario (the automation you assemble in Make, a chain of modules), and each module is one brick of it. The app has no trigger, so a scenario starts on a schedule or from another app.

A running list of open work per team. List Teams returns every team, then List Team Issues pulls the issues attached to each one. You get one bundle (one item passed from module to module) per issue, ready to send to a sheet or a chat app.

Full context on a single issue. When another app hands you a reference to an issue, Get an Issue fetches it and List Comments brings the discussion around it. Handy before you reply to a customer or escalate a case.

A project snapshot. List Projects and List Project Issues give you the project side of the same data. For anything the ready-made modules skip, Make a GraphQL Query lets you write the request yourself.

Two limits to know. The app has no module that watches for changes, so nothing starts the moment an issue appears. And Make itself flags its Iteration X documentation as limited, so test each module with real data before you rely on it. If you also look at n8n, the n8n vs Make comparison lays out the criteria. New to the editor? The Make training covers the basics, and the Make pricing page explains what each plan allows.

Connect

How do you connect your Iteration X account to Make?

  1. 01

    Open the connection window

    Add any Iteration X module to your scenario and click Create a connection. A connection is your Iteration X account linked to Make once; every Iteration X module in your scenarios reuses it afterward.

  2. 02

    Name it and authorize Make

    Give the connection a clear name if you like, such as the workspace it points to. Then follow what Iteration X asks: either approve Make on the Iteration X authorization page, or paste the key the app gives you.

  3. 03

    Save and check the fields

    Click Save. Back in the module, Make should now list the projects or teams it can read. If those lists stay empty, the connection is not working yet, so fix it before you go further.

First scenario

Your first scenario with Iteration X

GoalWhen the scenario runs on its schedule, Make lists your Iteration X projects and collects the issues of each project.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Search for Iteration X and pick List Projects.

  2. 02

    Link your account

    Click Create a connection and follow the three connection steps above. Once it is saved, fill in the module fields; Make shows the options it can read from your workspace.

  3. 03

    Add the issues module

    Click the + on the right of List Projects and add List Project Issues. In its fields, map the project data coming from the previous module, so each project gets its own lookup.

  4. 04

    Test with Run once

    Click Run once. The scenario runs a single time and each module shows the bundles it received. Open them to confirm you see the projects and the issues you expected.

  5. 05

    Schedule and switch it on

    Click the clock on List Projects to set the schedule (every 15 minutes by default), then switch the scenario on. Add a module from another app after the issues if you want them stored or shared.

Modules

What each Iteration X module does

Iteration X gives you 9 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Iteration X1

Get a Project

ActionIn the docs only

Hands you one Iteration X project as a single bundle, so the next modules can use its data. It works on one project at a time, never a list.

When to use it
another module or app already points to a specific project and you need its details before routing the rest of the scenario.
Watch out
it returns one project only; to go through all of them, start with List Projects.
Iteration X2

Get a Team

ActionIn the docs only

Fetches the details of one team in Iteration X, returned as a single bundle you can map into later modules. One team in, one team out.

When to use it
an issue or a message names a team and you want that team's information before you notify or assign anyone.
Watch out
if you need every team rather than one, List Teams is the right module.
Iteration X3

Get an Issue

ActionIn the docs only

Gives you the full record of one issue, so a later module can send it, copy it or decide what happens next. You get that one issue, nothing more.

When to use it
a form, an email or another app passes along a reference to an issue and you want the issue itself in your scenario.
Watch out
each run of it counts as an operation (one execution of one module) on your plan.
Iteration X4

List Comments

SearchIn the docs only

Brings back the comments Iteration X holds, as a search that can return zero, one or many bundles. You get the conversation, not just the headline of an issue.

When to use it
right after Get an Issue, when whoever picks up a case needs to read what was already said.
Watch out
every comment becomes its own bundle, so modules placed after it run once per comment.
Iteration X5

List Project Issues

SearchIn the docs only

Collects the issues that belong to one project, which gives you a clean view of the work tied to that project. As a search, it may return nothing, one issue or many.

When to use it
you think in projects and want a per-project digest, typically chained after List Projects as in the scenario above.
Watch out
when zero issues come back, the modules after it do not run for that project.
Iteration X6

List Projects

SearchIn the docs only

Returns every project Make can see in your Iteration X account, one bundle per project. It is the natural starting point when you want to loop through your projects.

When to use it
as the first module of a scheduled scenario that reviews each project, before List Project Issues.
Watch out
each project it returns multiplies the operations spent by the modules that follow it.
Iteration X7

List Team Issues

SearchIn the docs only

Pulls the issues assigned to one team, so each team gets its own list instead of a single mixed pile. It works as a search with zero to many results.

When to use it
your support or ops people are organized by team and each lead wants only their queue sent to them.
Watch out
pair it with List Teams or Get a Team so Make knows which team to query.
Iteration X8

List Teams

SearchIn the docs only

Lists the teams set up in Iteration X, one bundle per team, which you can then feed into team-level modules such as List Team Issues.

When to use it
you want a scenario that walks through every team, for instance to send each lead their own queue.
Watch out
a team added later shows up at the next scheduled run, not the moment it is created, since the app has no trigger.
Iteration X9

Make a GraphQL Query

ActionIn the docs only

Lets you send your own GraphQL request to Iteration X (GraphQL is a query language where you describe exactly the data you want back). It is your way past the eight ready-made modules.

When to use it
none of the Get or List modules returns the piece of data your scenario needs.
Watch out
Make's Iteration X documentation is limited, so you have to know the app's query structure yourself and test with Run once.
Need help

Need help automating Iteration X with Make?

A person reads every message.

FAQ

Questions about the Iteration X Make integration

01Is the Iteration X Make integration free?
Yes. Iteration X is a standard app, so it works on the Free plan of Make. That plan has limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Your usage is counted in credits, and each operation (one module run on one item) uses one. Iteration X itself has no price listed here.
02What do you need to connect Iteration X to Make?
An Iteration X account and a Make account. Make's help pages list no specific prerequisite for this app. You add an Iteration X module, click Create a connection, name it if you want, then either authorize Make on the Iteration X page or paste the key the app provides, and click Save. Since the official documentation is limited, check that the module fields fill with your projects or teams right after saving: that tells you the connection works.
03Can an Iteration X scenario start in real time?
No. The Iteration X app in Make has no trigger module at all, neither scheduled nor instant. You still have two ways to start a scenario. The first is the schedule on the first module, every 15 minutes by default, or every minute on a paid plan. The second is to open the scenario with a trigger from another app, then use Get an Issue or List Comments to fetch the Iteration X data that goes with that event.
04What if the Iteration X module you need is missing?
It depends on what you need. The app has no Make an API Call module, but it has Make a GraphQL Query, which lets you write your own request to Iteration X when the 8 other modules fall short. Be aware that Make describes its Iteration X documentation as limited, so you will need to know the app's data structure yourself. If that is out of reach, another app may cover the need, or the team can help you scope it.
05Should you use Make or n8n for Iteration X?
It depends on your criteria, not on a winner. In Make, Iteration X comes with 9 modules and no trigger, and it is available on every plan, including Free. The same app often has an n8n node too, so check that side before you decide. Compare what each tool offers for the exact data you need, how you want the automation to start, and which editor your team already knows. The comparison page on this site lays out those criteria in detail.
Same platform

Other docs you might need on this stack.

Browse all integrations