Resources · Make integration

MantisBT Make integrationAutomate MantisBT with Make.

Could your bug tracker file, update and tidy its own issues? The MantisBT Make integration gives you 15 modules: one trigger, 9 actions and 5 searches. It suits QA leads and support teams who live in MantisBT, and this page walks you from connection to a first working scenario.

Try the MantisBT integration on MakeSee the 15 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the MantisBT Make integration do?

The MantisBT Make integration links your MantisBT tracker to Make so issues and projects move without copy and paste. You build a scenario (the automation itself, a chain of modules), and each module handles one job: spotting new issues, creating or updating one, attaching a file, or reading projects.

Bug reports that file themselves. A form, a support inbox or a monitoring tool from another app feeds Create an Issue, and the report lands in the right MantisBT project with its text already written. If the reporter sent a screenshot, Add an Attachment to an Issue puts it on the same ticket.

Releases that stay in sync. When your team ships, Create a Project Version adds the new version to the project, and Update a Project keeps its details current. List Projects reads every project and sub-project your account can see, handy when one scenario has to touch several of them.

A watch on incoming issues. Watch New Issues picks up the tickets added since its last check, on the schedule you set, so you can react with Update an Issue, fetch the files with Download the Issue Files, or push the report into another tool.

One honest limit: Make says its MantisBT documentation is incomplete, because little public information exists about this app. Test each module with real data before you rely on it, and keep Make an API call in mind for anything the list does not cover. If you are still weighing platforms, read our n8n vs Make comparison, then check Make pricing before you scale up. Want help building it? Our Make agency sets up scenarios like these.

Connect

How do you connect MantisBT to Make?

  1. 01

    Add a MantisBT module

    In your scenario, click the +, search for MantisBT and pick any of its modules. The first time, Make asks for a connection: your MantisBT account linked to Make once, then reused by every MantisBT module. Click Create a connection.

  2. 02

    Name it and authorize Make

    Give the connection a name you will recognize later, such as the name of your tracker. Then follow what MantisBT asks for: either authorize Make on the MantisBT page that opens, or paste the key that MantisBT gives you.

  3. 03

    Save and check the lists

    Click Save. Once the connection exists, Make can read what your account sees, so the module can offer your projects and issues instead of asking you to type identifiers by hand.

First scenario

Your first scenario: tidy every new MantisBT issue

GoalWhen a new issue is added in MantisBT, Make updates it with the values you mapped, so every report gets the same first pass.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the editor to add the very first module.

  2. 02

    Set the trigger

    Search for MantisBT and choose Watch New Issues. Pick your connection, or click Create a connection if this is your first MantisBT module.

  3. 03

    Add the update

    Click the + on the right of the trigger, pick Update an Issue and map the issue from the trigger's bundle (one item passing from module to module) so Make changes the right ticket.

  4. 04

    Test with Run once

    Create a test issue in MantisBT, then click Run once. Open the bubbles above each module to read the bundles they received and confirm the update landed on the right issue.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set the schedule. A new scenario checks every 15 minutes by default. Then switch the scenario on so it keeps running without you.

Triggers

What can start a MantisBT scenario?

1 module starts a scenario when something happens in MantisBT. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by MantisBT as soon as it happens.

MantisBT1Watch New Issues

Watch New Issues

Scheduled trigger

In Make“Triggers when new issues are added.”

Watch New Issues hands your scenario each ticket that has been added to MantisBT since the last check, one bundle per issue, so every bug report can flow into the rest of your automation without anyone forwarding it.

How it fires
scheduled. Make checks MantisBT on the scenario's schedule, every 15 minutes by default, and on the Free plan never more often than that; paid plans go down to 1 minute.
When to use it
pick it whenever a fresh report should kick off something else, like posting it to your team chat or completing it with Update an Issue.
Watch out
each issue found costs an operation (one run of one module), so a busy tracker adds up fast.
Modules

What can Make do in MantisBT?

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

MantisBT1

Add an Attachment to an Issue

Action

In Make“Adds a file attachment to the specified issue.”

Puts a file on an existing MantisBT issue, so the screenshot, log or export that explains the bug sits right next to the report instead of in someone's inbox.

When to use it
right after Create an Issue, when the form or email that triggered the scenario carried a file the developer will need.
Watch out
on the Free plan Make handles files up to 5 MB.
MantisBT2

Create an Issue

Action

In Make“Creates a new issue.”

Opens a brand new ticket in MantisBT from data that arrived elsewhere, which means no more retyping a customer complaint or a failed test into the tracker.

When to use it
a support form, a monitoring alert or a spreadsheet row should become a bug report the moment it shows up.
Watch out
if the same scenario also watches new issues, you can create a loop, so keep the two apart.
MantisBT3

Create a Project

Action

In Make“Creates a new project.”

Sets up a new project in MantisBT for you, so a fresh client or product gets its own space in the tracker the moment the work is agreed, with no admin trip into the settings.

When to use it
a deal marked as won in your CRM, or a new product added to your catalog, should come with its own bug tracking space ready.
MantisBT4

Create a Project Version

Action

In Make“Adds a new version to a project.”

Adds a version to one of your MantisBT projects, which keeps release numbers in the tracker aligned with what your team actually ships, without a manual copy at each release.

When to use it
a release is tagged in your code host or marked done in your planning tool, and testers need that version available when they report bugs.
Watch out
map the project first, the version always belongs to one.
MantisBT5

Delete an Issue

Action

In Make“Deletes an existing issue.”

Removes a ticket from MantisBT for good. It keeps the tracker clean when test runs, spam or duplicates end up filed as real issues and nobody wants to delete them one by one.

