From caea8fc7b38d0bd29ad2b5ac49ecc5c1c03b62b0 Mon Sep 17 00:00:00 2001 From: johnxie Date: Thu, 22 Oct 2026 15:56:36 -0700 Subject: [PATCH 1/3] docs(recipes): Add recipes for Make, n8n, Square and any app with an API key (#35) --- README.md | 4 ++ recipes/README.md | 39 +++++++++++++++++++ recipes/any-app-with-an-api-key.md | 62 ++++++++++++++++++++++++++++++ recipes/make.md | 55 ++++++++++++++++++++++++++ recipes/n8n.md | 49 +++++++++++++++++++++++ recipes/square.md | 49 +++++++++++++++++++++++ 6 files changed, 258 insertions(+) create mode 100644 recipes/README.md create mode 100644 recipes/any-app-with-an-api-key.md create mode 100644 recipes/make.md create mode 100644 recipes/n8n.md create mode 100644 recipes/square.md diff --git a/README.md b/README.md index 632f0be..3b5bb46 100644 --- a/README.md +++ b/README.md @@ -15,6 +15,10 @@ Building a Taskade integration for another platform (n8n, Activepieces, Make, Pi | n8n | Source in [`packages/n8n-nodes-taskade`](packages/n8n-nodes-taskade) (package `n8n-nodes-taskade` 0.2.0). Not yet published to npm. | | Activepieces, Make, Pipedream | Planned. No code in this repo yet. | +## Recipes + +Step-by-step recipes connect Taskade with Make, n8n, Square and any app with an API key today. They use the Taskade webhook trigger, the HTTP step and the Public Action API v2. Start at the [recipes index](recipes/README.md). + ## Zapier app capabilities | Type | Keys | Notes | diff --git a/recipes/README.md b/recipes/README.md new file mode 100644 index 0000000..9437bc8 --- /dev/null +++ b/recipes/README.md @@ -0,0 +1,39 @@ +# Recipes + +These recipes connect Taskade with tools that have no official Taskade app yet, or whose app is still in review. Each recipe uses only what ships in Taskade today: + +- The **When a webhook arrives** trigger in a Taskade automation, for events that another tool sends to Taskade. +- The **Send HTTP Request** step with its **Authentication** panel, for calls from Taskade to another tool. +- The [Public Action API v2](https://www.taskade.com/api/documentation/v2) at `https://www.taskade.com/api/v2`, for calls from another tool to Taskade. + +| Recipe | Who it is for | Uses | +|---|---|---| +| [Use Taskade with Make today](make.md) | Make users, until the official Make app passes review | Public API, Send HTTP Request | +| [Use Taskade with n8n today](n8n.md) | n8n users, until the Taskade node is on npm | Public API, Send HTTP Request | +| [Connect Square to Taskade](square.md) | Teams that take payments in Square | Webhook trigger, Send HTTP Request with a Bearer Token | +| [Connect any app with an API key](any-app-with-an-api-key.md) | Teams whose tool is not in the 100+ integrations | Send HTTP Request with Custom auth, webhook trigger, Public API | + +## Before you start + +| You need | Where | +|---|---| +| A personal access token (starts with `tskdp_`) | Taskade **Settings** > **API** > **Personal access tokens** > **Create token**. A verified email is required, and you can keep up to 5 active tokens | +| A project ID | Open the project. The ID is in the address bar after `/d/` | +| The Pro plan or higher | Only for the **When a webhook arrives** trigger and **Outgoing webhooks** | + +Every Public API v2 operation is a `POST` with a JSON body and the header `Authorization: Bearer tskdp_YOUR_TOKEN`. A first call that lists the workspaces your token can reach: + +```bash +curl https://www.taskade.com/api/v2/listSpaces \ + -H "Authorization: Bearer tskdp_YOUR_TOKEN" \ + -H "Content-Type: application/json" \ + -d '{}' +``` + +## Keep secrets out of headers + +Put an API key or a token only in the **Authentication** panel of the **Send HTTP Request** step. Taskade saves that panel as an encrypted credential and sends it only when the step runs. The **Headers** and **Query params** fields are saved as plain text in the automation, so everyone who can open the automation can read them. + +## Taskade EVE can build these + +Each recipe ends with a one-sentence prompt. Paste it into the Taskade EVE chat, and Taskade EVE builds the automation. If a step needs a key, Taskade EVE asks you to paste it into the **Authentication** panel of that step. diff --git a/recipes/any-app-with-an-api-key.md b/recipes/any-app-with-an-api-key.md new file mode 100644 index 0000000..a175e70 --- /dev/null +++ b/recipes/any-app-with-an-api-key.md @@ -0,0 +1,62 @@ +# Connect any app with an API key + +Taskade connects to 100+ integrations. If your app is not one of them, it can still join an automation when it has an API key or sends webhooks. + +**Who it is for:** Teams whose tool is not in the Taskade integrations list, but who can copy an API key from it. + +**What it does:** A Taskade automation calls the app with your saved API key, and the app sends its events to a Taskade automation. + +**Before you start:** You need an API key and the API docs of the app. The webhook part needs the Pro plan or higher. + +## Steps + +1. In the app, create an API key. In its API docs, find the header for the key, for example `Authorization: Bearer ` or `X-API-Key: `. +2. In a Taskade automation, add **Send HTTP Request** from the **Data & Text Tools** tab. +3. Open **Authentication** and pick the **Auth Type** that the app expects: **Bearer Token**, **API Key** with a **Header Name**, or **Basic Auth**. Paste the key there. +4. Set **Method**, **URL** and **Request Body Type** **JSON**. Set **Response Body Type** to **JSON**, so the next steps can use the answer. +5. To hear from the app, create an automation with **When a webhook arrives**. Paste its **Webhook URL** into the webhook settings of the app. +6. Set **Verify requests** to a mode that the app supports: **Bearer token**, **Stripe signature** or **HMAC-SHA256 signature**. Use **None** only when the app supports no check. +7. If the app can run a script but cannot send webhooks, call the Taskade API from the script with a personal access token, as shown below. + +```bash +curl https://www.taskade.com/api/v2/createTask \ + -H "Authorization: Bearer tskdp_YOUR_TOKEN" \ + -H "Content-Type: application/json" \ + -d '{"projectId":"YOUR_PROJECT_ID","tasks":[{"contentType":"text/markdown","content":"Hello from my app","placement":"beforeend"}]}' +``` + +## Auth Type reference + +| Auth Type | Taskade sends | +|---|---| +| **Bearer Token** | `Authorization: Bearer ` | +| **API Key** | `
: ` | +| **Basic Auth** | `Authorization: Basic base64(username:password)` | + +## Verify requests reference + +| Mode | What the sender must do | +|---|---| +| **Bearer token** | Send `Authorization: Bearer `. Taskade makes the token when you turn on the automation | +| **Stripe signature** | Send the `Stripe-Signature` header of a Stripe webhook endpoint. Paste its signing secret in Taskade | +| **HMAC-SHA256 signature** | Send the hex HMAC-SHA256 of `.` in `X-Taskade-Signature-V2` and the Unix time in seconds in `X-Taskade-Timestamp`. Taskade rejects a request more than 5 minutes old | +| **None** | Nothing. Anyone with the URL can start the automation | + +## Check the result + +You are done when the **Send HTTP Request** step shows the answer of the app in its run, and an event from the app starts your webhook automation. + +## Notes + +- Never put a key in **Headers** or **Query params**. Taskade saves those fields as plain text in the automation, and everyone who can open the automation can read them. +- The webhook takes JSON, `multipart/form-data` and `application/x-www-form-urlencoded` bodies up to about 1.5 MB. If the automation is off, the URL answers 404. +- The **Send HTTP Request** step does not reach `localhost` or private network addresses. + +## Taskade EVE can build this for you + +> Build an automation that sends each new task in my Requests project to the Acme API with my saved API key. + +## Checked + +- Taskade steps, labels, the Auth Type and Verify requests options, and the `createTask` call: checked against the Taskade app and the [v2 spec](https://www.taskade.com/api/documentation/v2) on 2026-10-22. +- The behavior of a specific third-party app is not covered. Read its API docs for the URL, the header and the webhook settings. diff --git a/recipes/make.md b/recipes/make.md new file mode 100644 index 0000000..e9886a0 --- /dev/null +++ b/recipes/make.md @@ -0,0 +1,55 @@ +# Use Taskade with Make today + +The official Taskade app for Make is in review. [PR #34](https://github.com/taskade/integrations/pull/34) holds the app, and [issue #33](https://github.com/taskade/integrations/issues/33) tracks the Make review. Until Make approves it, connect Make and Taskade with the Make HTTP module and a Taskade automation. + +**Who it is for:** Make users who want a scenario to add tasks in Taskade, or to start when a task lands in Taskade. + +**What it does:** A Make scenario adds tasks to a Taskade project through the Taskade API, and a Taskade automation sends each new task to a Make scenario. + +**Before you start:** You need a Taskade account with a verified email and a Make account. The Taskade API takes a personal access token. + +## Steps + +1. In Taskade, open **Settings**, then **API**, and click **Create token** under **Personal access tokens**. Copy the token. It starts with `tskdp_`. +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`. +6. Run the module once. Make sure that Taskade answers `{"ok":true,...}` and that the task shows in your project. +7. To start a scenario from Taskade, copy the URL of a Make **Custom webhook** module. In a Taskade automation, add **When a task is added**, then **Send HTTP Request** with **Method** `POST`, that **URL** and **Request Body Type** **JSON**. + +Request body for step 5: + +```json +{ + "projectId": "YOUR_PROJECT_ID", + "tasks": [ + { "contentType": "text/markdown", "content": "New lead: {{name}}", "placement": "beforeend" } + ] +} +``` + +Answer from Taskade: + +```json +{ "ok": true, "items": [{ "id": "NEW_TASK_ID" }] } +``` + +## Check the result + +You are done when a Make run adds a task to your project, and a new Taskade task starts your Make scenario. The **When a task is added** trigger waits about 5 minutes after the last edit of a task. + +## Notes + +- Anyone who can edit the scenario can read the token in the header. Give the token its own name, such as `make`, and revoke it in **Settings** > **API** when you stop. +- `createTask` takes 1 to 20 tasks per call, and each `content` holds up to 2,000 characters. `placement` is `beforeend` (last) or `afterbegin` (first). +- For Taskade events such as a task assigned or a comment added, paste the Make URL into **Settings** > **API** > **Outgoing webhooks** (Pro and above). No automation is needed for those events. + +## Taskade EVE can build this for you + +> Build an automation that sends every new task in my Leads project to my Make webhook URL. + +## Checked + +- Taskade steps, labels and the `createTask` body: checked against the Taskade app and the [v2 spec](https://www.taskade.com/api/documentation/v2) on 2026-10-22. +- Make labels (**HTTP**, **Make a request**, **Custom webhook**): taken from Make's public docs. Not checked in a Make account. diff --git a/recipes/n8n.md b/recipes/n8n.md new file mode 100644 index 0000000..38b81a8 --- /dev/null +++ b/recipes/n8n.md @@ -0,0 +1,49 @@ +# Use Taskade with n8n today + +The Taskade node for n8n is ready for n8n verification in [PR #32](https://github.com/taskade/integrations/pull/32), and [issue #17](https://github.com/taskade/integrations/issues/17) tracks the npm publish and the n8n review. The node is not on npm yet. Until it is, connect n8n and Taskade with the built-in n8n nodes and a Taskade automation. + +**Who it is for:** n8n users, on n8n Cloud or self-hosted, who want a workflow to read or write Taskade. + +**What it does:** An n8n workflow adds tasks to a Taskade project through the Taskade API, and a Taskade automation starts an n8n workflow with each new task. + +**Before you start:** You need a Taskade account with a verified email. Taskade must reach your n8n over the public internet. The Taskade **Send HTTP Request** step blocks `localhost` and private network addresses. + +## Steps + +1. In Taskade, open **Settings**, then **API**, and click **Create token**. Copy the token. It starts with `tskdp_`. +2. In n8n, add an **HTTP Request** node. Set **Method** to `POST` and **URL** to `https://www.taskade.com/api/v2/createTask`. +3. Set **Authentication** to **Generic Credential Type**, then **Header Auth**. Use the name `Authorization` and the value `Bearer tskdp_YOUR_TOKEN`. +4. Turn on **Send Body**, pick **JSON**, and paste the body below with your project ID. The project ID is in the Taskade address bar, after `/d/`. +5. Click **Execute step**. Make sure that Taskade answers `{"ok":true,...}` and that the task shows in your project. +6. To start n8n from Taskade, add an n8n **Webhook** node with the method `POST`, and copy its **Production URL**. +7. In a Taskade automation, add **When a task is added**, then **Send HTTP Request** with **Method** `POST`, the n8n URL and **Request Body Type** **JSON**. Activate the n8n workflow. + +Request body for step 4: + +```json +{ + "projectId": "YOUR_PROJECT_ID", + "tasks": [ + { "contentType": "text/markdown", "content": "{{ $json.title }}", "placement": "beforeend" } + ] +} +``` + +## Check the result + +You are done when an n8n run adds a task to your project, and a new Taskade task shows as an execution in n8n. + +## Notes + +- The **Header Auth** credential keeps the token out of the workflow JSON, so an exported workflow does not carry it. +- For Taskade events such as a task assigned, paste the n8n URL into **Settings** > **API** > **Outgoing webhooks** (Pro and above). Each delivery carries an `X-Taskade-Signature` header that you can check. +- When the Taskade node is on npm, it replaces steps 2 to 5 with a **Taskade** node and a **Taskade Trigger** node. + +## Taskade EVE can build this for you + +> Build an automation that sends every new task in my Requests project to my n8n webhook URL. + +## Checked + +- Taskade steps, labels and the `createTask` body: checked against the Taskade app and the [v2 spec](https://www.taskade.com/api/documentation/v2) on 2026-10-22. +- n8n labels (**HTTP Request**, **Generic Credential Type**, **Header Auth**, **Send Body**, **Execute step**, **Webhook**, **Production URL**): taken from n8n's public docs. Not checked in an n8n instance. diff --git a/recipes/square.md b/recipes/square.md new file mode 100644 index 0000000..04bc925 --- /dev/null +++ b/recipes/square.md @@ -0,0 +1,49 @@ +# Connect Square to Taskade + +Square has no Taskade integration yet. A Taskade webhook and the **Send HTTP Request** step with your Square access token cover the common jobs today. + +**Who it is for:** Shops, studios and service teams that take payments in Square and track orders or clients in Taskade. + +**What it does:** Each completed Square payment adds a task to a Taskade project, and a Taskade automation can create a customer in Square. + +**Before you start:** The **When a webhook arrives** trigger needs the Pro plan or higher. You need a Square developer application with an access token. Test in the Square Sandbox first. + +## Steps + +1. In Taskade, create an automation with the trigger **When a webhook arrives**. Copy the **Webhook URL**, and set **Verify requests** to **None**. +2. In **Parameters**, add the Square fields that the next steps use: `data.object.payment.status` and `data.object.payment.amount_money.amount`. +3. Add an **Only continue if...** step that passes when the payment status is `COMPLETED`. Then add an **Add a task** step with the amount in the task text. Turn on the automation. +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. + +Request body for step 7 (map the values from your task): + +```json +{ + "given_name": "Jane", + "email_address": "jane@example.com" +} +``` + +## Check the result + +You are done when a Square test payment adds a task, and the **Send HTTP Request** step answers with a new customer `id`. + +## Notes + +- 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. +- If the automation is off, the webhook URL answers 404, and Square retries the event. + +## Taskade EVE can build this for you + +> Build an automation that adds a task to my Orders project each time Square sends a completed payment to my webhook. + +## Checked + +- Taskade steps, labels and webhook behavior: checked against the Taskade app on 2026-10-22. +- Square facts (Developer Console labels, the `payment.updated` event and its payload paths, `/v2/customers` and its fields, the `Square-Version` header, the Square signature header, retries): taken from Square's public docs. Not checked in a Square account. +- A nested field such as `data.object.payment.status` in **Parameters**: the field builder supports nested objects, but this recipe was not run end to end. From 13eadff20322584eeced9dfb3add787fa0f27cc8 Mon Sep 17 00:00:00 2001 From: johnxie Date: Thu, 22 Oct 2026 17:53:28 -0700 Subject: [PATCH 2/3] docs(recipes): Escape mapped values and use the Square Sandbox host 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. --- recipes/make.md | 9 +++++---- recipes/n8n.md | 14 ++++++++------ recipes/square.md | 15 ++++++++------- 3 files changed, 21 insertions(+), 17 deletions(-) diff --git a/recipes/make.md b/recipes/make.md index e9886a0..4653849 100644 --- a/recipes/make.md +++ b/recipes/make.md @@ -14,9 +14,10 @@ The official Taskade app for Make is in review. [PR #34](https://github.com/task 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`. -6. Run the module once. Make sure that Taskade answers `{"ok":true,...}` and that the task shows in your project. -7. To start a scenario from Taskade, copy the URL of a Make **Custom webhook** module. In a Taskade automation, add **When a task is added**, then **Send HTTP Request** with **Method** `POST`, that **URL** and **Request Body Type** **JSON**. +5. Before the HTTP module, add the **JSON** app's **Create JSON** module. Give it the structure of the body below, and map your Make values into `content`. +6. In the HTTP module, set the body to raw JSON and map the **JSON string** output of **Create JSON** as the request content. Do not type mapped values into raw JSON text. Raw text does not escape a quote or a line break in a value, so a name such as `Jane "JJ" Doe` breaks the request. +7. Run the scenario once. Make sure that Taskade answers `{"ok":true,...}` and that the task shows in your project. +8. To start a scenario from Taskade, copy the URL of a Make **Custom webhook** module. In a Taskade automation, add **When a task is added**, then **Send HTTP Request** with **Method** `POST`, that **URL** and **Request Body Type** **JSON**. Request body for step 5: @@ -52,4 +53,4 @@ You are done when a Make run adds a task to your project, and a new Taskade task ## Checked - Taskade steps, labels and the `createTask` body: checked against the Taskade app and the [v2 spec](https://www.taskade.com/api/documentation/v2) on 2026-10-22. -- Make labels (**HTTP**, **Make a request**, **Custom webhook**): taken from Make's public docs. Not checked in a Make account. +- Make labels (**HTTP**, **Make a request**, **Custom webhook**, **JSON**, **Create JSON**, **JSON string**): taken from Make's public docs. Not checked in a Make account. diff --git a/recipes/n8n.md b/recipes/n8n.md index 38b81a8..81d5a6a 100644 --- a/recipes/n8n.md +++ b/recipes/n8n.md @@ -13,22 +13,24 @@ The Taskade node for n8n is ready for n8n verification in [PR #32](https://githu 1. In Taskade, open **Settings**, then **API**, and click **Create token**. Copy the token. It starts with `tskdp_`. 2. In n8n, add an **HTTP Request** node. Set **Method** to `POST` and **URL** to `https://www.taskade.com/api/v2/createTask`. 3. Set **Authentication** to **Generic Credential Type**, then **Header Auth**. Use the name `Authorization` and the value `Bearer tskdp_YOUR_TOKEN`. -4. Turn on **Send Body**, pick **JSON**, and paste the body below with your project ID. The project ID is in the Taskade address bar, after `/d/`. +4. Turn on **Send Body** and pick **JSON**. Set the JSON field to **Expression**, and paste the expression below with your project ID. The project ID is in the Taskade address bar, after `/d/`. 5. Click **Execute step**. Make sure that Taskade answers `{"ok":true,...}` and that the task shows in your project. 6. To start n8n from Taskade, add an n8n **Webhook** node with the method `POST`, and copy its **Production URL**. 7. In a Taskade automation, add **When a task is added**, then **Send HTTP Request** with **Method** `POST`, the n8n URL and **Request Body Type** **JSON**. Activate the n8n workflow. Request body for step 4: -```json -{ +```js +{{ { "projectId": "YOUR_PROJECT_ID", "tasks": [ - { "contentType": "text/markdown", "content": "{{ $json.title }}", "placement": "beforeend" } + { "contentType": "text/markdown", "content": $json.title, "placement": "beforeend" } ] -} +} }} ``` +The expression returns the whole body as an object, and n8n serializes it. Do not put `{{ $json.title }}` inside quoted JSON text. n8n does not escape the value there, so a title such as `Call "Acme"` makes the body invalid. + ## Check the result You are done when an n8n run adds a task to your project, and a new Taskade task shows as an execution in n8n. @@ -46,4 +48,4 @@ You are done when an n8n run adds a task to your project, and a new Taskade task ## Checked - Taskade steps, labels and the `createTask` body: checked against the Taskade app and the [v2 spec](https://www.taskade.com/api/documentation/v2) on 2026-10-22. -- n8n labels (**HTTP Request**, **Generic Credential Type**, **Header Auth**, **Send Body**, **Execute step**, **Webhook**, **Production URL**): taken from n8n's public docs. Not checked in an n8n instance. +- n8n labels (**HTTP Request**, **Generic Credential Type**, **Header Auth**, **Send Body**, **Expression**, **Execute step**, **Webhook**, **Production URL**): taken from n8n's public docs. Not checked in an n8n instance. diff --git a/recipes/square.md b/recipes/square.md index 04bc925..b1aa60a 100644 --- a/recipes/square.md +++ b/recipes/square.md @@ -6,17 +6,17 @@ Square has no Taskade integration yet. A Taskade webhook and the **Send HTTP Req **What it does:** Each completed Square payment adds a task to a Taskade project, and a Taskade automation can create a customer in Square. -**Before you start:** The **When a webhook arrives** trigger needs the Pro plan or higher. You need a Square developer application with an access token. Test in the Square Sandbox first. +**Before you start:** The **When a webhook arrives** trigger needs the Pro plan or higher. You need a Square developer application. Test with its Sandbox access token and the Sandbox host `connect.squareupsandbox.com` first. ## Steps 1. In Taskade, create an automation with the trigger **When a webhook arrives**. Copy the **Webhook URL**, and set **Verify requests** to **None**. -2. In **Parameters**, add the Square fields that the next steps use: `data.object.payment.status` and `data.object.payment.amount_money.amount`. -3. Add an **Only continue if...** step that passes when the payment status is `COMPLETED`. Then add an **Add a task** step with the amount in the task text. Turn on the automation. +2. In **Parameters**, add the Square fields that the next steps use: `data.object.payment.id`, `data.object.payment.status` and `data.object.payment.amount_money.amount`. +3. Add an **Only continue if...** step that passes when the payment status is `COMPLETED`. Then add an **Add a task** step with the payment ID and the amount in the task text. Turn on the automation. 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. +6. To write to Square, add **Send HTTP Request** to a Taskade automation. Open **Authentication**, pick **Bearer Token**, and paste your Square Sandbox access token. +7. Set **Method** `POST`, **URL** `https://connect.squareupsandbox.com/v2/customers`, a `Square-Version` header, and **Request Body Type** **JSON** with the body below. Request body for step 7 (map the values from your task): @@ -35,7 +35,8 @@ You are done when a Square test payment adds a task, and the **Send HTTP Request - 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. +- To go live, change both the token and the host. Use your production access token and `https://connect.squareup.com/v2/customers`. A Sandbox token fails on the production host, and a production token creates real customers. +- The **Only continue if...** step skips a payment that is not complete. It does not stop a duplicate task. Square retries an event that it did not see delivered, and a completed payment can send `payment.updated` again, for example after a refund. Thus one payment can add more than one task. The payment ID in the task text helps you find a duplicate. - If the automation is off, the webhook URL answers 404, and Square retries the event. ## Taskade EVE can build this for you @@ -45,5 +46,5 @@ You are done when a Square test payment adds a task, and the **Send HTTP Request ## Checked - Taskade steps, labels and webhook behavior: checked against the Taskade app on 2026-10-22. -- Square facts (Developer Console labels, the `payment.updated` event and its payload paths, `/v2/customers` and its fields, the `Square-Version` header, the Square signature header, retries): taken from Square's public docs. Not checked in a Square account. +- Square facts (Developer Console labels, the `payment.updated` event and its payload paths, the Sandbox and production hosts, `/v2/customers` and its fields, the `Square-Version` header, the Square signature header, retries): taken from Square's public docs. Not checked in a Square account. - A nested field such as `data.object.payment.status` in **Parameters**: the field builder supports nested objects, but this recipe was not run end to end. From db5c9b6138b7d9bfb60615b53d3e3a99078ff5bd Mon Sep 17 00:00:00 2001 From: John Xie Date: Wed, 18 Nov 2026 21:38:40 -0800 Subject: [PATCH 3/3] docs(recipes): Update the Make and n8n status and remove claims that 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. --- recipes/README.md | 20 +++++++--------- recipes/any-app-with-an-api-key.md | 37 +++++++----------------------- recipes/make.md | 17 ++++++-------- recipes/n8n.md | 19 +++++++-------- recipes/square.md | 17 +++++--------- 5 files changed, 37 insertions(+), 73 deletions(-) diff --git a/recipes/README.md b/recipes/README.md index 9437bc8..8b744e0 100644 --- a/recipes/README.md +++ b/recipes/README.md @@ -1,6 +1,6 @@ # Recipes -These recipes connect Taskade with tools that have no official Taskade app yet, or whose app is still in review. Each recipe uses only what ships in Taskade today: +These recipes connect Taskade with a tool through a Taskade automation and the Public Action API v2. Use them when the tool has no Taskade app, or when you cannot install the Taskade app there yet. Each recipe uses these parts of Taskade: - The **When a webhook arrives** trigger in a Taskade automation, for events that another tool sends to Taskade. - The **Send HTTP Request** step with its **Authentication** panel, for calls from Taskade to another tool. @@ -8,20 +8,20 @@ These recipes connect Taskade with tools that have no official Taskade app yet, | Recipe | Who it is for | Uses | |---|---|---| -| [Use Taskade with Make today](make.md) | Make users, until the official Make app passes review | Public API, Send HTTP Request | -| [Use Taskade with n8n today](n8n.md) | n8n users, until the Taskade node is on npm | Public API, Send HTTP Request | +| [Use Taskade with Make today](make.md) | Make users, until the Taskade app is listed on Make | Public API, Send HTTP Request | +| [Use Taskade with n8n today](n8n.md) | n8n users who cannot install the Taskade community node, for example on n8n Cloud before n8n verifies the node | Public API, Send HTTP Request | | [Connect Square to Taskade](square.md) | Teams that take payments in Square | Webhook trigger, Send HTTP Request with a Bearer Token | -| [Connect any app with an API key](any-app-with-an-api-key.md) | Teams whose tool is not in the 100+ integrations | Send HTTP Request with Custom auth, webhook trigger, Public API | +| [Connect any app with an API key](any-app-with-an-api-key.md) | Teams whose tool has no Taskade integration | Send HTTP Request with an API key, webhook trigger, Public API | ## Before you start | You need | Where | |---|---| -| A personal access token (starts with `tskdp_`) | Taskade **Settings** > **API** > **Personal access tokens** > **Create token**. A verified email is required, and you can keep up to 5 active tokens | +| A personal access token (starts with `tskdp_`) | Taskade [**Settings** > **API**](https://www.taskade.com/settings/api). Create a personal access token there | | A project ID | Open the project. The ID is in the address bar after `/d/` | -| The Pro plan or higher | Only for the **When a webhook arrives** trigger and **Outgoing webhooks** | +| The Pro plan or higher | Only for the **When a webhook arrives** trigger and for Taskade webhook events | -Every Public API v2 operation is a `POST` with a JSON body and the header `Authorization: Bearer tskdp_YOUR_TOKEN`. A first call that lists the workspaces your token can reach: +Each recipe calls the Public API v2 with a `POST`, a JSON body and the header `Authorization: Bearer tskdp_YOUR_TOKEN`. A first call that lists the workspaces your token can reach: ```bash curl https://www.taskade.com/api/v2/listSpaces \ @@ -32,8 +32,4 @@ curl https://www.taskade.com/api/v2/listSpaces \ ## Keep secrets out of headers -Put an API key or a token only in the **Authentication** panel of the **Send HTTP Request** step. Taskade saves that panel as an encrypted credential and sends it only when the step runs. The **Headers** and **Query params** fields are saved as plain text in the automation, so everyone who can open the automation can read them. - -## Taskade EVE can build these - -Each recipe ends with a one-sentence prompt. Paste it into the Taskade EVE chat, and Taskade EVE builds the automation. If a step needs a key, Taskade EVE asks you to paste it into the **Authentication** panel of that step. +Put an API key or a token only in the **Authentication** panel of the **Send HTTP Request** step. Do not type a key into the **Headers** or **Query params** fields. diff --git a/recipes/any-app-with-an-api-key.md b/recipes/any-app-with-an-api-key.md index a175e70..fa02447 100644 --- a/recipes/any-app-with-an-api-key.md +++ b/recipes/any-app-with-an-api-key.md @@ -1,8 +1,8 @@ # Connect any app with an API key -Taskade connects to 100+ integrations. If your app is not one of them, it can still join an automation when it has an API key or sends webhooks. +If your app has no Taskade integration, it can still join a Taskade automation when it has an API key or sends webhooks. -**Who it is for:** Teams whose tool is not in the Taskade integrations list, but who can copy an API key from it. +**Who it is for:** Teams whose tool has no Taskade integration, but who can copy an API key from it. **What it does:** A Taskade automation calls the app with your saved API key, and the app sends its events to a Taskade automation. @@ -11,11 +11,11 @@ Taskade connects to 100+ integrations. If your app is not one of them, it can st ## Steps 1. In the app, create an API key. In its API docs, find the header for the key, for example `Authorization: Bearer ` or `X-API-Key: `. -2. In a Taskade automation, add **Send HTTP Request** from the **Data & Text Tools** tab. +2. In a Taskade automation, add a **Send HTTP Request** step. 3. Open **Authentication** and pick the **Auth Type** that the app expects: **Bearer Token**, **API Key** with a **Header Name**, or **Basic Auth**. Paste the key there. 4. Set **Method**, **URL** and **Request Body Type** **JSON**. Set **Response Body Type** to **JSON**, so the next steps can use the answer. 5. To hear from the app, create an automation with **When a webhook arrives**. Paste its **Webhook URL** into the webhook settings of the app. -6. Set **Verify requests** to a mode that the app supports: **Bearer token**, **Stripe signature** or **HMAC-SHA256 signature**. Use **None** only when the app supports no check. +6. Set **Verify requests** to a mode that the app supports, for example **Bearer token** or **HMAC-SHA256 signature**. Use **None** only when the app supports no check. 7. If the app can run a script but cannot send webhooks, call the Taskade API from the script with a personal access token, as shown below. ```bash @@ -25,38 +25,17 @@ curl https://www.taskade.com/api/v2/createTask \ -d '{"projectId":"YOUR_PROJECT_ID","tasks":[{"contentType":"text/markdown","content":"Hello from my app","placement":"beforeend"}]}' ``` -## Auth Type reference - -| Auth Type | Taskade sends | -|---|---| -| **Bearer Token** | `Authorization: Bearer ` | -| **API Key** | `
: ` | -| **Basic Auth** | `Authorization: Basic base64(username:password)` | - -## Verify requests reference - -| Mode | What the sender must do | -|---|---| -| **Bearer token** | Send `Authorization: Bearer `. Taskade makes the token when you turn on the automation | -| **Stripe signature** | Send the `Stripe-Signature` header of a Stripe webhook endpoint. Paste its signing secret in Taskade | -| **HMAC-SHA256 signature** | Send the hex HMAC-SHA256 of `.` in `X-Taskade-Signature-V2` and the Unix time in seconds in `X-Taskade-Timestamp`. Taskade rejects a request more than 5 minutes old | -| **None** | Nothing. Anyone with the URL can start the automation | - ## Check the result You are done when the **Send HTTP Request** step shows the answer of the app in its run, and an event from the app starts your webhook automation. ## Notes -- Never put a key in **Headers** or **Query params**. Taskade saves those fields as plain text in the automation, and everyone who can open the automation can read them. -- The webhook takes JSON, `multipart/form-data` and `application/x-www-form-urlencoded` bodies up to about 1.5 MB. If the automation is off, the URL answers 404. -- The **Send HTTP Request** step does not reach `localhost` or private network addresses. - -## Taskade EVE can build this for you - -> Build an automation that sends each new task in my Requests project to the Acme API with my saved API key. +- Never type a key into **Headers** or **Query params**. Put it only in the **Authentication** panel. +- With **Verify requests** set to **None**, anyone with the webhook URL can start the automation. Keep the URL private. ## Checked -- Taskade steps, labels, the Auth Type and Verify requests options, and the `createTask` call: checked against the Taskade app and the [v2 spec](https://www.taskade.com/api/documentation/v2) on 2026-10-22. +- Taskade steps and labels: taken from the Taskade app on 2026-10-22. +- The `createTask` call: the same as in the Zapier app and the n8n node in this repository. - The behavior of a specific third-party app is not covered. Read its API docs for the URL, the header and the webhook settings. diff --git a/recipes/make.md b/recipes/make.md index 4653849..65dcb6b 100644 --- a/recipes/make.md +++ b/recipes/make.md @@ -1,16 +1,16 @@ # Use Taskade with Make today -The official Taskade app for Make is in review. [PR #34](https://github.com/taskade/integrations/pull/34) holds the app, and [issue #33](https://github.com/taskade/integrations/issues/33) tracks the Make review. Until Make approves it, connect Make and Taskade with the Make HTTP module and a Taskade automation. +The Taskade app for Make is not listed on Make yet. Its source is in [`packages/make-app-taskade`](../packages/make-app-taskade), and [issue #33](https://github.com/taskade/integrations/issues/33) tracks the submission. Until Make lists it, connect Make and Taskade with the Make HTTP module and a Taskade automation. **Who it is for:** Make users who want a scenario to add tasks in Taskade, or to start when a task lands in Taskade. **What it does:** A Make scenario adds tasks to a Taskade project through the Taskade API, and a Taskade automation sends each new task to a Make scenario. -**Before you start:** You need a Taskade account with a verified email and a Make account. The Taskade API takes a personal access token. +**Before you start:** You need a Taskade account and a Make account. The Taskade API takes a personal access token. ## Steps -1. In Taskade, open **Settings**, then **API**, and click **Create token** under **Personal access tokens**. Copy the token. It starts with `tskdp_`. +1. In Taskade, open **Settings**, then **API**, and create a personal access token. Copy the token. It starts with `tskdp_`. 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`. @@ -38,19 +38,16 @@ Answer from Taskade: ## Check the result -You are done when a Make run adds a task to your project, and a new Taskade task starts your Make scenario. The **When a task is added** trigger waits about 5 minutes after the last edit of a task. +You are done when a Make run adds a task to your project, and a new Taskade task starts your Make scenario. ## Notes - Anyone who can edit the scenario can read the token in the header. Give the token its own name, such as `make`, and revoke it in **Settings** > **API** when you stop. - `createTask` takes 1 to 20 tasks per call, and each `content` holds up to 2,000 characters. `placement` is `beforeend` (last) or `afterbegin` (first). -- For Taskade events such as a task assigned or a comment added, paste the Make URL into **Settings** > **API** > **Outgoing webhooks** (Pro and above). No automation is needed for those events. - -## Taskade EVE can build this for you - -> Build an automation that sends every new task in my Leads project to my Make webhook URL. +- Taskade webhook events, such as a task assigned or a comment added, need the Pro plan or higher. The [webhooks guide](https://www.taskade.com/docs/guides/webhooks) shows how to send them to a URL. ## Checked -- Taskade steps, labels and the `createTask` body: checked against the Taskade app and the [v2 spec](https://www.taskade.com/api/documentation/v2) on 2026-10-22. +- Taskade steps and labels: taken from the Taskade app on 2026-10-22. +- The `createTask` call, its body, its limits and its answer: the same as in the Zapier app and the n8n node in this repository. - Make labels (**HTTP**, **Make a request**, **Custom webhook**, **JSON**, **Create JSON**, **JSON string**): taken from Make's public docs. Not checked in a Make account. diff --git a/recipes/n8n.md b/recipes/n8n.md index 81d5a6a..afdf91c 100644 --- a/recipes/n8n.md +++ b/recipes/n8n.md @@ -1,16 +1,16 @@ # Use Taskade with n8n today -The Taskade node for n8n is ready for n8n verification in [PR #32](https://github.com/taskade/integrations/pull/32), and [issue #17](https://github.com/taskade/integrations/issues/17) tracks the npm publish and the n8n review. The node is not on npm yet. Until it is, connect n8n and Taskade with the built-in n8n nodes and a Taskade automation. +The Taskade node for n8n is on npm as [`n8n-nodes-taskade`](https://www.npmjs.com/package/n8n-nodes-taskade). On self-hosted n8n, install it as a community node: see [its README](../packages/n8n-nodes-taskade/README.md#installation). n8n has not verified the node yet, and [issue #17](https://github.com/taskade/integrations/issues/17) tracks that review. If you cannot install a community node, for example on n8n Cloud, connect n8n and Taskade with the built-in n8n nodes and a Taskade automation. -**Who it is for:** n8n users, on n8n Cloud or self-hosted, who want a workflow to read or write Taskade. +**Who it is for:** n8n users who want a workflow to read or write Taskade without the Taskade node. **What it does:** An n8n workflow adds tasks to a Taskade project through the Taskade API, and a Taskade automation starts an n8n workflow with each new task. -**Before you start:** You need a Taskade account with a verified email. Taskade must reach your n8n over the public internet. The Taskade **Send HTTP Request** step blocks `localhost` and private network addresses. +**Before you start:** You need a Taskade account. Taskade must reach your n8n over the public internet. A `localhost` URL does not work. ## Steps -1. In Taskade, open **Settings**, then **API**, and click **Create token**. Copy the token. It starts with `tskdp_`. +1. In Taskade, open **Settings**, then **API**, and create a personal access token. Copy the token. It starts with `tskdp_`. 2. In n8n, add an **HTTP Request** node. Set **Method** to `POST` and **URL** to `https://www.taskade.com/api/v2/createTask`. 3. Set **Authentication** to **Generic Credential Type**, then **Header Auth**. Use the name `Authorization` and the value `Bearer tskdp_YOUR_TOKEN`. 4. Turn on **Send Body** and pick **JSON**. Set the JSON field to **Expression**, and paste the expression below with your project ID. The project ID is in the Taskade address bar, after `/d/`. @@ -38,14 +38,11 @@ You are done when an n8n run adds a task to your project, and a new Taskade task ## Notes - The **Header Auth** credential keeps the token out of the workflow JSON, so an exported workflow does not carry it. -- For Taskade events such as a task assigned, paste the n8n URL into **Settings** > **API** > **Outgoing webhooks** (Pro and above). Each delivery carries an `X-Taskade-Signature` header that you can check. -- When the Taskade node is on npm, it replaces steps 2 to 5 with a **Taskade** node and a **Taskade Trigger** node. - -## Taskade EVE can build this for you - -> Build an automation that sends every new task in my Requests project to my n8n webhook URL. +- For Taskade events such as a task assigned or a comment added, the **Taskade Trigger** node of the community node registers a signed webhook. It checks the `X-Taskade-Signature-V2` header of each delivery. Taskade webhook events need the Pro plan or higher. +- On self-hosted n8n, the **Taskade** node replaces steps 2 to 5, and the **Taskade Trigger** node replaces steps 6 and 7 for the events that it supports. ## Checked -- Taskade steps, labels and the `createTask` body: checked against the Taskade app and the [v2 spec](https://www.taskade.com/api/documentation/v2) on 2026-10-22. +- Taskade steps and labels: taken from the Taskade app on 2026-10-22. +- The `createTask` call and its body: the same as in the n8n node in this repository. - n8n labels (**HTTP Request**, **Generic Credential Type**, **Header Auth**, **Send Body**, **Expression**, **Execute step**, **Webhook**, **Production URL**): taken from n8n's public docs. Not checked in an n8n instance. diff --git a/recipes/square.md b/recipes/square.md index b1aa60a..b187579 100644 --- a/recipes/square.md +++ b/recipes/square.md @@ -1,6 +1,6 @@ # Connect Square to Taskade -Square has no Taskade integration yet. A Taskade webhook and the **Send HTTP Request** step with your Square access token cover the common jobs today. +This repository has no Square app. A Taskade webhook and the **Send HTTP Request** step with your Square access token cover the common jobs. **Who it is for:** Shops, studios and service teams that take payments in Square and track orders or clients in Taskade. @@ -33,18 +33,13 @@ You are done when a Square test payment adds a task, and the **Send HTTP Request ## Notes -- 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. +- With **Verify requests** set to **None**, 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. Do not type it into **Headers**. - To go live, change both the token and the host. Use your production access token and `https://connect.squareup.com/v2/customers`. A Sandbox token fails on the production host, and a production token creates real customers. - The **Only continue if...** step skips a payment that is not complete. It does not stop a duplicate task. Square retries an event that it did not see delivered, and a completed payment can send `payment.updated` again, for example after a refund. Thus one payment can add more than one task. The payment ID in the task text helps you find a duplicate. -- If the automation is off, the webhook URL answers 404, and Square retries the event. - -## Taskade EVE can build this for you - -> Build an automation that adds a task to my Orders project each time Square sends a completed payment to my webhook. ## Checked -- Taskade steps, labels and webhook behavior: checked against the Taskade app on 2026-10-22. -- Square facts (Developer Console labels, the `payment.updated` event and its payload paths, the Sandbox and production hosts, `/v2/customers` and its fields, the `Square-Version` header, the Square signature header, retries): taken from Square's public docs. Not checked in a Square account. -- A nested field such as `data.object.payment.status` in **Parameters**: the field builder supports nested objects, but this recipe was not run end to end. +- Taskade steps and labels: taken from the Taskade app on 2026-10-22. +- Square facts (Developer Console labels, the `payment.updated` event and its payload paths, the Sandbox and production hosts, `/v2/customers` and its fields, the `Square-Version` header, retries): taken from Square's public docs. Not checked in a Square account. +- A nested field such as `data.object.payment.status` in **Parameters** was not tested end to end.