FogBugz

FogBugz, now sold as Manuscript, is issue tracking and case management with wikis and time tracking attached. Agents open, assign, edit and resolve cases, manage projects, areas and milestones, and keep the case queue current with what happens in other systems.

91 actions API key available

Platform Documentation Capability data verified 2026-08-18

A role change reaches the flow from the HR system

Agent reads the person's new team, the projects that role covers, and the effective date

View Person and List Permitted Sections report what that account can currently reach

Agent compares current access against the role's definition and drafts only the difference

Subscribe and Set Current Filter align the queues the person actually works from

The proposed access changes post to the project owner with current and target side by side

An administrator approves any change to a person's type or group membership before it is applied

What This Integration Enables

FogBugz, sold today as Manuscript, is easy to mistake for a bug tracker. The connector's surface says otherwise. Alongside cases and milestones sit mailboxes and outbound correspondence, a full user and permission-group subsystem, working schedules and holidays, live and retrospective time tracking, source-control checkins, and a wiki with revision history. That is not a tracker with features bolted on. It is the design decision that one system should hold the work, the customer conversation about the work, the documentation of the work, and the record of who is allowed to see any of it.

For an agent, that combination is unusually productive, because most integration effort in a normal stack is spent stitching those four things together. FlowRunner agents work all four of those layers:

search and open cases the same way the search box does
move a case through a workflow whose legal transitions are ordered
reply into the customer thread that opened the case
book and correct time against cases
keep milestones and their dependencies current
write the wiki article as the work concludes

What they do not do alone is change who can reach what, and that restraint is not arbitrary. It follows from how FogBugz issues credentials, which is the subject of this page's human-in-the-loop gate.

Without FlowRunner

Access drift People accumulate project permissions across roles, and nobody has a picture of who can reach what

The case and the customer thread diverge The reply goes out from somebody's mailbox, and the case record has no idea the conversation happened

Reporting means exporting Answering "what is open, for whom, against which milestone" starts with a spreadsheet download

With FlowRunner

Access reviewed as it changes Every role change produces a stated difference between current and intended access, on the day it happens

The thread lives on the case Customer correspondence is recorded as case events, so the next person sees what was already said

Reporting reads the source Saved filters and searches are queried directly, and the numbers match what the team sees

Use Case Scenarios

Joiners, movers, and leavers, with the privileged half held back

A role change lands in BambooHR and reaches the flow. The agent reads the person's record with View Person, then calls List Permitted Sections to get the projects and wikis that account can currently reach at each level, which is the operation that answers who can see what. It compares that against the role definition and produces a difference rather than a plan: three projects to add, one group to leave, two subscriptions that no longer make sense. The unprivileged half runs immediately, because Subscribe, Unsubscribe, Set Current Filter, and Star Item change what somebody sees in their own queue and nothing else. The half that changes authority waits, and the summary posts to the project owner in Slack with both states listed.
The customer thread and the case are the same conversation

A customer emails a support address, FogBugz opens a case from it, and the agent picks it up. It reads the case, searches for related history with Search Cases using the same query syntax the search box takes, and pulls prior checkins from GitHub that reference the affected area through Record Checkin's history. Where the answer is known, it drafts a response and uses Reply To Email so the message threads correctly in the customer's inbox rather than arriving as a new conversation, and the reply is recorded on the case as an event. Where the answer is not known, Edit Case adds the research as a comment, Change Case Status moves it along the one legal transition available from its current state, and the case reaches a human with the work already done.
A release report that assembles itself

Ahead of a release, the agent reads the milestone with View Milestone, lists its open cases, and checks Add Milestone Dependency relationships to see whether an earlier milestone slipping has pushed this one. It reads List Upcoming Holidays for the people the remaining cases are assigned to, because a case assigned to somebody who is away for the next week is a schedule problem rather than a work problem. Time booked against the milestone comes from List Time Intervals with Person set to cover everybody rather than defaulting to the token's own. The result is written into a wiki article with Create Wiki Article, which keeps the report where the rest of the project documentation already lives, and posted to Google Sheets for the roll-up.

Human-in-Loop Highlight

A FogBugz API token carries the full permissions of the user who created it, there is no way to narrow its scope, and it never expires. Everything an agent does through this connector is therefore indistinguishable, to the site, from that person doing it. That is workable for cases, comments, time, and wikis, all of which leave an event trail on the record. It is not workable for the operations that change authority, and FogBugz has several. Edit Person can set a person's type, and type is a number whose values are not ordered by privilege, so the ordinary user and the administrator differ by a digit. Set Permissions with a level of None revokes access rather than leaving it unchanged. Delete Permission Group takes away whatever access that group granted to everyone in it and reserves the group's name permanently, so it cannot simply be recreated.

