n8n-nodes-listbee 0.20.0 → 0.99.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +15 -166
- package/dist/package.json +2 -1
- package/package.json +2 -1
package/README.md
CHANGED
|
@@ -1,172 +1,21 @@
|
|
|
1
|
-
# n8n-nodes-listbee
|
|
1
|
+
# n8n-nodes-listbee (deprecated)
|
|
2
2
|
|
|
3
|
-
|
|
4
|
-
[](LICENSE)
|
|
3
|
+
**This n8n community node is deprecated.** ListBee has pivoted to an agent-native architecture.
|
|
5
4
|
|
|
6
|
-
|
|
5
|
+
## What to use instead
|
|
7
6
|
|
|
8
|
-
|
|
7
|
+
### Option 1: n8n HTTP Request node
|
|
8
|
+
Use n8n's built-in **HTTP Request** node with:
|
|
9
|
+
- **URL:** `https://api.listbee.so/v1/...`
|
|
10
|
+
- **Authentication:** Generic Credential Type -> Header Auth -> `Authorization: Bearer lb_...`
|
|
11
|
+
- **OpenAPI spec:** `https://listbee.so/openapi.json` (n8n can import OpenAPI specs for auto-generated request nodes)
|
|
9
12
|
|
|
10
|
-
|
|
13
|
+
### Option 2: n8n AI Agent with MCP
|
|
14
|
+
If you're building an AI agent workflow in n8n, point it at:
|
|
15
|
+
- **MCP HTTP:** `https://mcp.listbee.so`
|
|
11
16
|
|
|
12
|
-
|
|
17
|
+
### Reference
|
|
18
|
+
- **Docs:** `https://docs.listbee.so`
|
|
13
19
|
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
In n8n, go to **Credentials** → **Add Credential** → **ListBee API**, paste your key, and save. n8n verifies it automatically against the API.
|
|
17
|
-
|
|
18
|
-
## Nodes
|
|
19
|
-
|
|
20
|
-
### ListBee (regular node)
|
|
21
|
-
|
|
22
|
-
API operations across all ListBee resources. Can also be used as an AI tool node.
|
|
23
|
-
|
|
24
|
-
### ListBee Trigger
|
|
25
|
-
|
|
26
|
-
Starts workflows when ListBee events occur. Automatically registers and cleans up webhooks when the workflow is activated or deactivated. Incoming events are verified using HMAC-SHA256 signatures.
|
|
27
|
-
|
|
28
|
-
## Operations
|
|
29
|
-
|
|
30
|
-
25 operations across 9 resources.
|
|
31
|
-
|
|
32
|
-
### Account
|
|
33
|
-
|
|
34
|
-
| Operation | Description |
|
|
35
|
-
|-----------|-------------|
|
|
36
|
-
| Get | Get account status, plan, fee rate, and operational readiness |
|
|
37
|
-
| Update | Update account settings (GA Measurement ID, order notifications, events callback URL) |
|
|
38
|
-
| Delete | Permanently delete the account and all associated data |
|
|
39
|
-
|
|
40
|
-
### API Keys
|
|
41
|
-
|
|
42
|
-
| Operation | Description |
|
|
43
|
-
|-----------|-------------|
|
|
44
|
-
| Self Revoke | Permanently revoke the API key used to authenticate this request |
|
|
45
|
-
|
|
46
|
-
### Bootstrap
|
|
47
|
-
|
|
48
|
-
Public endpoints — no API key required. Use these to automate account creation and onboarding flows.
|
|
49
|
-
|
|
50
|
-
| Operation | Description |
|
|
51
|
-
|-----------|-------------|
|
|
52
|
-
| Start | Begin account bootstrap — sends a verification OTP to the email address |
|
|
53
|
-
| Verify | Verify the OTP code (`bootstrap_token` + `otp_code`) — returns `api_key`, `account_id`, and `stripe_onboarding_url` |
|
|
54
|
-
| Poll | Check bootstrap status by account ID — returns readiness and Stripe onboarding state |
|
|
55
|
-
|
|
56
|
-
### Events
|
|
57
|
-
|
|
58
|
-
| Operation | Description |
|
|
59
|
-
|-----------|-------------|
|
|
60
|
-
| List | List all events, optionally filtered by type, listing ID, or order ID |
|
|
61
|
-
|
|
62
|
-
### Listing
|
|
63
|
-
|
|
64
|
-
| Operation | Description |
|
|
65
|
-
|-----------|-------------|
|
|
66
|
-
| Create | Create a listing with product page and payment link |
|
|
67
|
-
| Get | Get a listing by ID |
|
|
68
|
-
| Get Many | List all listings, optionally filtered by status (draft/published/archived) |
|
|
69
|
-
| Update | Update listing fields (name, price, description, cover, and more) |
|
|
70
|
-
| Delete | Delete a listing permanently |
|
|
71
|
-
| Publish | Make a draft listing publicly visible |
|
|
72
|
-
| Unpublish | Revert a published listing back to draft state |
|
|
73
|
-
| Archive | Move a published listing to archived state |
|
|
74
|
-
|
|
75
|
-
**Create and Update support:** name, price, description, tagline, CTA, compare-at price, image URL, currency, highlights, badges, rating, rating count, deliverable (single), agent callback URL, signing secret, reviews, FAQs, checkout schema, and metadata.
|
|
76
|
-
|
|
77
|
-
### Order
|
|
78
|
-
|
|
79
|
-
| Operation | Description |
|
|
80
|
-
|-----------|-------------|
|
|
81
|
-
| Get | Get an order by ID |
|
|
82
|
-
| Get Many | List orders, optionally filtered by status, listing, buyer email, or date range |
|
|
83
|
-
| Fulfill | Mark an order as fulfilled, optionally pushing a single deliverable to the buyer |
|
|
84
|
-
| Redeliver | Re-send the delivery to the buyer (resends access grant or deliverable) |
|
|
85
|
-
| Refund | Issue a full refund for a paid order |
|
|
86
|
-
|
|
87
|
-
### Plan
|
|
88
|
-
|
|
89
|
-
| Operation | Description |
|
|
90
|
-
|-----------|-------------|
|
|
91
|
-
| List | List all available plans with pricing (public endpoint, no authentication required) |
|
|
92
|
-
|
|
93
|
-
### Stripe
|
|
94
|
-
|
|
95
|
-
| Operation | Description |
|
|
96
|
-
|-----------|-------------|
|
|
97
|
-
| Connect | Get a Stripe Connect onboarding URL for guided account setup |
|
|
98
|
-
| Disconnect | Remove Stripe configuration from your account |
|
|
99
|
-
|
|
100
|
-
### Utility
|
|
101
|
-
|
|
102
|
-
| Operation | Description |
|
|
103
|
-
|-----------|-------------|
|
|
104
|
-
| Ping | Check API connectivity and verify API key validity |
|
|
105
|
-
|
|
106
|
-
## Trigger Events
|
|
107
|
-
|
|
108
|
-
The ListBee Trigger node supports all 10 event types:
|
|
109
|
-
|
|
110
|
-
| Event | Description |
|
|
111
|
-
|-------|-------------|
|
|
112
|
-
| `order.paid` | A purchase was completed and payment confirmed |
|
|
113
|
-
| `order.fulfilled` | An order was fulfilled (managed or external delivery confirmed) |
|
|
114
|
-
| `order.refunded` | An order was refunded |
|
|
115
|
-
| `order.disputed` | A chargeback or dispute was opened |
|
|
116
|
-
| `order.dispute_closed` | A dispute was resolved |
|
|
117
|
-
| `order.canceled` | An order was canceled |
|
|
118
|
-
| `listing.created` | A new listing was created |
|
|
119
|
-
| `listing.updated` | A listing was updated |
|
|
120
|
-
| `listing.published` | A listing was published and made public |
|
|
121
|
-
| `listing.deleted` | A listing was deleted |
|
|
122
|
-
|
|
123
|
-
Leave the events field empty to subscribe to all events.
|
|
124
|
-
|
|
125
|
-
## Fulfillment Workflows
|
|
126
|
-
|
|
127
|
-
ListBee supports two fulfillment modes:
|
|
128
|
-
|
|
129
|
-
**Managed** — ListBee delivers digital content automatically after payment. Set deliverables on the listing (file, URL, or text) and ListBee handles the rest.
|
|
130
|
-
|
|
131
|
-
**External** — ListBee fires `order.paid` and you handle delivery in n8n. Use the Fulfill operation to push generated or processed content back to ListBee for delivery.
|
|
132
|
-
|
|
133
|
-
Typical managed fulfillment workflow:
|
|
134
|
-
|
|
135
|
-
1. **Listing: Create** with name, price, and `deliverable` (URL or text) → get a listing ID
|
|
136
|
-
2. **Listing: Publish** → listing goes live with a checkout URL
|
|
137
|
-
3. ListBee delivers the deliverable to the buyer automatically after payment
|
|
138
|
-
|
|
139
|
-
Typical external fulfillment workflow:
|
|
140
|
-
|
|
141
|
-
1. **ListBee Trigger** (`order.paid`) → workflow starts, or use `agent_callback_url` on the listing
|
|
142
|
-
2. Generate or retrieve content
|
|
143
|
-
3. **Order: Fulfill** → push a single deliverable to ListBee for the buyer
|
|
144
|
-
|
|
145
|
-
## Pagination
|
|
146
|
-
|
|
147
|
-
List operations (Get Many) use cursor-based pagination. Set **Limit** (1–100, default 50) to control page size. The response includes a `cursor` field and `has_more` boolean — pass the cursor value to the next request to fetch the next page.
|
|
148
|
-
|
|
149
|
-
## Error Handling
|
|
150
|
-
|
|
151
|
-
The node parses ListBee's RFC 9457 error responses into readable messages:
|
|
152
|
-
|
|
153
|
-
- `Validation error: Price must be greater than 0 [field: price]`
|
|
154
|
-
- `Rate limit exceeded — retry after 60s`
|
|
155
|
-
- `Listing not found`
|
|
156
|
-
|
|
157
|
-
Error responses include a request ID for support debugging.
|
|
158
|
-
|
|
159
|
-
## Idempotency
|
|
160
|
-
|
|
161
|
-
Create and action operations support an optional **Idempotency Key** in Additional Fields. The same key and request body combination returns a cached response instead of creating a duplicate — safe for retries.
|
|
162
|
-
|
|
163
|
-
## Links
|
|
164
|
-
|
|
165
|
-
- [ListBee API Docs](https://docs.listbee.so)
|
|
166
|
-
- [npm](https://www.npmjs.com/package/n8n-nodes-listbee)
|
|
167
|
-
- [CHANGELOG](CHANGELOG.md)
|
|
168
|
-
- [n8n Community Nodes](https://docs.n8n.io/integrations/community-nodes/)
|
|
169
|
-
|
|
170
|
-
## License
|
|
171
|
-
|
|
172
|
-
[MIT](LICENSE)
|
|
20
|
+
## Reversibility
|
|
21
|
+
Email damian@listbee.so if you need a first-class n8n node again.
|
package/dist/package.json
CHANGED
|
@@ -1,6 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "n8n-nodes-listbee",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.99.0",
|
|
4
|
+
"deprecated": "Use n8n HTTP Request node with https://api.listbee.so or MCP at https://mcp.listbee.so",
|
|
4
5
|
"description": "n8n community node for the ListBee commerce API",
|
|
5
6
|
"license": "MIT",
|
|
6
7
|
"homepage": "https://listbee.so",
|
package/package.json
CHANGED
|
@@ -1,6 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "n8n-nodes-listbee",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.99.0",
|
|
4
|
+
"deprecated": "Use n8n HTTP Request node with https://api.listbee.so or MCP at https://mcp.listbee.so",
|
|
4
5
|
"description": "n8n community node for the ListBee commerce API",
|
|
5
6
|
"license": "MIT",
|
|
6
7
|
"homepage": "https://listbee.so",
|