Resources · Make integration

Yodiz Make integrationAutomate Yodiz with Make.

Can Make keep Yodiz in step with the rest of your tools? Yes: the Yodiz Make integration offers 14 modules, 3 of them triggers. This page shows agile teams how to connect their account and build a first scenario, one click at a time.

Try the Yodiz integration on MakeSee the 14 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Yodiz Make integration do for your team?

The Yodiz Make integration links your Yodiz account to Make, a no-code tool where you build scenarios, meaning automations made of modules chained one after the other. Yodiz brings 14 modules: 3 triggers that spot new issues, tasks and user stories, 7 actions and 4 searches. What happens in your agile tracker can flow to other apps, and the reverse.

Bugs reported by customers land in the tracker. A support form feeds Create an Issue, and the issue shows up in the right project without anyone retyping it.

New stories reach the people who build them. Watch New User Stories spots each story added to the backlog and sends it to the design team's channel or to a planning sheet.

Sprint reports fill themselves in. List User Stories followed by List Tasks gathers the work of a project into a spreadsheet ready for the review meeting.

What the modules do not cover: every trigger is scheduled, so Make checks Yodiz at an interval instead of hearing about changes the moment they happen, and the list has no module to update or delete an item. For those gaps, Make an API Call reaches the Yodiz API directly. If you are still weighing tools, the n8n vs Make comparison sets out the criteria, and the Make training walks you through your first builds. Stuck on an error later? Head to Make troubleshooting.

Connect

How do you connect Yodiz to Make?

  1. 01

    Generate your Yodiz API key

    In Yodiz, open the Settings icon at the top right, choose Yodiz API in the header menu and press Generate API Key. Copy the key shown on screen and keep it at hand for the next step.

  2. 02

    Add a Yodiz module and create the connection

    In your Make scenario, add any Yodiz module and click Create a connection. A connection is your Yodiz account linked to Make once, then reused by every Yodiz module. Type a label in Connection name if you manage several accounts.

  3. 03

    Paste the key and confirm

    Paste the API key into the connection window, or follow the instructions Make shows on screen, then confirm. Once the connection exists, Make lists the projects and items it can read, so you choose from a menu instead of typing IDs.

First scenario

Your first scenario: turn a bug form into a Yodiz issue

GoalWhen a customer submits a bug report through your form app, Make creates a matching issue in Yodiz.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the + to add the first module. That first module is the trigger of your form app, where the bug reports arrive.

  2. 02

    Add Create an Issue

    Click the + on the right of the form module, search for Yodiz and pick Create an Issue. Click Create a connection and paste the API key you generated earlier.

  3. 03

    Map the form answers

    Pick the project from the list Make offers once the connection works. Then drag the answers of the form into the fields of the issue, so each report carries what the customer wrote.

  4. 04

    Test with Run once

    Send a test answer through your form, then click Run once. Read the bundle each module received, then open Yodiz and check that the new issue sits in the right project.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, and switch the scenario on. From then on, each new bug report becomes a Yodiz issue with no copy and paste.

Triggers

What can start a Yodiz scenario?

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

Yodiz1Watch New Issues

Watch New Issues

Scheduled trigger

In Make“Triggers when a new issue is created.”

Watch New Issues starts your scenario whenever someone logs a new issue in Yodiz, and hands Make that issue as a bundle, the single item passed on to the next module. The bug or request then reaches your other tools without anyone copying it by hand.

How it fires
scheduled. Make checks Yodiz on the scenario's schedule, every 15 minutes by default, and each new issue it finds becomes one bundle.
When to use it
your QA lead logs bugs in Yodiz and support wants each one posted in the team chat or a tracking sheet.
Watch out
on the Free plan the shortest interval is 15 minutes, so a fresh issue can wait that long before Make sees it.
Yodiz2Watch New Tasks

Watch New Tasks

Scheduled trigger

In Make“Triggers when a new task is created.”