So the agent prepares the change and hands over the last step: "Role change for j.okafor: the new role adds write access to Platform and Billing and removes membership of the Contractors group. Applying the group removal revokes access to 4 projects and 2 wikis, listed below. The role template also sets person type to Administrator, which grants full control of the site. The token making these changes belongs to m.reyes and is not scoped. Apply all, apply without the type change, or reject?" The comparison, the impact list, and the wording of the request are the agent's work. The grant is not, because a permission granted by a never-expiring token is a decision nobody can attribute afterward unless a person made it on purpose. Set Next Case Number sits behind the same gate for a smaller reason: it moves the whole site's case counter and cannot be undone.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

91 actions

Connection and site

Check API Version Returns the API version the site runs and the oldest it still accepts. The only call that needs no token, so also the quickest way to confirm a site URL is right.
Validate Token Checks that the configured token is still live. It does not create one: tokens are generated in the FogBugz interface.
View User Settings Returns the settings of the person the token belongs to, including time zone and notification preferences.
View Site Settings Returns the site's settings, such as its name, its URL, and whether community submissions are open.

Cases

Search Cases Searches cases exactly as the search box does, so a query that works there works here. Leave the query empty to return the cases in the current filter.
List Cases Returns the cases in a saved or built-in filter, for the views people have already set up.
View Case Returns one case using the limited view an integration user is allowed. For the full record with chosen columns, use Search Cases.
Create Case Opens a case. If the token's user cannot modify the named project, FogBugz does not fail, it opens the case somewhere else, so check the project is writable first.
Edit Case Changes a case and records a comment against it. Supplying Tags replaces the case's tags, so anything left out is removed.
Change Case Status Moves a case through its workflow. The moves are ordered: active before resolve, resolved before close, closed before reopen.
Push Content To Case Adds a title and body to a case, opening a new one if no case number is given. The smallest way to get text into FogBugz, meant for notifications.
Mark Case As Viewed Clears the unread mark on a case or one of its events for the token's user, without changing the case.
Find Scout Case Looks up the case carrying a crash reporter's description, which is how a reporter finds the one case it has been appending to.
Set Next Case Number Sets the number the next case will be given. An import tool that moves the whole site's counter and cannot be undone, so it belongs behind a human decision.

Customer email

Send Email Sends an email out from a case and records it as an event. The From address has to be one of the site's own mailboxes.
Reply To Email Replies to the email that opened a case, keeping the thread together in the customer's inbox.
Forward Email Forwards a case's email to someone else, recording the forward on the case.
Add Correspondent Adds an email address to the token's user, so mail sent to it is recognized as theirs.
Remove Correspondent Removes an email address from the token's user, reporting how many rows it actually removed.

Projects and areas

List Projects Returns the projects the token's user can see, or only the writable ones on request.
View Project Returns one project by id or exact name.
Create Project Creates a project and names the person responsible. Public submission lets anyone with the site URL open a case without signing in.
List Areas Returns the areas cases can be filed under, optionally narrowed to one project.
View Area Returns one area by id, or by name within a project.
Create Area Creates an area inside a project. A primary contact of minus one inherits the project's.

Milestones

List Milestones Returns milestones, which FogBugz calls fix-fors. Without a project you get every project's plus the global ones.
View Milestone Returns one milestone by id, or by name within a project.
Create Milestone Creates a milestone. A new one is not assignable until you say so, which means no case can be filed against it yet.
Edit Milestone Changes a milestone's title, dates, or whether cases can be filed against it.
Add Milestone Dependency Records that one milestone cannot ship until another has, which is how FogBugz pushes dates forward when the earlier one slips.
Remove Milestone Dependency Removes a dependency so the later milestone is no longer held back.

Site reference data

List Categories Returns the case categories the site defines. A category decides which statuses a case may take.
View Category Returns one category and its default statuses.
List Statuses Returns the statuses a case can be set to. Statuses belong to a category, so ask within one rather than reading them mixed together.
View Status Returns one status by id, or by name within a category.
List Priorities Returns the priorities cases can be opened at, with the site default marked.
View Priority Returns one priority.
List Tags Returns every tag in use on the site, with how many cases carry each.
List Filters Returns the saved, shared, and built-in filters available, marking which is current.
Set Current Filter Sets which filter the token's user is looking at, which is what List Cases falls back to.
List Kanban Columns Returns the Kanban columns cases can be dropped into, optionally for one planner board.
List Mailboxes Returns the mailboxes the site receives customer email into. A case can only be replied to from one of these.
View Mailbox Returns one mailbox and the settings it sends replies with.
List Snippets Returns the canned text snippets people insert while writing, which is how replies stay consistent.

People

