InitfinityTMGetting Started with Initfinity
Initfinity is a visual workflow builder where you connect nodes to create automations directly in your browser.
Core ideas
- Flows are built with nodes and edges.
- Each node performs one job, like transforming text, calling an API, or handling files.
- Data moves from one node to the next through connections.
Basic features
- Canvas editing: Drag, connect, and organize workflow nodes visually.
- Inspector controls: Configure each node with form controls, code fields, and validation.
- Flow execution: Run your workflow and observe how data progresses through the graph.
- Tips and shortcuts: Use the Help Center tips tab to discover common actions faster.
- Code when you need it: Drop into JavaScript or Python with the Code node.
- Run without a browser: Host a flow to run it on a schedule or from a webhook URL.
- Product tour: Launch the guided tour from the About tab for a quick walkthrough.
Suggested first workflow
- Add two simple nodes (for example, an input and a transformer).
- Connect their ports.
- Configure options in the Inspector.
- Run the flow and inspect the output.
Keep exploring
Browse the other articles to go further: schedule a flow, host it behind a webhook, add an AI agent, or script a step in code. The template gallery has ready-made flows to start from.
Coming from n8n, Make or Zapier
Choose File > Import, pick n8n workflow and select an exported workflow (or search "import" in the command palette). Triggers, schedules, HTTP requests, code, Set, Wait and If nodes are converted; anything else becomes a pass-through code node so the wiring stays intact. If conditions that compare plain $json fields become a small code node in front of the condition. HTTP request bodies become a small code node in front of the request, and query parameters are added to the URL. A note on the canvas lists everything that needs a manual look, such as other expressions and credentials.
The same menu imports a Make scenario (a blueprint exported as JSON) and a Zapier export. Make's HTTP requests, sleeps and routers are converted and webhook triggers become a Start trigger; Zapier steps become a chain where delays, code steps and webhook requests are converted. Everything else becomes a pass-through code node, and a note on the canvas lists what needs a manual look. Zapier imports are best effort, because Zapier does not document its export format.