Skip to content

Commit a9c3517

Browse files
author
Cowork 3P
committed
docs: fix English n8n docs to match Chinese version
- Add missing image references (n8n-1.png through n8n-5.png) - Fix broken step numbering in installation and credential sections - Convert Troubleshooting section to <details>折叠面板 format
1 parent d3c626f commit a9c3517

1 file changed

Lines changed: 19 additions & 13 deletions

File tree

  • src/content/docs/integrations/workflows-and-notifications

src/content/docs/integrations/workflows-and-notifications/n8n.md

Lines changed: 19 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -36,15 +36,15 @@ For n8n Cloud users, installation is straightforward — search and add the node
3636
2. Open the **nodes panel** (click the **+** button on the canvas).
3737
3. Search for **CoreClaw** in the community node registry.
3838

39-
Search for CoreClaw node in n8n
39+
![Search for CoreClaw node in n8n](@/assets/docs/n8n-1.png)
4040

41-
1. Click **Install node** to add the CoreClaw node to your instance.
41+
4. Click **Install node** to add the CoreClaw node to your instance.
4242

43-
Install n8n-nodes-coreclaw package
43+
![Install n8n-nodes-coreclaw package](@/assets/docs/n8n-2.png)
4444

4545
After installation, you can find the CoreClaw node under **Community Nodes** in the nodes panel.
4646

47-
CoreClaw node in Community Nodes list
47+
![CoreClaw node in Community Nodes list](@/assets/docs/n8n-3.png)
4848

4949
### Create credentials
5050

@@ -53,14 +53,14 @@ Before using the CoreClaw node, you need to create a credential with your CoreCl
5353
1. In n8n, go to **Credentials****Add Credential**.
5454
2. Search for **CoreClaw API** and select it.
5555

56-
Create CoreClaw API credential
56+
![Create CoreClaw API credential](@/assets/docs/n8n-4.png)
5757

58-
1. Enter a name for the credential (e.g., "CoreClaw Production").
59-
2. In the **API Key** field, paste the API key you copied from the [CoreClaw Console](https://console.coreclaw.com/settings/integrations).
58+
3. Enter a name for the credential (e.g., "CoreClaw Production").
59+
4. In the **API Key** field, paste the API key you copied from the [CoreClaw Console](https://console.coreclaw.com/settings/integrations).
6060

61-
Enter API key and save credential
61+
![Enter API key and save credential](@/assets/docs/n8n-5.png)
6262

63-
1. Click **Save** to store the credential.
63+
5. Click **Save** to store the credential.
6464

6565
You can now use this credential in any CoreClaw node in your workflows.
6666

@@ -299,13 +299,16 @@ Full API reference: [API Integration](/api/integration/).
299299

300300
## Troubleshooting
301301

302-
**Node not appearing after installation**
302+
<details>
303+
<summary><strong>Node not appearing after installation</strong></summary>
303304

304305
1. Refresh the n8n page.
305306
2. Check **Settings → Community Nodes** — the node should be listed there.
306307
3. If using n8n Cloud, ensure verified community nodes are enabled in the Cloud Admin Panel.
308+
</details>
307309

308-
**Invalid API key error**
310+
<details>
311+
<summary><strong>Invalid API key error</strong></summary>
309312

310313
1. Verify the API key in the [CoreClaw Console](https://console.coreclaw.com/settings/integrations).
311314
2. Ensure there are no extra spaces or line breaks in the credential.
@@ -319,8 +322,10 @@ curl -X POST "https://openapi.coreclaw.com/api/v1/account/info" \
319322
```
320323

321324
A successful response contains `code: 0`.
325+
</details>
322326

323-
**Worker-specific input fields**
327+
<details>
328+
<summary><strong>Worker-specific input fields</strong></summary>
324329

325330
Each Worker has different input parameters. To find the correct fields:
326331

@@ -335,4 +340,5 @@ Or call the API:
335340
curl "https://openapi.coreclaw.com/api/scraper?slug=YOUR_SCRAPER_SLUG"
336341
```
337342

338-
The response contains `data.parameters.custom.properties` — each entry maps to an input field.
343+
The response contains `data.parameters.custom.properties` — each entry maps to an input field.
344+
</details>

0 commit comments

Comments
 (0)