# Plugin Activated

<!-- meta: type=event-wp-activated_plugin; location=WordPress Events › Plugin Events; category=Trigger; platforms=WordPress -->

## Overview

Plugin Activated is a **Trigger** in **WordPress Events › Plugin Events**. Starts your flow when this WordPress hook fires (activated_plugin).

Use the General and Design tabs to narrow when it should run. The Payload Fields section lists data WordPress passes to the flow.

Save and activate the flow, then perform the action on your WordPress site to test.

When this trigger fires, JOrchestrator starts the flow and passes the incoming event or request data to the next connected step. Configure filtering, payload shape, and security on the **Design** tab.

## Why use this node

Plugin Activated is a **trigger** in the **WordPress Events › Plugin Events** group. Triggers start a flow. They listen for an external signal — a CMS event, inbound HTTP call, payment notification, or schedule — and pass the incoming data to the first downstream step.

Typical reasons teams add **Plugin Activated** to a flow:

- React when WordPress fires `activated.plugin` — automate follow-up work instead of custom theme functions.php code
- Send notifications or sync data whenever this hook runs on your linked WordPress site
- Chain CMS-native events into messaging, AI, or external API steps
- Replace fragile PHP snippets with a visual, testable flow

## When it runs

This **trigger** starts the flow when its signal fires on your linked site or when an inbound request matches its configuration. Downstream steps receive the trigger payload as their input.

## Example workflows

Common patterns on the canvas:

1. **Plugin Activated** → **Send Email** (notify editor)
2. **Plugin Activated** → **Set JSON** → **API REST POST** (sync to CRM)
3. **Plugin Activated** → **If** (role check) → **Send Notification**

## Properties panel

The designer shows these tabs for this node:

| Tab | Purpose |
|-----|---------|
| **Info** | Plain-language description and output payload fields for downstream steps |
| **Design** | Trigger configuration and payload schema |

### System (automatic — not edited by the user)

These fields are managed by the designer or runtime — you do not type into them directly:

| Property key | Label | Type | Required | Visible when | Notes |
|--------------|-------|------|----------|--------------|-------|
| `_nodeId` | Node ID | `node-id` | No | — | — |

### User-configured — General tab

| Property key | Label | Type | Required | Visible when | Notes |
|--------------|-------|------|----------|--------------|-------|
| `label` | Label | `text` | No | — | Node label |
| `value` | Value | `text` | No | — | Enter value |

### CMS site configuration (not on this node's properties panel)

Credentials, API keys, mailers, SMTP, and integration defaults are configured in the CMS plugin under **Node Configuration**, not per step on this node. Link the flow to a domain before testing CMS-backed fields.

## Output payload fields

_This node does not define standard output payload fields in the designer Info tab._

## Related nodes

Other steps in the same area of the palette:

- **Add Attachment** (`event-wp-add_attachment`) — WordPress Events › Media Events
- **After Switch Theme** (`event-wp-after_switch_theme`) — WordPress Events › Theme Events
- **Comment Posted** (`event-wp-comment_post`) — WordPress Events › Comment Events
- **Delete Attachment** (`event-wp-delete_attachment`) — WordPress Events › Media Events
- **Delete Comment** (`event-wp-delete_comment`) — WordPress Events › Comment Events