<!-- BusyBot node reference — https://busybot.net/tools/pushcut/ -->

> Node: Pushcut (`pushcut`) · Action · v1
> Category: Communication · Credentials: Pushcut API (`pushcutApi`)
> Updated: 2026-08-16

# Pushcut

> Send smart notifications to iOS devices via the Pushcut API.

## Overview

Pushcut is an iOS automation app that lets you send rich push notifications with actions to Apple devices. This tool sends notifications through a pre-configured notification template in the Pushcut app. You can override the title, text, and input of the notification, and optionally target specific devices. The Pushcut API uses an API key sent via the API-Key header. Each notification is sent to a named notification template identified by its notification name or ID.

**Category:** Communication  
**Tool Name:** `pushcut`  
**Version:** 1

**Appearance:** Icon: `lucide-Smartphone` | Color: `#1D72F3`

## Node Type

**Action** — processes input items and produces output

## Input / Output

| Direction | Port(s) |
|-----------|--------|
| Input | `Input` |
| Output | `Output`, `Error` |

## Credentials

This tool requires **Pushcut API** credentials.
See the [Credentials Guide](https://busybot.net/credentials/pushcut-api/) for setup instructions.

### Resources

| Resource | Value |
|----------|-------|
| Notification | `notification` |

### Operations

| Operation | Value | Description |
|-----------|-------|-------------|
| Notification: Send | `send` | Send a notification |

### Parameters

#### Notification: Send

| Parameter | Type | Required | Default | Description |
|-----------|------|----------|---------|-------------|
| Notification Name | `string` | Yes | — | The name or ID of the notification template to send. Find in the Pushcut iOS app under your configured notifications. You can also retrieve the list via GET https://api.pushcut.io/v1/notifications. Supports expressions. |
| Additional Fields | `collection` | No | `{}` | Additional optional fields for the notification. |
| — Devices | `string` | No | — | Comma-separated list of device names or IDs to target. If empty, sends to all devices. Find device IDs via GET https://api.pushcut.io/v1/devices. |
| — Input | `string` | No | — | Value that is passed as input to the notification action. |
| — Text | `string` | No | — | Text that is used instead of the one defined in the app. |
| — Title | `string` | No | — | Title that is used instead of the one defined in the app. |

#### All Operations

| Parameter | Type | Required | Default | Description |
|-----------|------|----------|---------|-------------|
| Max Concurrency | `number` | No | `10` | Maximum number of items to process concurrently. |

## Output Data

One output item is produced per input item, on the `Output` port. The Pushcut response confirming the notification was sent is merged onto the item JSON at the top level — it is not nested under a wrapper property — so the rest of the incoming item passes through unchanged and any response field is addressed directly, for example `{{ $json.id }}`. Binary data on the input item is forwarded untouched.

Pushcut answers a successful send with a short acknowledgement, and when it replies with no body at all nothing is merged, so the item passes straight through. There is no fan-out: sending to several devices still produces exactly one output item. Failures go to the `Error` port in `errorPort` mode, carrying `_error`.

## Usage Examples

- Send a push notification to all iOS devices via Pushcut
- Send a Pushcut notification with custom title and text
- Trigger a Pushcut notification targeting a specific device
- Send an iOS notification with input data for the action

## Example Configuration

Send a notification template exactly as it is configured in the Pushcut app:

```json
{
  "type": "pushcut",
  "parameters": {
    "resource": "notification",
    "operation": "send",
    "notificationName": "Daily Reminder"
  }
}
```

Override the template's title and text with values from the incoming item:

```json
{
  "type": "pushcut",
  "parameters": {
    "resource": "notification",
    "operation": "send",
    "notificationName": "Weather Alert",
    "additionalFields": {
      "title": "Weather Update",
      "text": "{{ $json.forecast }}"
    }
  }
}
```

Target named devices and hand the notification's action a value to work with:

```json
{
  "type": "pushcut",
  "parameters": {
    "resource": "notification",
    "operation": "send",
    "notificationName": "Task Complete",
    "additionalFields": {
      "title": "Workflow Finished",
      "text": "Your automation task has completed successfully",
      "devices": "iPhone, iPad",
      "input": "{{ $json.resultId }}"
    },
    "maxConcurrency": 5
  }
}
```

### Error Handling

| Mode | Behavior |
|------|----------|
| **stop** | Halts workflow on first error |
| **continue** | Skips failed items, passes successful ones through |
| **errorPort** | Routes failed items to Error output port |

## Tips

Send smart push notifications to iOS devices via the Pushcut app, with optional title/text overrides and device targeting.

### Notes

- The notification template must already exist in the Pushcut iOS app. This node triggers a template by name or ID; it cannot create one.
- Title and Text override what the template defines. Leave them empty to use the template's own wording.
- Devices takes one comma-separated string, which the node splits into a list of device names before sending. Leave it empty to reach every device on the account.