tr Skip to content
Black Friday FlowMattic for life, 12 payments of $33.25 Or $399 once. Nothing added for splitting Ends in --Days --Hrs --Min --Sec See the deal

Create a ClickUp task for each new BugBug suite

Each time a BugBug suite run finishes, this workflow creates a task in ClickUp, so your team has a place to review the results of every run without checking BugBug by hand.

BugBug ClickUp

2 steps Setup ~5 min Used on 1.8k sites Free to import

The Create a ClickUp task for each new BugBug suite workflow on the FlowMattic canvas, with 2 steps across BugBug, ClickUp
The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Automated test suites run often, and the results are easy to miss when they only live in BugBug. Turning each finished run into a ClickUp task puts it on the board your team already works from, where someone can review it, assign it or close it.

BugBug has no trigger for a newly created suite. Its FlowMattic triggers cover test, suite and schedule runs starting and finishing, so this template uses Suite Finished: the BugBug trigger fires whenever a suite run finishes. That means a task is created every time a suite run finishes, not once per suite. A suite that runs ten times gives you ten tasks.

FlowMattic passes the run data to the ClickUp Create Task action, which adds a new task where you choose. Map values from the run into the task name and description so each task says which suite ran. As imported, runs that pass and runs that fail both create a task. You can follow each one in Task History.

Review queue for nightly regression suites

A QA lead finds one ClickUp task per finished nightly suite run each morning and closes them as the results are checked.

Release checks before a deploy

When the pre-release suite finishes in BugBug, a task appears in the release list so the developer on duty signs off on the run before shipping.

Audit trail of test runs for a client

An agency keeps one ClickUp task per finished BugBug suite run in the client's space, giving a running record of when the site was tested.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

  1. Step 1Trigger
    BugBug Suite Finished

    Starts a run whenever a BugBug suite run finishes, whatever the result. The data BugBug sends about the run is passed on for mapping in ClickUp; a test run shows exactly which values you get.

  2. Step 2Action
    ClickUp Create Task

    Adds one ClickUp task per finished suite run. Connect your ClickUp account, choose where the task goes, and map values from the BugBug run into the task name and description.

What you need

  • FlowMatticCore
  • BugBug AccountAccount
  • ClickUp AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

  • Add a Filter after the BugBug trigger that continues only when the run result reports a failure, so ClickUp gets a task only for runs that need attention. Check a test run for the exact result value.
  • Put the suite name and finish time in the ClickUp task name, so tasks from repeated runs of the same suite are easy to tell apart.
  • Run one suite in BugBug after import so FlowMattic captures the run data, then map it in the Create Task step before you turn the workflow on.

Questions about this workflow

Does creating a new suite in BugBug make a ClickUp task?

No. BugBug's triggers in FlowMattic react to runs starting or finishing, not to suites being created. A task is made each time a suite run finishes.

Will a BugBug suite that runs every day fill ClickUp with tasks?

Yes, as imported. Each finished run creates its own task. Add a Filter on the run result if you only want tasks for failed runs.

Do passing BugBug suite runs create ClickUp tasks too?

Yes. The trigger fires when a suite run finishes, whether it passed or failed. A Filter after the trigger can narrow this down.

Can a finished BugBug test, not a whole suite, create the task?

Yes. Swap the trigger for BugBug's Test Finished event, then remap the values in the ClickUp step.

Import this workflow into your WordPress site

Download the JSON, import it from the Workflows screen and connect your accounts. Every run stays on your server, with no per-task fees.

30-day money-back guarantee Unlimited workflows and runs Self-hosted

Customers who run it every day

Rated 4.8 out of 5 by customers
Read more reviews

The software works really well, and the team is adding integrations constantly, so I'm positive it eventually will catch up with Zapier. The flows are very easy to create and if you have any doubt, the team will give you great support.

Kai P.

Easy to use, familiar UI for automating all kinds of wordpress tasks. Integrating all our plugins together is key and flowmattic fits the job perfectly.