Skip to main content

Make Waves ’26 Step into AI’s glass box. Prague, 19–20 Oct.

Register now (opens in a new tab)
FogBugz
WordPress

Connect FogBugz and WordPress

Explore ready-made FogBugz and WordPress templates and start automating in minutes.

Get started free

Create a custom workflow

Integrate FogBugz with WordPress and automate the work that moves between them — no code required.

Create a custom workflow

Every automation starts with a trigger and an action. Select one from each app to generate a workflow tailored to your needs.

FogBugz
Trigger: Watch Areas
WordPress
Action: Select an action
1. Select a trigger

  • Triggers when a new area is created.

  • Triggers when a case has been assigned.

  • Triggers when a case has been closed.

  • Triggers when a case has been edited.

  • Triggers when a case email event has been occured.

  • Triggers when a case email has been forwarded.

  • Triggers when a case email has been received.

  • Triggers when a case email has been replied.

  • Triggers when a case email has been sent.

  • Triggers when a case email has been sorted.

  • Triggers when a case event has occured.

  • Triggers when a case has been opened.

  • Triggers when a case has been reactivated.

  • Triggers when a case has been reopened.

  • Triggers when a case has been resolved.

  • Triggers when a case status has been changed.

  • Triggers when a new category is created.

  • Triggers when a new milestone is created.

  • Triggers when a new project is created.

  • Triggers when a new status is created.

  • Triggers when a new tag is created.

  • Triggers when a new user is created.

2. Select an action

  • Creates a category.

  • Creates a comment.

  • Creates a media item.

  • Creates a post.

  • Creates a tag.

  • Creates a user.

  • Deletes a category specified by its ID.

  • Deletes a comment specified by its ID.

  • Deletes a media item specified by its ID.

  • Deletes a post specified by its ID.

  • Deletes a tag specified by its ID.

  • Deletes a user specified by its ID.

  • Returns info about a category specified by its ID.

  • Returns info about a comment specified by its ID.

  • Returns info about a media item specified by its ID.

  • Returns info about a post specified by its ID.

  • Returns info about a tag specified by its ID.

  • Returns info about a user specified by its ID.

  • Performs an arbitrary authorized API call.

  • Updates a category specified by its ID.

  • Updates a comment specified by its ID.

  • Updates a media item specified by its ID.

  • Updates a post specified by its ID.

  • Updates a tag specified by its ID.

  • Updates a user specified by its ID.

Select a trigger and an action

Create workflow (opens in a new tab)

Triggers and actions

Explore what you can automate between FogBugz and WordPress.

Add a Milestone Dependency
Creates a dependency between two milestones.
Action
Assign a Case
Updates and assigns a specific case to a person specified.
Action
Close a Case
Updates and closes a specific case. Person Assigned to ID will be set to 1.
Action
Create a Case
Creates a new case.
Action
Create a Category
Creates a category.
Action
Create a Comment
Creates a comment.
Action
Create a Media Item
Creates a media item.
Action
Create a Milestone
Creates a new milestone.
Action
Create a Post
Creates a post.
Action
Load more

Support

FAQs

Everything you need to know about Make. Can't find the answer you're looking for? Please chat to our team.

Start by registering for Make. As a new Make user, you’ll automatically be assigned a free account. Once your account is set up, you can start creating your first scenarios. We recommend starting with our step-by-step video tutorial.

A scenario represents a workflow or a project of your own creation, and it is made up of a series of modules that automate apps and services. Creating a scenario allows you to transfer and transform data between apps and services via these modules to automate anything and improve the way you work.

Modules are the main building blocks of automation in Make. Modules represent actions that Make performs with an app, like creating, updating, or deleting data.

Mapping links the modules in your scenario. When you map an item, you connect the data retrieved by one module to another module to perform the desired action. For example, you can map email addresses and subject lines to create a spreadsheet using this data.