Every new task created in Yodiz can kick off a scenario with this trigger. Make receives the task as a bundle and passes it to whatever module you add next, so the person who owns the follow-up hears about it without opening Yodiz.

How it fires
scheduled: Make checks Yodiz on the scenario's schedule, which is every 15 minutes for a new scenario.
When to use it
developers split a story into tasks and a project manager wants each task copied into a planning sheet.
Watch out
the trigger reacts to creation only, as its name says. A task that changes later does not start the scenario a second time.
Yodiz3Watch New User Stories

Watch New User Stories

Scheduled trigger

In Make“Triggers when a new user story is created.”

When a product owner adds a user story in Yodiz, Watch New User Stories turns it into the starting point of a scenario. From that one bundle you can announce the story, open a task with Create a Task, or log it in another app.

How it fires
scheduled, with Make asking Yodiz for new stories on the scenario's schedule, every 15 minutes unless you change it.
When to use it
backlog grooming produces new stories and the design team needs each one on its own board.
Watch out
paid plans let the interval drop to 1 minute, while the Free plan keeps a 15 minutes minimum, which matters if stakeholders expect quick notice.
Modules

What else can Make do in Yodiz?

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

Yodiz1

Create an Issue

Action

In Make“Creates a new issue.”

Create an Issue files a new issue in Yodiz from data that arrives somewhere else: a support form, an email, a row in a sheet. Your team then finds the bug in the tracker instead of buried in an inbox.

When to use it
a customer reports a problem through a form and you want it logged in the right Yodiz project without retyping.
Watch out
each run creates one issue per bundle, so a Run once test on real data leaves real issues behind.
Yodiz2

Create a Task

Action

In Make“Creates a new task.”

With Create a Task, a scenario adds work items to Yodiz for you. It suits repeatable steps that follow an event, like a checklist item that should exist whenever a new story or issue appears.

When to use it
after Watch New User Stories fires, add a standard task such as writing test cases so nobody forgets it.
Watch out
the module creates a task each time it receives a bundle, so check with Run once before switching the scenario on.
Yodiz3

Create a User Story

Action

In Make“Creates a new user story.”

This module writes a fresh user story into a Yodiz project, so requests collected outside the tool reach the backlog as proper stories. The product owner reviews them in Yodiz, where the team already plans its sprints.

When to use it
feature ideas come in through a feedback form and you want each one queued as a story.
Watch out
Make lists the projects it can read once the connection works, so pick the project from that list instead of typing a value.
Yodiz4

Get an Issue

Action

In Make“Retrieves issue by its ID.”

Get an Issue fetches one issue when you already know its ID and hands its details to the next module. It fills the gap when an earlier step only carries a reference, not the content.

When to use it
a chat message or a sheet row mentions an issue ID and you need the issue itself before replying.
Watch out
it works from an exact ID; if all you know is the project, start with List Issues instead.
Yodiz5

Get a Task

Action

In Make“Retrieves task by its ID.”

Pull a single Yodiz task into your scenario by its ID with Get a Task. The result is one bundle you can map into an email, a report or another app, so the task reads the same everywhere.

When to use it
another tool stores the task ID and you want its current version before sending an update to a client.
Watch out
without an ID, reach the task through List Tasks and the user story it belongs to.
Yodiz6

Get a User Story

Action

In Make“Retrieves user story by its ID.”

Get a User Story brings back one story, found by its ID, so later modules can read its details. Think of it as the lookup step before you announce, copy or report on a story.

When to use it
a draft release note lists story IDs and you want each story's content added to it automatically.
Watch out
one run returns one story; to go through a whole project, List User Stories is the better starting point.
Yodiz7

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call is the way out when no listed module fits: it calls any endpoint of the Yodiz API with the connection you already set up. You reach what the other modules leave aside, such as editing or removing an item, if the API offers it.

