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

> Node: Pushcut Trigger (`pushcut_trigger`) · Webhook trigger · v1
> Category: Utility · Credentials: Pushcut (`pushcutApi`)
> Updated: 2026-08-16

# Pushcut Trigger

> Triggers when a Pushcut server action is executed from an iOS device

## Overview

Receives webhook notifications from Pushcut when a user triggers a server action from the Pushcut iOS app. Pushcut is an iOS automation app that sends smart notifications with custom actions. When a server action is tapped in the app, Pushcut sends a POST request to the registered webhook URL with the action context payload. The trigger registers a subscription with the Pushcut API using a user-defined action name, which then appears as a server action in the Pushcut iOS app. The entire incoming request body is captured and forwarded as the trigger output. Useful for building mobile-triggered automations, remote server controls, iOS shortcut integrations, and notification-driven workflows.

**Category:** Utility  
**Tool Name:** `pushcut_trigger`  
**Version:** 1

**Appearance:** Icon: `lucide-Smartphone` | Color: `#ce3e00`

## Node Type

**Trigger** — webhook (receives incoming HTTP callbacks)

## Input / Output

| Direction | Port(s) |
|-----------|--------|
| Input | None (trigger node) |
| Output | `Output` |

## Credentials

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

### Parameters

| Parameter | Type | Required | Default | Description |
|-----------|------|----------|---------|-------------|
| Action Name | `string` | No | — | Choose any name you would like. It will show up as a server action in the Pushcut iOS app. |

## Output Data

Each incoming Pushcut request produces one output item. The item carries three metadata fields, and the request body is merged in at the top level:

- `_trigger` — always `pushcut_webhook`
- `_timestamp` — ISO 8601 timestamp of when the request arrived
- `_webhookEvent` — always `action_triggered`

Everything Pushcut sends in the body (for example the action name, any text you typed into the notification, and the device list) sits alongside those fields. Reference it downstream by expression, e.g. `{{ $json.actionName }}`.

## Usage Examples

- Start a workflow when a Pushcut notification action is tapped on iPhone
- Trigger a server task from an iOS shortcut via Pushcut
- Run a home automation routine from a Pushcut notification
- Execute a deployment script when a Pushcut server action is triggered

## Example Configuration

Register a server action named "Deploy Production":

```json
{
  "type": "pushcut_trigger",
  "parameters": {
    "actionName": "Deploy Production"
  }
}
```

Register a server action for a home automation routine:

```json
{
  "type": "pushcut_trigger",
  "parameters": {
    "actionName": "Evening Routine"
  }
}
```

### Trigger Behavior

- **Activation:** When the workflow is activated, a webhook endpoint is registered with the service.
- **Deactivation:** The webhook is automatically unregistered when the workflow is deactivated.
- **Payload:** The incoming webhook payload is parsed and output as workflow items.
- **Verification:** Supports signature verification where applicable.

## Tips

Entry point that fires when a Pushcut server action is triggered from the iOS app. Configure the Action Name parameter -- this name will appear as a server action in the Pushcut app. When a user taps the action in a notification or runs it from the app, Pushcut sends a POST request to this webhook with the action context payload.