Resources · Make integration

FogBugz Make integrationAutomate FogBugz with Make.

Can Make keep your FogBugz projects, milestones and users in order without manual clicks? The FogBugz Make integration gives you 24 modules: 7 triggers, 13 actions and 4 searches. This guide is for team leads who know FogBugz and want a first working scenario, then a clear picture of each module.

Try the FogBugz integration on MakeSee the 24 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the FogBugz Make integration let you automate?

The FogBugz Make integration links your FogBugz account to Make, a tool where you build a scenario: an automation made of modules, each one a brick that watches, creates, reads or lists something in an app. Here the modules cover projects, milestones, areas and users, so the setup work around a new project can run on its own.

A project that arrives ready to plan. Watch Projects spots each new project, then Create a Milestone and Add a Milestone Dependency lay down its first planning steps, so nobody starts from an empty board.

Onboarding that follows the hiring. When a new person joins, Create a User opens the FogBugz account from data sent by another app, and Update a User adjusts it later. Watch Users does the reverse and tells other tools that someone was added in FogBugz.

A structure copied elsewhere. List Projects and List Areas return your current setup as bundles (one item per project or area) that the next module can write into a sheet or a report.

Know the limits before you build: every trigger here is scheduled, so Make checks FogBugz on the scenario's schedule instead of hearing about changes the moment they happen. None of the listed modules touches cases directly; Make an API Call is the way to reach anything else the FogBugz API offers. The Make documentation for this app also warns that it is AI-generated from the vendor docs, so double-check a detail before you rely on it. If you also use n8n, FogBugz often has a node there too, and the n8n vs Make comparison lays out how the two tools work. For the plan side, read Make pricing; for hands-on help, the Make training covers scenario building from scratch.

Connect

How do you connect FogBugz to Make?

  1. 01

    Create an API token in FogBugz

    A connection is your FogBugz account linked to Make once, then reused by every FogBugz module. It needs an API token: in FogBugz, open the Avatar Menu, click User Options, then Create API Token, and copy the token shown on screen.

  2. 02

    Add a FogBugz module and open the connection

    In your Make scenario, add any FogBugz module, then click Create a connection. The Connection name field is optional; a name like the FogBugz site you use helps when you run several accounts.

  3. 03

    Paste the token and save

    Enter the credentials you copied from FogBugz, or follow the instructions Make shows on screen, and save. From then on, every FogBugz module in any scenario can pick this connection from a dropdown instead of asking again.

First scenario

Build your first scenario: a milestone for every new project

GoalWhen a new project appears in FogBugz, Make creates its first milestone right away.

  1. 01

    Start a blank scenario

    From the Scenarios page, create a new scenario and click the big + to place the first module on the canvas.

  2. 02

    Pick Watch Projects

    Search for FogBugz, choose Watch Projects and select the connection you created, or click Create a connection if this is your first FogBugz module.

  3. 03

    Add Create a Milestone

    Click the + on the right of the trigger, pick Create a Milestone, then map the project coming from Watch Projects into the milestone so it lands in the right place.

  4. 04

    Test with Run once

    Create a test project in FogBugz, then click Run once. Open the bubbles above each module to read the bundles they received and check the milestone in FogBugz.

  5. 05

    Schedule and switch it on

    On the first module, set the schedule (every 15 minutes by default, never shorter than that on the Free plan) and switch the scenario on. Each new project now gets its milestone.

Triggers

What can start a FogBugz scenario?

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

FogBugz1Watch Areas

Watch Areas

Scheduled trigger

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

Hear about every area someone adds to a FogBugz project, and pass it to the rest of your scenario as a fresh bundle you can copy, announce or log.

How it fires
scheduled. Make checks the app on the scenario's schedule and picks up the areas created since its last look.
When to use it
your support lead maintains a spreadsheet of product areas and wants new ones to appear there without retyping them.
Watch out
it reacts to new areas only; a renamed area does not start the scenario.
FogBugz2Watch Categories

Watch Categories

Scheduled trigger

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

Get a signal each time a new category shows up in FogBugz, so changes to how your team classifies work never go unnoticed by the tools downstream.

How it fires
scheduled. Make checks the app on the scenario's schedule, so a category created a moment ago waits for the next check.
When to use it
an admin adds a category and the reporting sheet or the chat channel of the team should learn about it without a manual note.
Watch out
categories are rarely created, so most checks return nothing; that is normal, not a broken scenario.
FogBugz3Watch Milestones

Watch Milestones

Scheduled trigger

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

Catch every new milestone in FogBugz and send it where your planning actually happens, such as a shared calendar tool or a project channel.

How it fires
scheduled. Make checks the app on the scenario's schedule and returns one bundle per milestone created since the previous check.
When to use it
a product manager wants each new release milestone announced to the wider team as soon as it exists in FogBugz.
Watch out
if the same scenario also creates milestones with Create a Milestone, those will come back through this trigger; filter them or keep the two flows apart.
FogBugz4Watch Projects

Watch Projects

Scheduled trigger

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

