O que construímos depois.
Proponha ideias, vote nas que você precisa e acompanhe o status. As mais votadas sobem na lista.
Flow: Add a Convert to file step for CSV and JSON attachments
n8n Convert to File and Extract from File turn rows into CSV or JSON and back (https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.converttofile/). Flow has no binary or file data between steps: action.email sends text only (lib/flow-schema.ts). Weekly report flows end up pasting rows into the email body. First scope: build a CSV string from a list and attach it to the email step.
Flow: Add a Compare datasets step to find new, changed and removed rows
n8n Compare Datasets returns items only in A, only in B, equal and different (https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.comparedatasets/). Flow has no way to diff two lists without writing code in data.code (lib/flow-schema.ts). Syncing a Sheet with CRM contacts is a common first flow for small teams. First scope: two lists, a key field and four outputs.
Flow: Add a Digest step that collects items and releases them on a schedule
Zapier Digest collects entries over time and releases them as one summary (https://zapier.com/apps/digest/integrations). Flow can approximate it with a data table and a schedule flow (lib/flow-tables.ts) but needs two flows and manual cleanup. A Digest step would append to a named bucket and a schedule trigger would read and clear it. This matters for teams that want one daily email instead of one email per event. First scope: append, release and clear on a per-flow bucket.
Flow: Add a Split out step that turns a list field into one item per entry
n8n has Split Out and Aggregate nodes to move between a list and separate items (https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.splitout/). Flow loops over a list with logic.loop (lib/flow-schema.ts) capped at 100 items and with no Delay inside. A step that fans a list into items would let nodes after it run per entry without those limits. First scope: a list template and a field to keep, up to 1,000 items.
Flow: Add a Stop and error step that fails a run with a custom message
n8n has a Stop and Error node (https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.stopanderror/) and Zapier has Paths with a halt option. Flow can only fail through a node error or a Code step (lib/flow-engine.ts), so a branch that should end as failed needs a script. A step with a message template would route into the existing failure alert and error flow. First scope: one field with the message and an optional error code.
- 0
Flow: Sort, limit and remove duplicates from a list in one step
Done. n8n has Sort, Limit and Remove Duplicates nodes (https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.sort/) and Zapier Formatter has Utilities such as pick from list. Flow had only Merge/Aggregate and the Code step (lib/flow-schema.ts, data.merge). The new List step covers sort, limit and dedupe over a list from an earlier node.
- 0
Flow: Cap runs per flow and hold the excess for review
Zapier flood protection holds runs when a trigger fires more than 100 times at once (configurable up to 1,500) and lets you replay or discard them (https://help.zapier.com/hc/en-us/articles/32466537676685-Adjust-flood-protection-limits-in-Zap-workflows). In Flow a bulk CRM import or a webhook loop starts one run per event with no limit, which can send hundreds of Slack messages or emails. First scope: a per-flow 'max runs per 10 minutes' setting (default 100), held runs listed in the Runs tab with Run all and Discard, and an email to the owner when it trips. Priority: medium. Effort: S. Compared with Zapier.
Flow: Expose flows over MCP and the public v1 API
Zapier MCP and the n8n MCP Server Trigger let Claude, ChatGPT or Cursor call workflows as tools, and both have a REST API to list, run and inspect workflows (https://zapier.com/mcp, https://docs.n8n.io/build/ways-of-building-workflows/connect-to-n8n-mcp-server.md). app/api/v1 covers agents, calendar, chat, crm, links and robots but not flows. First scope: GET /api/v1/flows, POST /api/v1/flows/{id}/run with inputs and GET /api/v1/flows/runs/{id} behind a flow:run scope, then an MCP endpoint that lists flows with a manual or webhook trigger as tools. Priority: medium. Effort: M. Compared with Zapier / n8n.
- 0
Flow: Add folders, list search and row actions to the flows list
Zapier groups Zaps in shared folders (https://zapier.com/pricing) and n8n uses projects with search and tags. The Flow list is flat with no search, and renaming, duplicating or deleting requires opening the editor (there is no duplicate at all). Past 20 or 30 flows the list stops scaling. First scope: a row menu with Rename, Duplicate and Delete (using the app's confirm dialog instead of window.confirm), a search box, then folders with the same model as Link folders. Priority: medium. Effort: S. Compared with Zapier / n8n.
- 0
Flow: Add hosted forms that start a flow and approval forms that collect data
Zapier Forms (formerly Interfaces) and the n8n Form Trigger give a public page whose submissions start a workflow, and n8n's Wait node can resume on a second form (https://help.zapier.com/hc/en-us/articles/15927500577037-Use-forms-in-Zapier-Interfaces, https://docs.n8n.io/build/flow-logic/wait.md). Flow only reacts to CRM form.submitted, which also creates a contact. Internal requests (refunds, access, purchase approvals) need a plain form. First scope: trigger.form with fields defined in the node and a public URL like the webhook token, then a 'collect fields' option on the Approval step. Priority: medium. Effort: M. Compared with Zapier / n8n.
- 0
Flow: Show a workspace run history with search by data and a usage dashboard
Zapier Zap History lists every run across Zaps with filters and CSV export (https://help.zapier.com/hc/en-us/articles/8496294549005-Export-your-Zap-history); n8n has an executions list searchable by data and an Insights dashboard with failure rate and time saved (https://n8n.io/pricing/). Flow runs are only visible inside each flow's Runs tab, so 'what failed last night' means opening flows one by one. First scope: /app/flow/runs with all runs, filters for flow, status and date, search inside trigger data, and a header with runs, failures and failure rate for the last 7 and 30 days. Priority: medium. Effort: M. Compared with Zapier / n8n.
- 0
Flow: Add polling triggers for RSS feeds, IMAP inboxes and changed HTTP responses
Most Zapier triggers are polling triggers (every 1 to 15 minutes by plan, https://zapier.com/pricing) and n8n ships RSS Feed Trigger, Email Trigger (IMAP) and generic polling. Flow triggers are internal events, webhook, schedule, Stripe and manual (lib/flow-schema.ts), so any service without webhooks needs a schedule plus HTTP plus a data table to dedupe by hand. The minute cron and flow tables already give polling and dedupe state. First scope: trigger.rss and trigger.http_poll (fires when a JSON path changes), deduped by item id in a hidden table, then IMAP. Priority: medium. Effort: M. Compared with Zapier / n8n.
- 0
Flow: Export and import flows as JSON and copy nodes between flows
n8n workflows are plain JSON on every plan: download, import, or paste onto the canvas (https://docs.n8n.io/workflows/export-import/). Zapier offers Zap import/export on Team and Enterprise (https://help.zapier.com/hc/en-us/articles/8496308481933-Import-and-export-Zaps-in-your-Team-or-Enterprise-account). Flow has no export, no import and no node clipboard, so a flow cannot move between workspaces, be kept in git or be shared in a support thread. First scope: Export JSON in flow settings (credentials replaced by their type), Import on /app/flow that validates with validateGraph, and Cmd+C / Cmd+V of selected nodes in the editor. Priority: high. Effort: S. Compared with n8n.
- 0
Flow: Keep a draft separate from the published version that runs
n8n 2.0 split Save from Publish and production runs the published version (https://docs.n8n.io/workflows/publish/); Zapier keeps drafts apart from the live Zap (https://help.zapier.com/hc/en-us/articles/9693520498445-Create-Zap-versions). In Flow, Save writes flow_flows.graph and bumps the version, so an enabled flow starts running the half-edited graph the moment you press Cmd+S (lib/flow.ts updateFlow). Versions and diffGraphs already exist. First scope: a draft_graph column the editor saves to, a Publish button that copies it to graph and creates the version, and a 'Draft differs from published' note in the header. Priority: high. Effort: M. Compared with Zapier / n8n.
- 0
Flow: Build a flow from a plain-language description
Zapier Copilot and the n8n AI Workflow Builder turn a sentence like 'when a deal is won, create the Stripe customer and post in #sales' into a working draft (https://docs.n8n.io/release-notes/, https://zapier.com/pricing). Flow has ai.text and ai.agent nodes but nothing that writes the graph: every flow starts from one of 16 templates or an empty canvas. The node catalog, event samples and validateGraph in lib/flow-schema.ts are already a typed spec an LLM can target through the AI gateway. First scope: a 'Describe your flow' box on /app/flow that returns a validated graph opened in the editor as unsaved changes, with missing credentials flagged on each node. Priority: high. Effort: M. Compared with Zapier / n8n.
Flow: Add a WhatsApp Business Cloud node to send messages and receive replies
n8n ships a WhatsApp Business Cloud node and trigger, also used as an approval channel (https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.whatsapp/), and WhatsApp is among Zapier's top messaging apps. Flow has Slack, Discord and Telegram but no WhatsApp (lib/flow-integrations.ts, lib/flow-credentials-schema.ts), and the generic webhook cannot pass Meta's GET verification (see the webhook gap). Latin America is our home market (PRODUCT.md), where WhatsApp is the default channel for booking reminders, lead follow-up and support. First scope: credential (phone number id plus token), send text and template message, and a trigger for incoming messages with signature check. Priority: medium. Effort: M. Compared with Zapier / n8n.
- 0
Flow: Test a single step with pinned sample data instead of running the whole flow
n8n lets you execute one node and pin its output so later test runs reuse it without calling external systems again, and edit the pinned data to test edge cases (https://docs.n8n.io/data/data-pinning/); Zapier tests each step on its own while building. Flow can test the whole flow with a manual input and rerun from a step of a past run (components/flow/FlowEditor.tsx testRun, lib/flow-engine.ts rerunFromStep), but every test fires all real side effects (Slack posts, emails, Stripe customers). First scope: a 'Test this step' button that runs one node against the last outputs (lib/flow.ts lastOutputs) or editable pinned JSON, without running downstream nodes. Priority: medium. Effort: M. Compared with Zapier / n8n.
- 0
Flow: Add Wait until a date and wait for a resume call to the Delay step
n8n's Wait node resumes after an interval, at a specified date and time, on a unique per-run resume webhook, or on a form submission (https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.wait/); Zapier Delay offers Delay For and Delay Until. Our Delay only waits a relative amount capped at 30 days (lib/flow-engine.ts logic.delay), so 'one day before the booking starts' or 'on the deal close date' cannot be expressed. Our apps are full of dates (bookings, deal close dates, issue due dates), which makes this especially valuable. First scope: a mode select on logic.delay with 'until' taking a templated date plus offset, and a 'resume URL' mode that reuses the hook route. Priority: medium. Effort: S. Compared with Zapier / n8n.
- 0
Flow: Email the flow owner when runs fail and offer automatic replay
Zapier emails owners about errors and offers autoreplay, which retries a failed step up to 5 times and holds the error email until the last attempt fails, set per account or per Zap (https://help.zapier.com/hc/en-us/articles/8496241726989). n8n uses an Error Trigger workflow. Flow has per-node retries, an optional error flow and manual rerun from a step, but nothing tells anyone a run failed unless they built an error flow themselves (no notification code in lib/flow-engine.ts finalize). Broken automations that fail silently are the main reason small teams stop trusting them. First scope: a per-flow 'notify on failure' toggle (on by default) sending one email digest per flow per hour, using the existing notifications and email modules. Priority: medium. Effort: S. Compared with Zapier / n8n.
- 0
Flow: Add AI extract and classify steps that return structured fields
n8n has an Information Extractor node that returns fields from a JSON schema, a JSON example or attribute descriptions, and a Text Classifier that routes to one output per category (https://docs.n8n.io/integrations/builtin/cluster-nodes/root-nodes/n8n-nodes-langchain.information-extractor/); Zapier's AI by Zapier returns named output fields. Our ai.text node returns free text only (lib/flow-engine.ts aiNode), so using the answer in an If or a CRM field needs a JSON parse step and luck. Typical small-team flows are 'classify this inbound email or chat as sales, support or spam' and 'extract name, company and budget from this form'. First scope: an output mode on ai.text with a field list (name, type, description) using structured output, and an ai.classify node with one output handle per category. Priority: medium. Effort: M. Compared with Zapier / n8n.
- 0
Flow: Add Google Sheets lookup, update and upsert rows plus a new row trigger
n8n's Google Sheets node supports append or update row, update row, get rows with filters, clear and delete (https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.googlesheets/sheet-operations/), and Zapier's most used Sheets trigger is 'New or Updated Spreadsheet Row'. Our Sheets node only appends a row or reads a whole range (lib/flow-integrations.ts sheetsConfigSchema operation append|read) and there is no Sheets trigger. Sheets is the default database of small teams, so 'update the row for this deal when it is won' and 'when a row is added, create a contact' are everyday cases. First scope: lookup by column, update and upsert by key column, and a polling trigger for new rows using the schedule infrastructure. Priority: medium. Effort: M. Compared with Zapier / n8n.
Flow: Connect Google, Slack and Notion with one-click OAuth that refreshes tokens
Zapier and n8n connect apps with an OAuth button and refresh tokens automatically (https://docs.n8n.io/integrations/builtin/credentials/google/oauth-single-service/). Flow credentials are pasted secrets: Google needs a service account JSON or a raw ya29 access token, and the generic oauth_token type stores only an access token with no refresh, so a pasted Google token stops working after about an hour (lib/flow-credentials-schema.ts). The repo already runs Google OAuth for Gmail and Calendar (app/api/integrations/gmail, app/api/integrations/google-calendar), so the plumbing exists. Pasting a service account is a non-starter for a founder setting up a sheet sync. First scope: OAuth connect with refresh for Google Sheets, then Slack and Notion, shown as credentials of the same types. Priority: medium. Effort: M. Compared with Zapier / n8n.
- 0
Flow: Prune old runs and steps with a retention window per workspace
n8n prunes finished executions by default after 14 days or 10,000 executions, never touching waiting runs (https://docs.n8n.io/hosting/scaling/execution-data/); Zapier keeps run history for a plan-based window. Flow never deletes flow_runs, flow_steps or their stored inputs and contexts, which can reach 2 MB input and 8 MB context per run (lib/flow.ts MAX_RUN_INPUT, lib/flow-engine.ts CONTEXT_TOTAL_LIMIT), and rows are only removed when the flow itself is deleted (ON DELETE CASCADE). The UI can only show the last 100 runs anyway (listRuns clamps to 100), so older history is dead weight on Turso and a privacy liability for trigger payloads with personal data. First scope: a pruning pass in the cron tick deleting finished runs older than 30 days (env configurable for self-host), keeping waiting runs. Priority: medium. Effort: S. Compared with Zapier / n8n.
- 0
Flow: Add triggers for Notes, Board, Agents and task, chat and booking lifecycles
Zapier and n8n triggers exist for nearly every record change in an app (new or updated item, status change). Our event bus (lib/events.ts) is called from Cal, Link, CRM, Track, Chat, Docs and Robots, but Notes, Board and Agents emit nothing, so 3 of our 11 apps cannot start a flow (no emitEvent in lib/agents.ts, notes or board code). Useful events also missing: crm task due or completed (CRM workflows have task_due), chat conversation closed or assigned, agent handoff to a human, booking no-show, docs page updated, issue assigned. Triggering across our own apps is the core promise of Flow. First scope: board.card_created/moved, agent.handoff, conversation.closed, task.due and page.updated, each with an EVENT_SAMPLES entry. Priority: high. Effort: M. Compared with Zapier / n8n.
- 0
Flow: Add workspace data tables for lookups, dedupe and state between runs
Zapier Tables is included on Free (2,500 records, table steps do not count as tasks) and n8n added Data tables with a Data Table node, CSV import and an API, used to store markers that prevent duplicate runs and lookup lists (https://zapier.com/pricing, https://docs.n8n.io/data/data-tables/). Flow has no persistent storage: every run only sees its trigger and node outputs (lib/flow-engine.ts templateCtx), so 'only notify once per contact', counters, or a mapping table need an external Google Sheet. First scope: a flow_tables store per workspace (simple typed columns, 10k rows), a data.table node with insert, upsert by key, find and delete, and a small table view in the Flow app. Priority: high. Effort: L. Compared with Zapier / n8n.
- 0
Flow: Add an approval step that pauses a run until someone approves in Slack or email
Zapier Human in the Loop pauses a Zap until reviewers approve, decline or edit data, notified by email or Slack, with a Decision field for branching (https://help.zapier.com/hc/en-us/articles/38733184458765/). n8n ships 'Send and wait for response' on Slack, Gmail, Telegram, WhatsApp and more, and human review for AI agent tools (https://docs.n8n.io/advanced-ai/human-in-the-loop-tools/). Flow already has a waiting state and resumable jobs (lib/flow-engine.ts result.kind 'wait', resumeRun) but only Delay uses it. For small teams this is the safe way to let AI draft a reply or a quote and have a human click approve before it goes out. First scope: a logic.approval node with approved/rejected/timeout outputs, notifying by email and Slack with signed links, plus an approvals inbox in the Flow app. Priority: high. Effort: M. Compared with Zapier / n8n.
- 0
Flow: Let webhooks reply with custom data and accept GET and header or basic auth
n8n's Webhook node accepts GET, POST, PUT, PATCH, DELETE and HEAD, supports basic, header and JWT auth, and can respond when the last node finishes or through a Respond to Webhook node with custom status, headers and body (https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.webhook/, https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.respondtowebhook/). Our hook route only exports POST and always answers 202 {runId} before the flow runs (app/api/flow/hooks/[token]/route.ts). That blocks verification handshakes (Meta/WhatsApp hub.challenge, Slack url_verification), form handlers that need a redirect, and small APIs built on Flow. First scope: GET support, an optional shared-secret header check, and a 'Respond to webhook' node that waits up to about 10 s for a synchronous answer. Priority: high. Effort: M. Compared with Zapier / n8n.
- 0
Flow: Add date and text formatter filters (format, add time, timezone, replace, split)
Zapier Formatter is used in a large share of Zaps: date format, add or subtract time (+1 day -2 hours), timezone conversion, text replace, split, truncate, number formatting (https://help.zapier.com/hc/en-us/articles/31162113958925). n8n exposes Luxon date helpers and string helpers in every expression. Our template engine has 13 filters and {{now}} only as an ISO string, with no date formatting, date math, replace, split, slice or round (lib/flow-template.ts applyFilter), and unknown filters are silently ignored. Without this, users fall back to the Code step, which needs Vercel Sandbox and is unavailable on many self-hosts. First scope: add date:'format':tz, add:'+1d', replace, split, slice, round and fail validation on unknown filter names. Priority: high. Effort: S. Compared with Zapier / n8n.
- 0
Flow: Add actions to update CRM records, create tasks and update Track issues
Zapier and n8n app nodes cover create, update, get and search for every object (for example the n8n HubSpot node: contacts, deals, tasks, engagements, https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.hubspot/). Flow can only create a contact (an existing email returns created:false without updating fields), enroll in a sequence, list deals created in the last N hours, and create a Track issue (lib/flow-engine.ts crmContactNode, crmDealsNode, trackIssueNode). There is no update contact, find contact, create or update deal, move deal stage, create CRM task or note, update issue status or assignee, or create a Cal booking link, even though CRM workflows already implement update_field and create_task (lib/crm-workflow-catalog.ts). Cross-app automation is the reason to use Flow instead of Zapier, so these are table stakes. First scope: app.crm_contact upsert plus app.crm_deal (create/update/move stage), app.crm_task and app.track_issue update, with pickers instead of raw IDs for projectId, sequenceId and robotId. Priority: high. Effort: M. Compared with Zapier / n8n.
- 0
Flow: Run the scheduler every minute so minute schedules, delays and retries fire on time
Zapier polls every 15 minutes on Free and every 2 minutes on paid plans, and n8n schedules run to the minute (https://zapier.com/pricing). Our editor offers interval schedules in minutes (minimum 5) and Delay in seconds or minutes, but on cloud the Flow queue only drains in the hourly /api/cron/tick ('17 * * * *' in vercel.json); the copy itself admits runs can start up to an hour late (messages/en/flow.json scheduleGranularity and delayGranularity). Node retries schedule jobs 15 s to 1 h out and also wait for the next tick. This silently breaks the most common small-team automation, 'every 15 minutes check X', and any follow-up delay. First scope: call processFlowQueue from the existing 5-minute /api/cron/robots route (or add a 1-minute cron for Flow only), then remove the granularity warnings. Priority: high. Effort: S. Compared with Zapier / n8n.
- 0
Flow: visual automations across every app
An open-source n8n/Zapier: triggers from every product, webhooks, schedules, conditions, delays, HTTP and AI steps.