Setting up the Zap
Process Blueprint posts a process to a webhook you own. This is the Zap that turns that into a ClickUp task — creating one the first time, and updating the same task every time after.
1Catch the webhook
Start a Zap with Webhooks by Zapier → Catch Hook. Copy the URL it gives you, paste it into Export → Send to Zapier in Process Blueprint, and save.
Now send a process before you build the rest of the Zap, with Markdown spec and PNG image ticked (both are suggested and on by default). Zapier learns the field names from a real payload, so the fields below will not appear in any dropdown until one has arrived. Then press Test trigger.
| Field | What it is |
|---|---|
process | The blueprint's name |
blueprint_id | Its permanent id. Match on this, not the name |
steps | How many steps it has |
note | Whatever you typed in the dialog |
markdown | The full spec as text, for the task description |
json | The blueprint, re-importable |
svg | The map as text |
png_url | A link to the map, live for five minutes. This is what an attachment step wants |
Every field arrives every time. One you did not tick comes through empty, which Zapier displays as no data — that is what it looks like, not a fault.
2Look for the task already there
Add ClickUp → Find Task. Point it at the Space, Folder and List the processes live in, and
search for blueprint_id.
Tick "Should this step be considered a success when nothing is found?" Without it the Zap stops dead the first time a process is new, which is every process the first time you send it.
blueprint_id rather than process. The id never
changes; the name does, and the first time somebody renames a process a name-matched Zap creates a
second task instead of updating the first.3Split on whether it found one
Add Paths by Zapier with two paths:
- Found — the Find Task step's ID field exists.
- Not found — the same field does not exist.
4aFound: update it
On the Found path, add ClickUp → Update Task. Point it at the ID from step 2 and map:
- Name ←
process - Description ←
markdown
4bNot found: create it
On the Not found path, add ClickUp → Create Task in the same List, with the same mapping,
and put blueprint_id somewhere step 2 will find it next time — a custom field is
tidiest, and the description works if you would rather not add one.
5Attach the map
On either path, add ClickUp → Post Attachment, point it at the task from the step
before, and give it png_url as the file.
Zapier attaches a file from a URL or from a file object, never from base64 — which is why that field is a link rather than the image itself. The link lives for five minutes. That is ample for a Zap, which fires in seconds, and it means the map is not left sitting on a public URL afterwards. Anyone holding the link can fetch it during those five minutes, which is the trade for being able to attach it at all.