When to use it
you need an action missing from the list, for example changing an item after a deploy.
Watch out
you write the request yourself, so keep the Yodiz API documentation open while you set it up.
Yodiz8

List Issues

Search

In Make“Lists all issues of the selected project or user story.”

List Issues returns every issue of a chosen project or user story, one bundle per issue. It is how you build a digest or a tally without exporting anything from Yodiz.

When to use it
a sprint review needs all the issues of a story gathered into one sheet.
Watch out
a search can return zero, one or many bundles, and each following module runs once per bundle. Every run is an operation, the unit Make counts on your plan.
Yodiz9

List Projects

Search

In Make“Lists all projects.”

Before you reach stories or issues project by project, you often need the projects themselves: List Projects returns all of them from your Yodiz account. Each project arrives as its own bundle.

When to use it
you want a portfolio overview in a spreadsheet, one row per project.
Watch out
chaining List Projects into List User Stories multiplies bundles fast, so run it once to see the volume before you schedule it.
Yodiz10

List Tasks

Search

In Make“Lists all tasks of the selected user story.”

Pick a user story and List Tasks hands you all its tasks, one bundle each. Handy for copying a story's work items into a teammate's to-do app or into a checklist.

When to use it
a story is about to ship and the tester wants the full task list in one message.
Watch out
the search works per user story, not per project; for a whole project, place List User Stories in front of it.
Yodiz11

List User Stories

Search

In Make“Lists all user stories of the selected project.”

List User Stories collects the stories of one project, each as a bundle ready for the next module. Use it to feed a backlog report, a planning sheet or a round of notifications.

When to use it
the product owner prepares a planning meeting and wants the project's stories copied into a shared document.
Watch out
every story that comes out triggers one run of the following modules, so a large project spends more operations than you might expect.
Need help

Need help automating Yodiz with Make?

A person reads every message.

FAQ

Questions about Yodiz and Make

01Is the Yodiz Make integration free?
Yes. Yodiz is a standard app in Make, so it works from the Free plan onward. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run and files up to 5 MB, with 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, lift the cap on active scenarios, allow 40 minutes of execution and count usage in credits, meaning operations, each month. Your Yodiz subscription is separate and handled by Yodiz.
02What do you need to connect Yodiz to Make?
An active Yodiz account and an API key. You generate the key in Yodiz from the Settings icon, in the Yodiz API menu, with the Generate API Key button. In Make, add any Yodiz module, click Create a connection, give it a name if you like and paste the key. That single connection then serves all 14 Yodiz modules in every scenario you build, so you set it up once per account rather than once per module.
03Do Yodiz triggers in Make fire in real time?
No. The 3 Yodiz triggers, Watch New Issues, Watch New Tasks and Watch New User Stories, are scheduled. Make checks Yodiz on the scenario's schedule, which is every 15 minutes for a new scenario. On the Free plan, 15 minutes is also the shortest interval, while paid plans go down to 1 minute. Yodiz has no instant trigger in Make, so there is no webhook option for it. If the wait matters for your team, shorten the schedule on a paid plan.
04What if a Yodiz module is missing in Make?
Use Make an API Call. This module calls any endpoint of the Yodiz API with the connection you already created, so it covers what the other listed modules leave out, such as editing or removing an item if the API allows it. Look up the endpoint and the data it expects in the Yodiz API documentation. Note that the Make help page for Yodiz is AI-generated and may contain mistakes, so confirm important details with Yodiz directly.
05Make or n8n for Yodiz?
It depends on your criteria, not on a universal winner. On Make, Yodiz comes with 14 modules, 3 scheduled triggers and a universal API module, all usable from the Free plan. n8n is a separate automation tool, and many apps have a node there as well; check whether Yodiz is one of them before you compare. The n8n vs Make comparison on this site lays out the criteria side by side without ranking one tool above the other, which helps you decide on your own terms.
Same platform

Other docs you might need on this stack.

Browse all integrations