Recipes for Make, n8n, Square and any app with an API key #35

Goal

Publish short recipes that connect Taskade with Make, n8n, Square and any app with an API key today, built only on what ships: the Taskade webhook trigger, the HTTP step with its Authentication panel, and the Public Action API v2.

Why

• Canny: "Make.com (formerly Integromat) integration" has 97 votes, and the Make half of "Zapier & Make" has 36 more. The node for a self-hosted workflow tool (n8n) has 61.
• The official Make app (feat(make): Add the Taskade custom app for Make as code (#33) #34, tracked in Make: official Taskade app for Make, submitted for the Make app review #33) waits on the Make review, and the n8n node (feat(n8n): Make the Taskade node ready for n8n verification (#17) #32, tracked in n8n: publish n8n-nodes-taskade to npm + submit for n8n Cloud verification #17) waits on npm and the n8n review. Users need a path that works before both approvals.
• Square and other long-tail apps have no Taskade integration. Customers ask how to connect them with an access token or an API key.

Scope

• recipes/ with one file per recipe: make.md, n8n.md, square.md, any-app-with-an-api-key.md, plus recipes/README.md as the index.
• The Make and n8n recipes lead with the official app or node in review, then give the API and webhook path that works today.
• Each recipe: who it is for, what it does in one sentence, 4 to 7 numbered steps, and a one-sentence Taskade EVE prompt.
• A short "Recipes" section in the root README that links the index. No other README change.
• No change to the Zapier app or to packages/n8n-nodes-taskade.

Done when

• The recipes are merged.
• Each Taskade step, label and endpoint matches the live app and the v2 spec (https://www.taskade.com/api/documentation/v2).
• Each vendor step (Make, n8n, Square) is marked where it was not checked in the vendor app.