When to use it
a filter earlier in the scenario has already confirmed the issue is junk.
Watch out
a deletion cannot be undone from Make, so test it with Run once on a throwaway issue first.
MantisBT6

Delete a Project

Action

In Make“Deletes a project by ID.”

Erases a whole MantisBT project, found by its ID, which helps when temporary projects pile up and clutter the list your testers pick from.

When to use it
a sandbox or demo project was created by another scenario and its job is finished.
Watch out
this is the most destructive module of the app; put a filter before it and never feed it a list you have not checked.
MantisBT7

Make an API call

Action

In Make“Performs an arbitrary authorized API call.”

Lets you call any endpoint of the MantisBT API with the connection you already set up, so you are not stuck when the other modules do not cover your case.

When to use it
you need an operation that has no dedicated module, and you know which endpoint handles it.
Watch out
you write the request yourself, so keep the MantisBT API reference open next to the editor while you build.
MantisBT8

Update an Issue

Action

In Make“Updates an existing issue.”

Changes an issue that already exists, so the ticket reflects what happened outside MantisBT: a fix deployed, a customer reply, a new detail from support.

When to use it
another tool knows something new about a bug and the tracker should say so too, or a fresh issue from Watch New Issues needs a first pass.
Watch out
map the right issue ID, or Make edits the wrong ticket.
MantisBT9

Update a Project

Action

In Make“Updates an existing project.”

Edits an existing MantisBT project so its details match the source of truth you keep elsewhere, which spares you from maintaining the same information in two places.

When to use it
a client or product record changes in your CRM or catalog and the matching project should follow.
Watch out
find the project with Get a Project or List Projects first, then map its ID here.
MantisBT10

Download the Issue Files

Search

In Make“Downloads all files of the specified issue. Can be filtered by file's ID.”

Fetches every file attached to a given issue and passes them on, so you can archive them or send them to another app. You can also filter by a file's ID when you only need one.

When to use it
attachments from a closed bug should end up in your cloud storage, or a reviewer needs them in a chat message.
Watch out
each file is a separate bundle, so the next module runs once per file.
MantisBT11

Get an Issue

Search

In Make“Returns an issue by its ID.”

Reads one MantisBT issue from its ID and returns its details, which gives the next modules everything they need about that ticket without searching the whole tracker.

When to use it
another app only stores the issue number, for example a support ticket linked to a bug, and you want the full report to write a reply.
Watch out
no ID, no result; map it from an earlier module.
MantisBT12

Get a Project

Search

In Make“Returns a project by its ID.”

Returns a single project from its ID, so a scenario can check what a project looks like before it creates versions or issues inside it.

When to use it
you already know the project ID from another system and want its current details in the scenario, for a report or a decision in a filter.
Watch out
to find an ID you do not have yet, use List Projects instead.
MantisBT13

List all Issues

Search

In Make“Returns the list of issues. Can be filtered by their status or by a project.”

Pulls a list of issues out of MantisBT, which you can narrow down by status or by project, and turns it into data you can sort, count or send somewhere else.

When to use it
building a digest of open bugs for one project, or feeding a dashboard in a spreadsheet.
Watch out
a search returns several bundles, one per issue, and every following module runs for each of them, which uses operations.
MantisBT14

List Projects

Search

In Make“Returns all projects and sub-projects accessible to the user.”

Brings back every project and sub-project your MantisBT account can reach, a quick way to loop over the whole tracker without keeping a list of IDs by hand.

When to use it
a scenario has to act on each project, like adding the same release version everywhere, or you need to spot one by its name.
Watch out
the result depends on the rights of the connected account.
Need help

Need help automating MantisBT with Make?

A person reads every message.

FAQ

MantisBT and Make: common questions

01Is the MantisBT Make integration free?
Yes, MantisBT is a standard app in Make, so it works from the Free plan onward. The Free plan has limits, though: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lift those limits, with runs down to every minute and unlimited active scenarios. Usage is counted in operations, one per module run on each bundle, so a scenario that handles many issues uses more of your monthly allowance.
02What do you need to connect MantisBT to Make?
You need a MantisBT account and a Make account. Make's documentation lists no prerequisites and no official connection steps for MantisBT, so the usual Make flow applies: add a MantisBT module, click Create a connection, give it a name if you like, then either authorize Make on the MantisBT page or paste the key MantisBT gives you, and click Save. The connection is created once and reused by all 15 MantisBT modules in every scenario you build.
03Does the MantisBT trigger in Make fire instantly?
No. Watch New Issues is a scheduled trigger: Make asks MantisBT for new issues on the scenario's schedule instead of being told the moment one is created. A new scenario checks every 15 minutes by default. On the Free plan that is also the shortest gap allowed, while paid plans can check every minute. You set the rhythm with the clock on the first module. For most bug tracking flows this delay is fine, since a report handled a few minutes later still reaches the right person.
04What if a MantisBT module is missing in Make?
Use Make an API call. It reaches any endpoint of the MantisBT API with the connection you already have, so you can cover what the other modules do not. Keep in mind that Make describes its MantisBT documentation as limited, due to little public information about the app, which means you should test every module with Run once on sample data. Start with a call that only reads data, run it once and look at the bundle it returns before you map anything into the next module.
05Should you use Make or n8n for MantisBT?
It depends on the team. The same app often has an n8n node too, so check that the operations you need exist on both sides before you choose. Make gives you 15 ready modules for MantisBT, a visual editor where each step is a bubble, and the Make an API call module for the rest. Compare the modules each tool offers for your exact use case, build a small test flow and keep the one your team maintains most comfortably. The comparison page on this site goes further.
Same platform

Other docs you might need on this stack.

Browse all integrations