Core & Utility Nodes

Nodes2Cloud includes several utility nodes that aren't tied to a specific third-party integration but provide essential functionality for building, testing, and managing your workflows.

These nodes generally do not require any credentials.

---

1. Manual Trigger

What the node does

The Manual Trigger allows you to execute a workflow by clicking a button in the editor. It is primarily used for testing and debugging your workflow as you build it.

Options / Fields

• Mock Data (JSON): (Optional) You can provide a custom JSON payload here. When you manually trigger the workflow, this JSON will be passed down to the next node as the initial payload. This is extremely useful for simulating webhooks or testing edge cases without having to fire the real event.

How to set it up

1. Add the Manual Trigger as the very first node in your workflow.
2. (Optional) Provide mock data in the Mock Data field if your downstream nodes expect specific variables to exist.
3. Click the "Run Workflow" or "Test" button in the editor.

---

2. Markdown

What the node does

The Markdown node converts text between different formats, most commonly transforming Markdown text into HTML. This is highly useful when you generate text via an AI agent and need to send it via an email or platform that requires HTML.

Options / Fields

• Input Text: The text you want to convert.
• Mode / Operation: The conversion direction (e.g., Markdown to HTML).

How to set it up

1. Pass the markdown text you want to convert into the Input Text field.
2. Ensure the correct conversion mode is selected.
3. The output will be the converted string (e.g., <h1>Heading</h1>).

---

3. Unsupported (Imported)

What the node does

This is a special fallback node used internally by Nodes2Cloud's migration engine. When you import a workflow from another automation platform (like n8n, Make, or Zapier), if Nodes2Cloud encounters a node type it doesn't currently support, it will replace it with this "Unsupported" node.

Options / Fields

• Original Node Data: Displays the raw JSON configuration of the original node from the imported platform.

How to set it up

1. You typically don't add this node yourself. It appears automatically during an import.
2. The node preserves the original configuration so no data is lost.
3. Troubleshooting: Workflows containing an Unsupported node will fail to compile and run. You must manually replace this node with a supported Nodes2Cloud equivalent (like an HTTP Request node or a custom JavaScript node) before the workflow can be activated.