Repository navigation
docs(recipes): Add recipes for Make, n8n, Square and any app with an API key (#35) - #36
Conversation
|
@deanzaka this PR adds recipes only (6 Markdown files, 258 added lines, no code). Please follow each recipe once with the QA table below. Impact
User path, before and afterQA
Not verified
|
There was a problem hiding this comment.
🟡 Changes recommended
The walkthroughs need corrections to environment selection, duplicate-delivery guidance, and dynamic JSON serialization before readers can reliably follow them.
4 open issues
What changed in this PR
Adds documentation-only recipes for connecting Taskade to Make, n8n, Square, and other API-enabled apps while official integrations are unavailable or awaiting approval.
Changes:
- Adds four walkthroughs using Taskade’s webhook trigger, HTTP step, and Public Action API v2.
- Provides shared setup and credential-handling guidance.
- Links the recipes from the root README without changing integration code, dependencies, or CI.
| File | Description |
|---|---|
recipes/square.md |
Payment webhook and customer-creation walkthrough. |
recipes/README.md |
Recipe index, prerequisites, and credential guidance. |
recipes/n8n.md |
HTTP Request and Webhook node walkthrough. |
recipes/make.md |
HTTP module and Custom webhook walkthrough. |
recipes/any-app-with-an-api-key.md |
Generic API authentication and webhook verification guidance. |
README.md |
Adds a link to the recipes index. |
Review effort: Balanced
| 2. Open the Taskade project for the new tasks. Copy the project ID from the address bar, after `/d/`. | ||
| 3. In Make, add the **HTTP** app's **Make a request** module. Set the method to `POST` and the URL to `https://www.taskade.com/api/v2/createTask`. | ||
| 4. Add the header `Authorization` with the value `Bearer tskdp_YOUR_TOKEN`. Add the header `Content-Type` with the value `application/json`. | ||
| 5. Set the body to raw JSON and paste the body below. Map your Make values into `content`. |
There was a problem hiding this comment.
Fixed in 13eadff. Steps 5 and 6 now build the body with the JSON app Create JSON module and map its JSON string output into the HTTP request content, with a warning that raw JSON text does not escape a mapped value.
| Request body for step 4: | ||
|
|
||
| ```json | ||
| { | ||
| "projectId": "YOUR_PROJECT_ID", | ||
| "tasks": [ | ||
| { "contentType": "text/markdown", "content": "{{ $json.title }}", "placement": "beforeend" } | ||
| ] | ||
| } | ||
| ``` |
There was a problem hiding this comment.
Fixed in 13eadff. Step 4 now sets the JSON field to Expression, and the body is one expression that returns the whole object with content: $json.title, so n8n serializes the title. A note warns against {{ $json.title }} inside quoted JSON.
| 4. In the Square Developer Console, open your application, then **Webhooks**, then **Subscriptions**. Add a subscription with the Taskade URL and the `payment.updated` event. | ||
| 5. Send a test event from Square. Make sure that a run shows in the automation history and that a task shows in your project. | ||
| 6. To write to Square, add **Send HTTP Request** to a Taskade automation. Open **Authentication**, pick **Bearer Token**, and paste your Square access token. | ||
| 7. Set **Method** `POST`, **URL** `https://connect.squareup.com/v2/customers`, a `Square-Version` header, and **Request Body Type** **JSON** with the body below. |
There was a problem hiding this comment.
Fixed in 13eadff. Steps 6 and 7 now use the Sandbox token and https://connect.squareupsandbox.com/v2/customers, and a new note says to change both the token and the host to go live.
|
|
||
| - Square signs each event with its own header, and Taskade does not read that header. Thus the Taskade URL is the only key. Keep it private, and do not paste it into a page or a chat. | ||
| - Put the Square token only in the **Authentication** panel, never in **Headers**. Taskade saves headers as plain text in the automation. | ||
| - A Square payment sends `payment.updated` more than once as its status changes. The **Only continue if...** step keeps one task for each completed payment. |
There was a problem hiding this comment.
Fixed in 13eadff. The one-task-per-payment claim is gone. The note now says that the filter skips incomplete payments but does not stop duplicates (retries, later updates such as a refund), and step 2 and 3 put the payment ID in the task text so that a duplicate is easy to find.
Build the Make body with Create JSON and the n8n body as one expression object, so a quote in a mapped value does not break the request. Point the Square walkthrough at the Sandbox host, say how to go live, and replace the one-task-per-payment claim with a duplicate warning.
Keep the README of master. Add the Recipes section after the table of integrations, because master has no Status section.
…the repository does not prove - make.md: The Make app source is in packages/make-app-taskade. Make does not list the app yet. - n8n.md: The node is on npm. Self-hosted n8n installs it as a community node. The trigger checks X-Taskade-Signature-V2. - recipes/README.md: The index rows match the new status of Make and n8n. - Remove the token limit, the email rule, the storage, size, delay and 404 claims, and the prompt sections.

Closes #35
Adds
recipes/: four short recipes that connect Taskade with Make, n8n, Square and other apps that have an API key, plus an index. They use the When a webhook arrives trigger, the Send HTTP Request step with its Authentication panel, and the Public Action API v2.What changes
recipes/README.mdlistSpacescall, the rule that keeps secrets out of Headersrecipes/make.mdpackages/make-app-taskade(not listed on Make yet, #33). Make HTTP module toPOST /api/v2/createTask, and a Taskade automation that posts new tasks to a Make Custom webhookrecipes/n8n.mdn8n-nodes-taskadeon npm for self-hosted n8n (#17 tracks the n8n review). n8n HTTP Request with Header Auth, and a Taskade automation that posts to an n8n Webhookrecipes/square.mdpayment.updatedevents into When a webhook arrives, and Send HTTP Request with a Bearer Token to the Square SandboxPOST /v2/customersrecipes/any-app-with-an-api-key.mdcurlcall tocreateTaskREADME.mdHow the claims were checked
createTaskbody, its limits (1 to 20 tasks, 2,000 characters), theplacementvalues, thetskdp_token, the/d/<project id>address, the Pro gate on webhooks and theX-Taskade-Signature-V2header match the code and the READMEs in this repository.Not changed
src/,index.js,package.json),packages/n8n-nodes-taskadeandpackages/make-app-taskadeare untouched.