Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,10 @@ The open source Taskade apps for Zapier, n8n and Make, built on the public Taska

Two more platforms keep their own Taskade apps in their own repositories: [Taskade on Activepieces](https://www.activepieces.com/pieces/taskade) and [Taskade on Pipedream](https://pipedream.com/apps/taskade).

## Recipes

Step-by-step recipes connect Taskade with Make, n8n, Square and other apps that have an API key. They use a Taskade automation and the Public Action API v2. Start at the [recipes index](recipes/README.md).

## What ships today

Every name below comes from the code in this repository. The [Zapier app reference](#zapier-app-reference) lists the Zapier keys.
Expand Down
35 changes: 35 additions & 0 deletions recipes/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
# Recipes

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.
- 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 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 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**](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 for Taskade webhook events |

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 \
-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. Do not type a key into the **Headers** or **Query params** fields.
41 changes: 41 additions & 0 deletions recipes/any-app-with-an-api-key.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,41 @@
# Connect any app with an API key

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 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.

**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 <key>` or `X-API-Key: <key>`.
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, 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
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"}]}'
```

## 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 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 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.
53 changes: 53 additions & 0 deletions recipes/make.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,53 @@
# Use Taskade with Make today

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 and a Make account. The Taskade API takes a personal access token.

## Steps

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`.
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:

```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.

## 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).
- 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 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.
48 changes: 48 additions & 0 deletions recipes/n8n.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,48 @@
# Use Taskade with n8n today

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 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. Taskade must reach your n8n over the public internet. A `localhost` URL does not work.

## Steps

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/`.
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:

```js
{{ {
"projectId": "YOUR_PROJECT_ID",
"tasks": [
{ "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.

## 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 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 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.
45 changes: 45 additions & 0 deletions recipes/square.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,45 @@
# Connect Square to Taskade

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.

**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. 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.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 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):

```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

- 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.

## Checked

- 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.
Loading