Create ClickUp tasks from Zerowork.io TaskBot runs
When a Zerowork.io TaskBot sends its run data to this workflow’s webhook URL, FlowMattic creates a new task in ClickUp from it, so work your bot gathers ends up in your project space.
ClickUp2 steps Setup ~5 min Used on 1.0k sites Productivity Free to import

What this workflow does
Zerowork.io TaskBots collect data from the web for you, but the results often need a person to act on them. If your team plans its work in ClickUp, the useful step is to turn each bot run into a task someone can pick up. Here, each bot run becomes a ClickUp task automatically.
Runs begin at a Webhook trigger, which gives you a URL, and you set your TaskBot to send an HTTP request to it with the data you want passed on. Each request that reaches the URL starts a run. FlowMattic then calls ClickUp with Create Task and builds the new task from the values in the request, mapped the way you choose.
Zerowork's own FlowMattic trigger also works by receiving an HTTP request from a TaskBot, so the generic webhook does the same job here. Every request creates one task. To keep strangers from posting to the URL, turn on the webhook's authentication setting.
Leads scraped by a bot, followed up in ClickUp
A TaskBot collects contact details from a directory. Each record it sends becomes a ClickUp task for a sales rep to research and contact.
Price or listing checks that need review
Your bot checks listings and sends what it found. Each request opens a ClickUp task so someone on the team reviews the result.
Content research queue
A TaskBot gathers article links on a topic. Every link it posts turns into a task in your content team's ClickUp space.
How this workflow runs
What happens at each step once the workflow is on, and what you need before you import it.
Webhook Capture Webhook ResponseGives you a webhook URL and waits for requests. Set your Zerowork.io TaskBot to send an HTTP request there, and each request's data is passed to ClickUp.
ClickUp Create TaskCreates a new task in ClickUp from the webhook data. Map the TaskBot values into the task, connect your ClickUp account, and check a test run to see where the task is created.
What you need
- FlowMatticCore
- 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.
- Send one test request from your TaskBot before mapping the ClickUp step. FlowMattic captures the payload so you can see every value the bot sends.
- Turn on Require authentication on incoming requests in the Webhook trigger, and add the key to the TaskBot's request, so only your bot can create tasks.
- If the bot sends rows you don't need, add a Filter after the webhook that continues only when a key value is not empty.
Questions about this workflow
How does a Zerowork.io TaskBot reach this workflow?
You add an HTTP request to your TaskBot that posts to the FlowMattic webhook URL. Whatever data the bot includes in that request is what the ClickUp step can use.
Can one TaskBot run create several ClickUp tasks?
Each request to the webhook creates one task. If the bot sends a list in a single request, you need an Iterator before ClickUp to make a task per item.
Can anyone who finds the webhook URL create ClickUp tasks?
Only while authentication is off. Turn on the trigger's Require authentication on incoming requests setting so requests without your key are refused.
Do I need a Zerowork.io connection in FlowMattic?
No connection is needed for the webhook. You need a ClickUp account to connect, and a TaskBot that can send an HTTP request.
More Project Management workflows
Other ready-to-import templates from the same category.
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