List People Returns the site's users. By default this covers active normal users only, so community, virtual, and deactivated accounts each need asking for.
View Person Returns one user by email or full name, or the token's own user when neither is given.
Create Person Creates a user. Type decides how much they can see, from a community user who sees only their own cases to an administrator who can change anything.
Edit Person Changes a user. Marking someone inactive stops them signing in without deleting them or their history, and the type field on this operation is the path by which an ordinary account becomes an administrator.

Schedules and time off

List Working Schedule Returns one person's working hours, lunch break, and working days, which is what FogBugz schedules their cases around.
List Site Holidays Returns the holidays the whole site observes, which are excluded from everyone's schedule.
List Upcoming Holidays Returns one person's holidays still to come, which is how a flow finds out who is away before assigning work.
Get Holiday Returns one holiday by id.
Create Holiday Books time off for one person, taking those days out of their schedule. The dates are UTC, which matters at the boundaries.
Edit Holiday Changes a holiday's title, dates, or the person it belongs to.

Time tracking

Start Work Starts the clock against a case for the token's user. FogBugz tracks one timer per person, so starting a second stops the first.
Stop Work Stops the running timer and writes the elapsed time onto that case.
List Time Intervals Returns tracked work. It defaults to the token's own intervals, so a timesheet report has to ask for everybody's.
View Time Interval Returns one tracked interval.
Create Time Interval Books a block of work against a case after the fact rather than timing it live. The dates are UTC, and booking for someone else needs an administrator token.
Edit Time Interval Corrects a booked interval, keeping the current value of anything left out.
Delete Time Interval Removes a booked interval, taking its hours off the case.

Subscriptions and favorites

Subscribe Subscribes a person to a case or wiki article so they are notified of changes. Subscribing somebody else needs an administrator token.
Unsubscribe Removes a subscription so a person stops being notified.
Star Item Adds a case or wiki article to somebody's favorites.
Unstar Item Removes a case or wiki article from somebody's favorites.
List Favorites Returns somebody's starred cases and articles, each row saying which kind it is.

Permissions

Set Permissions Grants or revokes access to one project or wiki, for exactly one of a person, a user group, or a built-in group. A level of None revokes access rather than leaving it unchanged.
List Permitted Sections Returns the projects or wikis a user or group can reach at a given level or better. The operation an access review is built on.
List Permission Groups Returns the user groups permissions can be granted to, and can include deleted ones, which is how a blocked name is found.
List Permission Group Members Returns the users in one group. Needs an administrator token.
Create Permission Group Creates a group to grant permissions to as a unit. Names are unique across deleted groups too, so an old name cannot be reused.
Delete Permission Group Deletes a group. Everyone in it loses whatever access it granted, and the name stays reserved afterward.
Add Person To Group Puts a user in a group, giving them everything that group can reach. Needs an administrator token.
Remove Person From Group Takes a user out of a group, removing the access it granted. Needs an administrator token.

Source control

Record Checkin Links a commit to a case so the case shows what changed. The operation a post-commit hook calls.
List Checkins Returns the commits linked to a case.

Wikis

List Wikis Returns the wikis on the site. A wiki is the container; the pages inside it are articles.
Create Wiki Creates a wiki, which starts with a root article people can branch from.
Edit Wiki Changes a wiki's title or tagline, leaving its articles untouched.
Delete Wiki Deletes a wiki and everything in it. Recoverable only through Undelete Wiki, so the id is worth keeping.
Undelete Wiki Restores a deleted wiki and its articles.

Wiki articles

List Wiki Articles Returns the articles in one wiki.
Create Wiki Article Writes a new article. Setting the author or timestamp is how an import keeps its original history.
Edit Wiki Article Writes a new revision. Supplying Tags replaces the article's tags, and the previous revision stays in the history either way.
View Wiki Article Returns an article as it stands now or as it was at an earlier revision.
List Wiki Article Revisions Returns an article's revision history, so a flow can see who changed what and when.

Wiki templates

List Wiki Templates Returns the templates that give wiki articles their look.
Create Wiki Template Creates a template. Marking it default applies it to every wiki that has not chosen one of its own.
Edit Wiki Template Writes a new revision of a template.
View Wiki Template Returns a template, current or at an earlier revision.
List Wiki Template Revisions Returns the revision history of the site's wiki templates.

Frequently Asked Questions

What can FlowRunner do with FogBugz?

FlowRunner agents can run Check API Version, Validate Token, and View User Settings in FogBugz, plus 88 more actions.

Does connecting FogBugz to FlowRunner require OAuth?

No. FogBugz connects to FlowRunner with an API key, no OAuth flow required.

Can FogBugz trigger a FlowRunner workflow automatically?

FogBugz doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with FogBugz

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us