Start a scenario the moment Make finds a new FogBugz project, which makes it the natural entry point for any setup routine you repeat per project.

How it fires
scheduled. Make checks the app on the scenario's schedule, so the delay between creation and reaction depends on that schedule.
When to use it
every new client project needs the same first milestone, areas and a message to the account manager.
Watch out
on the Free plan the shortest interval is 15 minutes, so a project created right after a check waits for the next one.
FogBugz5Watch Statuses

Watch Statuses

Scheduled trigger

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

Learn when a new status joins your FogBugz workflow, so dashboards and mappings in other tools can be adjusted before they fall out of sync.

How it fires
scheduled. Make checks the app on the scenario's schedule and lists the statuses added since it last looked.
When to use it
a reporting sheet groups work by status and silently breaks when a new status appears; this trigger warns the person who maintains it.
Watch out
it tracks the creation of a status, not a case moving from one status to another.
FogBugz6Watch Tags

Watch Tags

Scheduled trigger

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

Spot each tag that appears in FogBugz and keep a clean, shared vocabulary instead of discovering duplicates weeks later.

How it fires
scheduled. Make checks the app on the scenario's schedule and brings back one bundle per new tag.
When to use it
a QA lead reviews new tags to merge near duplicates like two spellings of the same feature, and wants a message for each one.
Watch out
tags are created freely by users, so this trigger can fire often; each bundle processed counts as operations on your plan.
FogBugz7Watch Users

Watch Users

Scheduled trigger

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

Know when a person gets a FogBugz account, and use that moment to set up the rest of their tools or tell their manager.

How it fires
scheduled. Make checks the app on the scenario's schedule and returns each user created since the last run.
When to use it
IT adds people in FogBugz first and wants a welcome message or a row in the access register to follow.
Watch out
it reports new accounts only; editing a profile later does not start the scenario again.
Modules

What can FogBugz do inside a scenario?

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

FogBugz1

Add a Milestone Dependency

Action

In Make“Creates a dependency between two milestones.”

Tie two milestones together so FogBugz knows one comes after the other, and your plan reflects real order instead of two floating dates.

When to use it
right after Create a Milestone builds a beta and a release milestone for a new project, link them in the same run.
Watch out
both milestones must exist first, so place this module after the ones that create or find them.
FogBugz2

Create a Milestone

Action

In Make“Creates a new milestone.”

Adds a new milestone in FogBugz from data your scenario already has, which saves retyping release plans from another tool.

When to use it
a new project arrives through Watch Projects and should get its kickoff milestone without anyone opening FogBugz.
Watch out
run the scenario twice on the same data and you get two milestones; check first with List Milestones if duplicates matter.
FogBugz3

Create an Area

Action

In Make“Creates a new area.”

Sets up a fresh area inside a FogBugz project, so incoming work has a place to land from day one.

When to use it
every new client project needs the same few areas, and you would rather have Make add them after Watch Projects than click through them by hand.
Watch out
map the project from an earlier module, otherwise the area has nowhere to attach.
FogBugz4

Create a Project

Action

In Make“Creates a new project.”

Opens a brand new FogBugz project from an event in another app, such as a deal marked as won or a form submitted by a client.

When to use it
sales closes a contract in the CRM and engineering should find the matching project waiting in FogBugz.
Watch out
no module here deletes a project, so a test run leaves a real project behind; test with a clearly named dummy and remove it yourself.
FogBugz5

Create a User

Action

In Make“Allows you to create a new user.”

Gives a new colleague a FogBugz account straight from your hiring or HR tool, with no ticket to IT.

When to use it
a row added to the onboarding sheet for a developer should end with that person able to log in to FogBugz.
Watch out
a test with Run once creates a real account, so use a test address you can clean up afterward.
FogBugz6

Delete a Milestone Dependency

Action

In Make“Removes a dependency between two milestones.”

Removes the link between two milestones, leaving both milestones in place, which frees one of them when plans change.

When to use it
a release is split and its milestone no longer waits on the one before it.
Watch out
the removal is not undone by Make; if a wrong pair is mapped, you rebuild the link with Add a Milestone Dependency.
FogBugz7

Get a Milestone

Action

In Make“Views information about a milestone.”

Reads one milestone you already know and hands its details to the next module, so a message or a report can quote it correctly.

When to use it
another app sends you a milestone reference and you need the full record before you post an update.
Watch out
it expects one specific milestone; to look across several, List Milestones is the better pick.
FogBugz8

Get an Area

Action

In Make“Views details of a particular area.”

Fetches the details of a single area, useful when the next step needs the full record of one area you already know.

When to use it
after Watch Areas, pull the area's full record before writing it into the team's documentation page.
Watch out
every call is one operation on your plan, so skip it if the trigger already carries what you need.
FogBugz9

Get a Project

Action

In Make“Views details of a particular project.”

Looks up one FogBugz project and hands its record to the next modules, so they reuse it instead of asking you again.

When to use it
a scenario that starts in a CRM needs the matching project's details to write a clean summary for the client.
Watch out
you need the project reference first; when you only know a name, start with List Projects.
FogBugz10

Get a User

Action

In Make“Allows you to view a user.”

Pulls one person's FogBugz profile so other modules can address them, notify them or copy their details elsewhere.

When to use it
a new milestone should be announced to its owner, and you want their record before sending the message.
Watch out
it needs one precise user; when you only have a name or an email, find the person with List Users first.
FogBugz11

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the FogBugz API with the same connection, which covers whatever the ready-made modules leave out.

When to use it
you need something the other modules do not handle, such as work on cases, and the FogBugz API documents it.
Watch out
you write the request yourself, so keep the FogBugz API reference open and test with Run once before you switch the scenario on.
FogBugz12

Update a Milestone

Action

In Make“Edits an existing milestone.”

Changes an existing milestone so FogBugz keeps matching the plan when a date or a name moves in another tool.

When to use it
the release date shifts in your roadmap sheet and the FogBugz milestone should follow without a second edit.
Watch out
point it at the right milestone first, found with List Milestones or Get a Milestone, or the change lands on the wrong release.
FogBugz13

Update a User

Action

In Make“Allows you to edit an existing user.”

Edits a FogBugz user when their details change somewhere else, so you do not maintain the same person in two places.

When to use it
HR updates a job title or an email and FogBugz should reflect it after the next run.
Watch out
try it with Run once on your own profile before you point it at a colleague, since the edit applies to a real account.
FogBugz14

List Areas

Search

In Make“Gets a list of areas.”

Returns your areas as a series of bundles, one per area, ready to be written into a sheet or compared with another list.

When to use it
before Create an Area, check whether the area already exists so you do not add it twice.
Watch out
each area becomes its own bundle, and every following module runs once per bundle, which adds up in operations.
FogBugz15

List Milestones

Search

In Make“Lists all of the milestones.”

Gathers all your milestones in one pass, which is the quickest way to feed a release calendar or an overview report.

When to use it
a scenario started by a webhook from another app rebuilds the release overview whenever someone asks for it.
Watch out
it can return nothing, one or many bundles; plan what the next module does in each case.
FogBugz16

List Projects

Search

In Make“Gets a list of projects.”

Brings back the list of FogBugz projects so you can loop over them or find the one that matches a name from another app.

When to use it
a client email mentions a project by name and the scenario must find its reference before calling Get a Project.
Watch out
without a filter step after it, every project flows to the next module.
FogBugz17

List Users

Search

In Make“Allows you to list users from the site.”

Pulls the people of your FogBugz site as separate bundles, a handy base for an access review or a directory sync.

When to use it
IT wants to compare FogBugz accounts with the staff list and flag anyone who left.
Watch out
the module's key is listPeople even though Make shows it as List Users, so search for both names in shared blueprints.
Need help

Need help automating FogBugz with Make?

A person reads every message.

FAQ

FogBugz and Make: common questions

01Is the FogBugz Make integration free?
Yes, FogBugz is a standard app, so it works from the Make Free plan. That plan allows 2 active scenarios, runs a scheduled scenario at most every 15 minutes, stops an execution after 5 minutes and caps transfer at 512 MB. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and remove the limit on active scenarios. Usage is counted in operations, one per module per bundle, so a list that returns many areas costs more than a single lookup. Your FogBugz subscription is separate.
02What do you need to connect FogBugz to Make?
An active FogBugz account and an API token. In FogBugz, open the Avatar Menu, go to User Options, click Create API Token and copy it. Then add a FogBugz module in Make, click Create a connection, optionally name it, and paste the credentials. One connection serves every FogBugz module in all your scenarios, so you never repeat the setup. If Make shows its own on-screen instructions while you connect, follow them instead of guessing; they replace the paste step. Keep the token somewhere safe, since the connection depends on it.
03Do FogBugz triggers in Make work in real time?
No. All 7 FogBugz triggers are scheduled: Make checks FogBugz on the scenario's schedule and processes what was created since the last check. A new scenario is set to every 15 minutes by default, which is also the shortest interval on the Free plan; paid plans go down to 1 minute. There is no instant trigger for FogBugz in Make, so if you need a faster reaction, the event has to come from another app that can call Make through a webhook.
04What if a FogBugz module is missing in Make?
Use Make an API Call. It reaches any endpoint of the FogBugz API with the connection you already have, which matters here because the listed modules cover projects, milestones, areas and users but not cases. You write the request from the FogBugz API documentation and test it with Run once. The Make help page for this app says it was AI-generated from the vendor docs, so confirm important details with FogBugz directly.
05Should you use Make or n8n for FogBugz?
It depends on which tool your team already builds in. Make offers 24 FogBugz modules, from Watch Projects to List Users, plus Make an API Call for the rest, and a visual editor where you test with Run once. FogBugz often has an n8n node as well. Compare the modules each tool lists for the actions you need, then pick the one your team will actually maintain; the comparison page linked above explains how the two tools differ.
Same platform

Other docs you might need on this stack.

Browse all integrations